Answered

Can you connect to more than one Dataverse environment at a time?

(1) Share

Report

Posted on by ghdunn

409

When you create a flow in a Power Automate environment then any Dataverse connector you use is by default going to connect to the dataverse database in that environment. Is there any way of changing that configuration so that you could, for example, List Rows from one environment, process the data, and then Unpdate a Row in a different environment?

I think I can make this work: (526) Send Data from one Power Automate Flow to Another using HTTP Requests - YouTube . In the video HTTP call is used to call a different flow, which could of course be in a different environment...but I wondered if there was any alternative/more elegant ways to stay within one flow?

I am guessing that Custom connectors could be an alternative, but again, I would like to use an 'inside the box' methods if I can.

Thanks!

Ged

Categories:

Using connectors

I have the same question (0)

All responses (11)

Answers (1)

Verified answer

Pstork1 69,026 Most Valuable Professional on at

Like (4)

Report
Copy link

Link copied!

If you use the Dataverse legacy connector you can choose which environment you want. The regular Dataverse connector will always connect to the default environment.

This article explains the difference. Announcing changes to Power Automate’s native integration with Microsoft Dataverse | Power Automate Blog

Was this reply helpful? Yes No
ghdunn 409 on at

Like (0)

Report
Copy link

Link copied!

Aha..my old friend @Pstork1 ..once more you come to my aid 🙂 Simple at that. I notice that the legacy connectors are a little different...no Fetchxml (I would need to understand the aggregation field and see if it suffices). More importantly, is there any sign that the legacy connectors will be deprecated?

Was this reply helpful? Yes No
Pstork1 69,026 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

The dynamics 365 connector has been deprecated, but the Dataverse legacy connector hasn't been. Its more that the new Dataverse connector was created for use in Dataverse for Teams, where you can only connect to the the current environment. So no sign that the older one will be deprecated anytime soon.

Was this reply helpful? Yes No
sean_incite 5 on at

Like (0)

Report
Copy link

Link copied!

Unfortunately it will be deprecated and unusable starting October 2023:
https://learn.microsoft.com/en-us/power-platform/important-changes-coming

Was this reply helpful? Yes No
Pstork1 69,026 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

One of the big obstacles standing in the way of that deprecation and removal is parity between the two connectors, particularly in terms of being able to choose the environment you want to connect to. I know they've announced plans to delete the connector, but they've also stated that they won't be able to do that until they reach parity.

Was this reply helpful? Yes No
sean_incite 5 on at

Like (0)

Report
Copy link

Link copied!

That's great to know Pstork1 - can you provide a link where they said they're waiting to achieve parity? I'm literally persuading my team right now to hold off on building a Web API connector in the meantime.

Was this reply helpful? Yes No
Pstork1 69,026 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Nothing in writing that I can point to. Just comments that have been made in conversations about this specific issue. It doesn't make sense to remove a legacy connector if the new connector can't cover the same job.

Was this reply helpful? Yes No
blakeholl 2 on at

Like (0)

Report
Copy link

Link copied!

I see information saying this functionality could hit public preview in Feb 2023, and production in March. Let's keep our fingers crossed!

Connect to other environments in the same region from the Microsoft Dataverse connector | Microsoft Learn

Was this reply helpful? Yes No
Chris from Flexsolv... 10 on at

Like (0)

Report
Copy link

Link copied!

The most recent deprecation announcement that I've seen is here.
There seems to be a functional gap between "By March 2023, no new flows can be created using the CDS 2.0 connector but existing flows will continue to work." and "Customers should use the Microsoft Dataverse connector ... the following features aren't available currently: Connector actions connecting to environments other than the current environment."
So, existing connections will continue to work until October 2023, but anybody needing to create a new one doesn't yet have an announced solution after March '23?

Was this reply helpful? Yes No
Chris from Flexsolv... 10 on at

Like (0)

Report
Copy link

Link copied!

The link above by @blakeholl no longer shows any information about connecting across other environments 😒

Was this reply helpful? Yes No