Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

Welcome to the CollectiveAccess support forum! Here the developers and community answer questions related to use of the software. Please include the following information in every new issue posted here:

  1. Version of the software that is used, along with browser and version

  2. If the issue pertains to Providence, Pawtucket or both

  3. What steps you’ve taken to try to resolve the issue

  4. Screenshots demonstrating the issue

  5. The relevant sections of your installation profile or configuration including the codes and settings defined for your local elements.


If your question pertains to data import or export, please also include:

  1. Data sample

  2. Your mapping


Answers may be delayed for posts that do not include sufficient information.

Existing place is not valid for element on import ?

edited May 29 in Troubleshooting

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.

Sign In or Register to comment.