It looks like you're new here. If you want to get involved, click one of these buttons!
I'm having trouble finding a similar scenario on the forums, but what I’d like to figure out is why place names that already exist don't stick on import to elements that use places as list option. For example: One place is “Berkeley, CA”, and the value to be imported for element “broadcaster_location” is “Berkeley, CA”. But the error log says this is not valid for said element. I’m obviously missing something, but is it in the places setup, or the mapping? Thanks for any feedback.
Comments
Are you using a matchOn parameter in your splitter?
No. I'm not using a splitter. I set up places to match most used values in our current database. But I get the feeling its not that straight forward?
I'd have to see your mapping and data source to say. Feel free to upload these here if you'd like our assistance.
I no longer have the data sheet I used for this import as it was a quick test, but there are no special parameters set for the element in question. Its simply a mapping to: "ca_objects.broadcaster_location", and the data coming in is something like "Seattle, WA".
In C/A the data type for the broadcaster_location is set to "places".