I know we can create a global option set or an option set just within the specific field.
Is there any reason we shouldn't just create Global Option sets all the time?
*This post is locked for comments
Hello,
If you have scenario when this optionset should not be reused with other entities then you can use entity-level optionset. Other than that I don't see a reason not to use Global Optionset.
Well, Global option set is used so that it can be called in multiple field creation. So instead of creating it again and again in every field, you create it just once. It just saves time. Otherwise you always have the option to create local option set
Standardization maybe.. For example, there is statuscode field in each entity, but it has different options depending on the entity. This approach would not work if you used a global option set.
Although, most of the times I tend to create global option sets.
As said the others, now i personally try when i can to use global one to make sure that maybe in the future for an unrelated project if i need to have an optionset with the same values, i can use it.
So i would go for the global one from my point of view.
Clément
I guess the way I'm thinking about it is to just create a Global Option Set for everything. It helps if you ever need to use it in the future and if not you just create a new global option set each time. Nothing to really lose right?
Unless there's something more I'm missing.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
HR-09070029-0 2
UllrSki 2
ED-30091530-0 1
