Scenario
Recently I was working for a client who want to integrate their eCommerce web site with Dynamics 365. While registering the user for an account on the website, they are using a multi select option to specify users contact preferences like email, SMS, Post, Phone etc. So the requirement is to send an email verification of the account if the users selected email as one of their contact preference. So I decided to use Power Automate.
Challenges and Solutions
As usual I decided to use CDS connecter for it. I started my step with contact create trigger but unfortunately, I could not see the multi select option set as part of the body. So, I decided to use the other CDS connector (CDS Current Environment) but unfortunately it was not there either. Then I discussed with one of my friends and decided to use ‘Get Record’ action to fetch the values and see whether its returning the multi select option set. First tried the ‘Get record’ action as part of CDS but no success, so tried the ‘Get record’ action with CDS (Current Environment), hurrah !!!! I can see the multi select option set values now.
Another issue I faced was related to checking the multi select option set value to see whether its contains email as an option. To overcome the issue, I used two compose steps. Please see the Flow steps below.

Lessons learned
- There are two CDS connectors available. Sometimes the second connector CDS (Current environment) may be hidden. So try to create the power automate as part of a solution and try to type common then system will show both connectors.

- If the Multi select option set attribute is not available as part of the body on create trigger, try to use ‘Get action’ with CDS (Current environment) connector.
- To compare multi select option set values try to do compose steps before condition check
Thanks for visiting my blog!!!
*This post is locked for comments