There are several new features available in D365 v9, one of these features is MultiSelect Option Set fields.
How often would an option set be useful where you could select multiple items from the list? In v9, MultiSelect Option Sets are available as a field type. This means you will have one field with a list of options and you can select more than one option from the list!
How many of you have an area on your contact form with multiple checkboxes, that grow by the month, for subscriptions or interests? All of these checkboxes can be consolidated into ONE field. Imagine if your company offers multiple services and customers can sign up for more than one service - the MultiSelect Option Set will solve this problem as well.
If you're familiar with adding new fields to an entity, then setting up a new MultiSelect Option Set field will be no problem. It's just a different field type that you select when adding a new field to an entity. You can even point a MultiSelect Option Set field to a Global Option set as well.
On the form, the MultiSelect Option Set looks a little different than the regular option set. You can add up to 150 fields to an Option Set so the search feature can be very useful here. You also have to ability to select all items from the list with one click.
Once you select the options for the field, they are all displayed in a single field, separated by semi-colons. Throughout the D365 interface you will see this field displayed the same way whether it be on the form or on a view.
Fun fact here for developers and technical users, if you use a data migration or integration program that connects to D365 through the API, the values for this field are separated by commas because the field is an array field. This means that as a system customizer or admin, you want to avoid using commas in your option set value text.
You can use MultiSelect Option Set fields in views for the query and to show as a column. When setting up your query, pay close attention to what to use for your operator. If you use Equals/Does Not Equal it will only return/exclude records with an exact match of those values.
Consider the Interests field that is shown below. If I select Equals "Reading;Traveling" it will return records where Reading and Traveling are the only two options selected. If you had a record that had Reading, Traveling, and Cooking selected, it would not be returned in your dataset. If I select Contain Values "Reading;Traveling" it will return records that contain Reading OR Traveling as one of the selected options.
If you wanted to find records that contain both Reading and Traveling, you would have to set it up like this instead:
You can trigger a workflow from a MultiSelect Option Set field but you cannot use the field in a condition or in a create or update step. Unfortunately at this time, the fields aren't available in Business Rules or Business Process Flows either. You are also limited from using them when doing a mass update.
.getValue().length (this will show you how many values have been selected from the list)
Even though you can use Global Option Sets when creating a new MultiSelect Option Set field, you're not able to map this field through the native mappings within the entity relationships. I would not let this stop you from using Global Option Sets because I believe that this may be something that could become available at a later time.
There are ways around some of the limitations by using data migration/integration programs or by creating custom workflow plugins. These are definitely things that we can help you with.
Beringer Technology Group, a leading Microsoft Gold Certified Partner specializing in Microsoft Dynamics 365 and CRM for Distribution. We also provide expert Managed IT Services, Backup and Disaster Recovery, Cloud Based Computing and Unified Communication Solutions.
The post Dynamics 365 v9: MultiSelect Option Set Fields appeared first on CRM Software Blog | Dynamics 365.
No related posts.