{"id":32363,"date":"2022-08-10T14:57:48","date_gmt":"2022-08-10T09:27:48","guid":{"rendered":"https:\/\/www.inogic.com\/blog\/?p=32363"},"modified":"2023-04-11T14:52:49","modified_gmt":"2023-04-11T09:22:49","slug":"multi-select-option-field-in-dynamics-365-v9-2-using-power-automate","status":"publish","type":"post","link":"https:\/\/www.inogic.com\/blog\/2022\/08\/multi-select-option-field-in-dynamics-365-v9-2-using-power-automate\/","title":{"rendered":"Multi-Select Option field in Dynamics 365 V9.2 using Power Automate"},"content":{"rendered":"

Introduction<\/strong><\/h2>\n

With every release of Dynamics 365, Microsoft introduces a wide variety of features. Some of which open new doors of opportunity whereas some help in overcoming existing limitations. Introduction of Multi-Select Option Set was kind of both.<\/p>\n

However, as a customizer, we still face a few roadblocks when it comes to dealing with any Multi-Select Option Set field. However, recently while working on a requirement, we were able to set default values for a Multi-Select Option Set using Power Automate.<\/p>\n

Now, let\u2019s further explore how this was done.<\/p>\n

Recently<\/strong>, we came across a scenario where we wanted to set values for the Multi-Select Option Set field named Regions<\/strong> based on the domain of the email addresses from two of the email address fields named Sales Email<\/strong> and Support Email. <\/strong>We achieved this by using Power Automate flows (Cloud Flows) as shown below.<\/p>\n

Step 1:<\/strong><\/p>\n

On the Account entity form we have the Sales Email<\/strong>, Support Email,<\/strong> and the Regions<\/strong> field. The Sales Email<\/strong> and the Support Email<\/strong> are the email Id fields based on which we would need to set the value of Multi Option set field Regions<\/strong>.<\/p>\n

\"Power<\/p>\n

\"Power<\/p>\n

For the above example, let\u2019s say we have the Sales Email Id with the domain containing \u2018.com\u2019<\/strong><\/em> whereas the Support Email Id has the domain containing \u2018.au\u2019<\/em><\/strong>. So now based on these, the Regions<\/strong> must get set as USA<\/em><\/strong> and Australia<\/em><\/strong>.<\/p>\n

\"Business<\/a><\/p>\n

Step 2:<\/strong> Create a Power Automate flow.<\/p>\n

To create a Power Automate flow navigate to Power Platform Admin Center<\/a> -> Open your solution<\/strong> -> New<\/strong> -> Automation<\/strong> -> Cloud Flow<\/strong> -> Automated<\/strong>.<\/p>\n

\"Power<\/p>\n

Step 3:<\/strong> Next, add steps.<\/p>\n

Use the Microsoft Dataverse Trigger When a row is added, modified or deleted<\/strong>.<\/p>\n

Then set the value of Change type<\/strong> to Added or Modified<\/strong>.<\/p>\n

Added<\/strong>: Triggers on creation of a Record.<\/p>\n

Modified: Triggers on updation of a Record.<\/p>\n

\"Power<\/p>\n

Step 4: <\/strong>Add condition in the next step.<\/p>\n

\"Power<\/p>\n

Step 5:<\/strong> In the conditional step we need to add the conditions. And as per the example, since we are setting the value of the Multiselect option set based on the values in the Sales Email<\/strong> and Support Email <\/strong>fields, we will use these 2 to add the conditions as shown below.<\/p>\n

\"Power<\/p>\n

We have added the condition as, if Sales Email contains\u201d.com\u201d and Support Email contains \u201c.au\u201d then auto populate the Regions<\/strong> as \u201cUSA\u201d and \u201cAustralia\u201d.<\/p>\n

Step 6:<\/strong> Post adding the condition, under If Yes<\/strong> add the action Microsoft Dataverse \u201cUpdate a row\u201d<\/strong>.<\/p>\n

In Table name<\/strong> select the Entity\/Table name on which flow needs to run (Executed).<\/p>\n

Row Id<\/strong> is unique identifier of the Entity\/Table.<\/p>\n

\"Power<\/p>\n

In action we have passed the actual value of the regions using the custom expression.<\/p>\n

To add the custom expression, we need to select \u201cEnter custom value<\/strong>\u201d.<\/p>\n

\"8Power<\/p>\n

In expression field enter the value of the option in Regions<\/strong> field\/column \u00e0 Click on save and the same will get set in the multi-option set field(i.e. Regions).<\/p>\n

\"Power<\/p>\n

\"Power<\/p>\n

As per the example, the value of option USA is \u2019100000000<\/strong>\u2018and for Australia \u2018100000003<\/strong>\u2019 which will get set.<\/p>\n

Conclusion:<\/strong><\/h2>\n

As illustrated above, we can easily set the values in Multiselect Optionset<\/strong> field by using Power Automate<\/a>.<\/p>\n

\"Microsoft<\/a><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction With every release of Dynamics 365, Microsoft introduces a wide variety of features. Some of which open new doors of opportunity whereas some help in overcoming existing limitations. Introduction of Multi-Select Option Set was kind of both. However, as a customizer, we still face a few roadblocks when it comes to dealing with any\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":13,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[18,1985,2361],"tags":[1975],"class_list":["post-32363","post","type-post","status-publish","format-standard","hentry","category-dynamics-365-v9-2","category-power-automate","category-technical","tag-power-automate"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/32363","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/comments?post=32363"}],"version-history":[{"count":0,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/posts\/32363\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/media?parent=32363"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/categories?post=32363"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.inogic.com\/blog\/wp-json\/wp\/v2\/tags?post=32363"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}