Tag: Power Automate
-
Dynamics 365 -Custom Filter for Subgrids with setFilterXml
The post discusses the use of the setFilterXml method in Dynamics 365 for applying custom filters to subgrids. It highlights accessing the subgrid control, retrieving existing FetchXml, modifying queries if needed, and using setFilterXml for custom logic. Note that this method is unsupported, so caution is advised.
-
Copy PowerApps/Dynamics 365 Solutions with PowerShell
Copying solutions between environments is a common task in Dynamics 365 and Power Apps projects if you do your deployments via DevOps pipelines. In this post, I will explain how to accomplish this task with PowerShell. For connecting to Dataverse via PowerShell, you can check my other post https://crmminds.com/2024/07/05/connect-to-dataverse-with-powershell/ Why…
-
How to Bulk change Owner of Power Automate Flows
When a user with critical Power Automate flows leaves, it can cause connection reference issues, disrupting business processes. To solve this, owners or admins can change flow ownership in bulk using Advanced Find. This maintains operational workflows and allows for business continuity even after the original owner leaves. For more…
-
Power Automate Connect to Other Environments
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…
-
Environment variables in Power Apps
Environment variables are a feature of Power Apps that allows you to store and reuse values across your apps and flows.
-
Http request failed as there is an error: ‘Cannot write more bytes to the buffer than the configured maximum buffer size: 104857600.’
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…
Crm Minds 