If you’re creating solutions with the Microsoft Dataverse connector, I think that you will be happy to know that starting form yesterday you can automate apps, data, and processes across Power Platform environments through new supported actions and triggers in the Microsoft Dataverse connector (actually in public preview).
Previously, the Microsoft Dataverse connector supported executing actions and triggers in the flow’s current environment. Now when using the Dataverse connector you will start seeing actions and triggers ending with “selected environment (preview)“:
When selecting one of those actions, you will be able to select the Dataverse environment:
In this way you can perform cross-environment operations between Dataverse environments (the connection you use for the action must have permissions to perform the operation in the other environment).
To work in the current environment, you need to select the (Current) option:
The connections to another Dataverse environment can also be set dynamically. To set the Environment parameter dynamically instead of selecting a specific environment in the action, select Enter custom value at the end of the Environment parameter selector and provide the root URL of a Power Platform environment in the following format:
https://<yourenvironmentid>.crm.dynamics.com/
At the time of writing this post, triggers with the selection of the environment are not yet released publicly (just wait a bit more).
The following triggers will have support for connecting to other Dataverse environments:
- When a row is added, modified or deleted
- When an action is performed
With this addition, you can create no limits integrations across Dynamics 365 and Power Platform products.
Please note that at the end of the preview phase, Dataverse connector actions in existing flows will be automatically updated to include the Environment parameter. There’s no action needed from flow owners or changes to existing flow behavior as part of this update.
A side note about performance optimizations: remember that the Microsoft Dataverse connector in Power Automate is optimized to directly connect to Dataverse through a native integration when the Environment parameter is set to (Current). When connecting to other environments, it connects through the Power Platform connectors platform (so APIs) and you will loose something in terms of performances.
Stefano Demiliani 