Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 2 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Have you taken a look at the new Common Data Service (Current Environment) connector within Power Automate?
If so, you may have seen some of the new actions you have available to you, when built within the context of a solution. More specifically Bound and Unbound Actions.
Recently, I had the need to automatically share records to an Owner team after creation, but identifying the proper format wasn't very straight forward. So I wanted to outline the steps below:
In order to use this connector, you must be within the context of a solution. When you use this connector, you will have multiple options to trigger the Flow compared to the standard CDS connector
In this case, I am choosing the trigger on Create. Then, you will search again for the Common Data Service (Current Environment) connector. This time it will give you the different actions. Since this action is not bound to an entity, we are going to chose Perform an unbound action.
Then, I can search for my action.
The format for the Target needs to be entitylogicalname(recordid), which you can pull as a Dynamic value from the creation trigger, in this case.
Below, you will see the proper formatting for the input values of PrincipalAccess. This is where I initially ran into issues with formatting. This needs to be in JSON format to provide the user or team that will be granted access to the record and the Access Mask for the privilege they will receive. You need to escape the @symbol for odata.type in order for this to be recognized as proper JSON format.
Here is some additional documentation on the GrantAccess action.
I hope this helps.
Business Applications communities