When we use the Cloud Flows integration in Power Pages, we can use Web Roles to restrict what users can call the Flow or not.
But sometimes only this is not enough and we might want to add more logic in the Flow to prevent certain actions. For instance, you can validate the Contact ID against Dataverse records to ensure the user has the right to execute certain actions.
Check out how you can do it.
Contact ID in the Trigger
Every Power Pages user is mapped to a record in the Contact table in Dataverse. If we have a look at the properties that Power Automate provides us in the Power Pages trigger:
Note that there is a User ID returned in the ‘When Power Pages calls a Flow’ trigger. This User ID is exactly the same as the Contact ID in Dataverse.
Validating Contact against records
Imagine a scenario where you want to perform actions against Dataverse records in Power Automate. You can use Power Automate to call actions not available natively or even call
Source link
More About This Author
-
SharePoint and Office 365 Consultant/Developer always trying to get the best from Microsoft stack (Microsoft 365/Azure/Power Platform and related stuff).
Living in Ireland since 2018, I had previously worked in Brazil as a consultant/developer for Office 365, SharePoint and related technologies for almost 10 years.
Array
Modern Workplace13 April 2024Power Pages and Cloud Flows – Validate user against Dataverse records based on Contact ID
Modern Workplace6 April 2024Download SharePoint library files in Power Pages with JavaScript and Cloud flows – Improved code using jQuery & option to open PDF file in a new tab
Modern Workplace13 March 2024Handle multiple N:N records associate and disassociate requests with JavaScript and Power Pages Web API
Modern Workplace17 February 2024Generic JavaScript Functions to Associate and Disassociate Dataverse records using the Power Pages Web API
