Recently we got the below error “Forbidden” for one of our flows that was using the Dataverse connection. After some analysis, we found the root cause of the error. The Dataverse connection reference was created using the Service Principal but it was not added as an Application User (with appropriate security role) in that environment. … Continue reading “Fix – Forbidden. There’s a problem…
Continue Reading Nishant Rana’s Article on their blog
Fix – Forbidden. There’s a problem with the flow’s trigger. Fix the trigger (Power Automate / Flow / Dataverse)
Recently we got the below error “Forbidden” for one of our flows that was using the Dataverse connection. After some analysis, we found the root cause of the error. The Dataverse connection reference was created using the Service Principal but it was not added as an Application User (with appropriate security role) in that environment….
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
- Dyn365CE7 May 2024Use Filter Array action to remove values from an array variable – Power Automate
- Dyn365CE6 May 2024Fixed – The latitude or longitude for the User record associated with this resource is invalid – Dynamics 365 Field Service /Dataverse
- Dyn365CE30 April 2024Use Geolocation Settings for Location Tracking and Auditing – Dynamics 365 Field Service
- Dyn365CE29 April 2024Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)