Rajeev Pentyala – Technical Blog on Power Platform, Azure and AI

Ability to connect to a different environment using Dataverse connector has been the most awaited feature.

Previously, the available methods to connect to Dataverse in other environments from cloud flows were through the The Dynamic 365 (deprecated) and Microsoft Dataverse (legacy).

With this new preview feature, Dataverse connector gains the ability to connect to different environments by introducing the Environment parameter.

Let’s explore this preview feature.

Steps to use this preview feature:

• Connect to a Dataverse environment and create a new cloud flow such as an instant flow with the Manually trigger a flow trigger, Alternatively, you can open an existing flow.
• Select a Dataverse Connector and search the actions with ‘Environment’ keyword as shown below.

• Lets choose and add the ‘List rows from selected environment (preview)’ action to the flow.
• There is a new Environment parameter. Use the Environment parameter to choose the environment to connect to.
  • The connection you use for the action must have permissions to perform the operation in the other environment.
  • To connect to Dataverse in the same environment as the flow, select (Current) in the Environment parameter.

• I’ve selected ‘Test’ as the Environment and ‘Account’ as the table.
  • To summarize, flow is being created on ‘Developer Dev’ environment and I am trying to fetch ‘Account’ records from ‘Test’ environment.

• My ‘Test’ environment currently has 2 ‘Account’ records.

• Save and test the flow. Flow has successfully fetched the 2 ‘Account’ records from ‘Test’ environment.

Refer here for the Microsoft Dataverse connector actions support connecting to other environments.

Add actions that connect to other environments dynamically:

• To set the Environment parameter dynamically instead of selecting a specific environment, select Enter custom value at the end of the Environment parameter selector and provide the root URL of a Power Platform environment in the format https://<yourenvironmentid>.crm.dynamics.com/.

• Save and Test the flow and you should get the results as below using the ‘Environment url’ approach.

• The URL can be provided as a string, expression, environment variable, or as dynamic content from the trigger or other actions in the flow.

Refer the current limitations of this preview feature here.

🙂