Picklist scoping and syncing between collections

Get Help
1

Hey there,
Following up on the discussion in this thread:

Using Pick Lists in Other Collections

I am curious to know – is there a way to automate the syncing of picklist values between collections? There are some picklists I want to be different between collections. For those, I will name them by-collection and I don’t care whether they’re accessible or editable between collections, because they’re collection-specific. But for the most part, I want most of my picklists to remain identical between collections (i.e. if a picklist has the same name and applies to the same field, if I update it in one collection, I want the changes made to affect all collections with that picklist on that field). Is there a way to do this currently? Or must I manually update other collections when a picklist change is made in a particular collection?

Also, what is the expected behavior for picklists in tables + fields shared between collections within a division and discipline, such as CollectingEvent or Accession? I would expect that they would update for all collections if a value is added in one, but I don’t think that’s what I’m observing.

1 Like
2

We also have some picklists that I would want to use across ‘all’ and not have to manually add to multiple collections. :slight_smile:

I do know there is funny behaviours with editing existing picklist values vs. their labels and the way those are displayed in various forms.

1 Like