-
Managing cloud flow run history in Dataverse enhances automation tracking in Dynamics 365. Centralized monitoring, security via RBAC, and optimized performance allow for effective data management. Admins can adjust retention periods and retrieve data using APIs or the Maker Portal, ensuring better control over automated workflows and troubleshooting processes.
-
The Microsoft Dataverse connector now offers enhanced flexibility with the inclusion of the Environment parameter. Users can seamlessly connect to different environments from cloud flows, enabling actions such as listing rows, adding or updating rows, and executing actions in specific environments. Certain limitations and actions/triggers not yet supporting the Environment parameter still exist.
-
Environment variables are a feature of Power Apps that allows you to store and reuse values across your apps and flows.
-
I recently encountered an issue in one of our flow runs involving the Dataverse connector’s ‘List Rows’ action. The filter used for this action was ‘ownerid eq @userId.’ The flow was running smoothly for all users except one. Upon checking the row count for that particular user, I found it to be more than 1300.
-
In this blog post, I will show you how to get user settings from Dynamics 365 using Power Automate flows. This is a useful technique when you want to customize your app or process based on the preferences or roles of different users. For example, you might want to send different email notifications or display
-
If you are a developer working with Dataverse, you may have encountered situations where you need to perform bulk data operations without triggering the custom business logic that is applied by plug-ins, workflows or Power Automate flows. For example, you may want to import a large number of records from an external source, or update
Join the fun!
Stay updated with our latest contents and other news by joining our newsletter.
Your message has been sent
Crm Minds 