Flows from the field: Dataverse API assignments; API calls; Child flows; OData filters
Dynamics 365 professionals share insights on Dataverse API assignments, API calls, child flows, and OData filters, all with Power Automate.
Want to see your flow featured in a future edition of this series? Contact me with your example.
Controlling Dataverse API assignment with Power Automate
Jerry Weinstock, writing on the CRM Innovation blog looked at how to implement granular controls that determine which user account gets charged for Dataverse CRUD API calls. Currently, one of the advanced options is Run as. Whatever gets selected as Run as overrides the assignment of the flow API calls rule so that all subsequent CDS actions default back to the process owner—essentially the person tasked as the owner of the flow.
To get going, users should navigate to the Run as selector and the go to the menu in the top right of the action card, allocating the flow owner to the API call. He explained the delegate privilege and team-owned records. Weinstock wrote:
Microsoft Dataverse records get acted on and created with the ‘right’ user information. So instead of every downstream CRUD action causing the created by, owner or modified by field to be filled in with the user that owns the flow, in many cases it would make more sense for it to be done in the name of the originating record. This is perfect in the case of child records where there is a security setting or view that either restricts the user to only seeing records they own or a view that returns “My ‘records’ ” so that they get the. And then ...
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us hereor login