Hi
I am getting strange behaviour with the picklist. I created a user-defined pick list in my rock collection and can access it in my soil collection. This document indicates that pick lists are scoped to a collection (Creating & Using Pick Lists). I created a Field From Table pick list in my rock collection but cannot use it in my soil collection. Am I missing something here?
Pick lists are scoped to the ‘collection’ level, but the way pick lists are assigned is via the Schema Config.
This means to use a different pick list between two different collections for the same field, you need to create two separate pick lists with the same name in each collection.
While the Schema Config will resolve based on the pick list name you select, the items in the pick list are based on the respective pick list record in each collection.
You must create a new pick list record for each Specify collection in which you want to use it. It’s a bit confusing at first, so let me know if you’d like to set up a short meeting or if I can help provide further clarification!
" This means to use a different pick list between two different collections for the same field, you need to create two separate pick lists with the same name in each collection." - The UI doesn’t behave this way, as I can reuse the picklist from different collection!
A short meeting will be helpful. Can you please send an invite? I am happy to adjust my schedule based on your availability
Essentially, the Schema Config is at the discipline level, but pick lists are at the collection level. It’s a bit confusing as you need to create a new pick list with the same name in the other collection so it is available to Specify. Even if you can see the pick list from another collection in the schema, a new one must be created for the items to be available in other collections within the same discipline.
You can schedule a meeting with me using this link! It uses my most recent availability so anytime it says I am available I’ll be able to meet:
Thank you! @kitchenprinzessin