Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I am building a form and its rather large, 200 fields plus. I have been asked to create a column/field with a data type of option set for someone to enter their occupation into the form and as you can imagine the options themselves are vast (another 200) I read that when creating a dropdown option set the crm creates a column for each answer so I am wondering...
Is the best thing to do to create a new table entitled "Occupations" with a list of the occupations to choose from and then create the field as a lookup field then the user selects from that table?
This may seem obvious to you all, but hopefully one of you would be so kind as to treasure me I am thinking about this correctly...
Many thanks in advance
Yes that the the approach I would take. You can actually then tie a view of the records in that table to a single line of text field by using the autocomplete control. (I wrote an article where I mention the autocomplete control here: d365goddess.com/.../) This will make the field look like an option set!
PLEASE MARK VERIFIED IF HELPFUL
If try to insert this huge amount of values, you might succeed however when it comes to using that field on the form, views, which is not user friendly and will impact the performance, etc - the system will die.
In fact, you should avoid to create optionset which having more than 10 options. Normal user can not maintain optionset when its having 200 options.
Its not user friendly and will impact the performance.
As per your requirement, you have to create a custom entity that store 200 records and create lookup of custom entity in other entities, which will be a better solution and can, add or remove values is easy and there wouldn't be any limit.
Read more about the difference here:Lookup Field vs Option Sets in Microsoft Dynamics 365/CRM (ledgeviewpartners.com)
Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.
Another consideration is will items get retired off this list regularly - if so, lookup is usually better as you can just deactivate the retired items. In an option set if you remove an item it clears all of those values from records they were assigned to i.e. leaves a null (vs deactivate - items still exists on the records, just can't select it for new records). So with long option sets you may end up doing a lot of other work if items are being removed over time - so that you don't get nulls.
Has the problem been solved? Any updates?
Please click Yes under "Did this answer your question?" to close this thread.
Business Applications communities