Update Dataverse Connector from Dataverse (Legacy) Connector

(1) Share

Report

Posted on by Michael Seerup

173

Im confused.

When can i use the new Dataverse Connector, and when can i use the old Dataverse Connector (Legacy)?

In this flow im was using the new connector, but now i can only add new steps with the old connector. Why?

dataverse connector.PNG

Bottomline, i would like to upgrade all my flows to use the new Dataverse connector, but in many cases i cant choose it, when i search for it.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (14)

Answers (1)

ChrisPiasecki 6,422 Most Valuable Professional on at

Like (1)

Report

Hi @UI1222,

You can use the new connector when authoring the Flow within an environment. The only time where you cant use the new connector is when using Azure Logic Apps, or you want to retrieve data from a different environment than the one you are authoring the flow in.

There used to be an issue where you couldn't choose the new connector when the flow was authored outside of a solution, but that was resolved some time back. You should be able to pick the new connector as its already available in your current flow.

If you're not authoring the flow in a solution currently, you may want to give that a try to see if it helps.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
Michael Seerup 173 on at

Like (2)

Report

Hi @ChrisPiasecki

I have 30+ flows within the same environment. I cant find any pattern to where i can use the old connector vs. the new connector.
Im not connecting to data from other environments.

The flows are not in a solution, but i dont see how that should chance anything.

Its right there 🙂 but only sometimes...

Maybe the issue you are referring to, isn't solved anyway. do you know where i can find more info on that?

Was this reply helpful? Yes No
bettc 44 on at

Like (3)

Report

I am having this issue as well, its only there intermittently

Was this reply helpful? Yes No
ChrisPiasecki 6,422 Most Valuable Professional on at

Like (1)

Report

Hi @UI1222,

I don't have a specific link that mentions the fix to that issue, just that Ive seen many articles previously from months back that described the issue and I used to also experience it, but have not had that issue for months now.

I'd recommend maybe try re-adding the step(s), or rather than continue spinning your wheels, recreate the flow inside a solution if possible, which is recommended in general. I'd also recommend opening a ticket with Microsoft support to report the issue as it is unexpected behavior.

---
Please click Accept as Solution if my post answered your question. This will help others find solutions to similar questions. If you like my post and/or find it helpful, please consider giving it a Thumbs Up.

Was this reply helpful? Yes No
Nielf 306 on at

Like (1)

Report

Did any of you find a solution for this issue? I am experiencing the same thing.

Was this reply helpful? Yes No
Michael Seerup 173 on at

Like (1)

Report

Unfortunately not,

I had a session with Microsoft support last week, regarding another problem, and i asked them how to upgrade the legacy connector, but they didn't know how to do it.

Was this reply helpful? Yes No
Nielf 306 on at

Like (1)

Report

Thanks for getting back, @UI1222.

I think it will be quicker for me to simply recreate the flows that uses the legacy connector than spending time troubleshooting with Microsoft Support.

Was this reply helpful? Yes No
Michael Seerup 173 on at

Like (1)

Report

I still have this problem...
I have found a pattern. when i start a new flow from scratch, all the Dataverse connections are available. As long as i stay in the first session, everything is fine. if i leave the first session and come back another day, the new Dataverse connections are no longer available.

Can anyone recognize this?

Was this reply helpful? Yes No
CU22072131-3 on at

Like (0)

Report

I ran into this issue today. Starting a new flow it works, but once I copy some steps from a different flow over, then save/close/reopen I can no longer use the new Dataverse connection, only legacy option is available.

Was this reply helpful? Yes No
CU22072131-3 on at

Like (0)

Report

I tried copying a different step that was a dataverse update action and pasting that from my clipboard doesn't work. In the "i"/information it says "The action you are trying to copy and paste doesn't match the current flow schema. Please add this action manually". So I'm ok in a new flow until I do something that changes the flow schema, then after exiting and re-entering the flow I can only use the legacy connectors. I have a couple custom connectors that I'm using, I wonder if they are doing it, or maybe it's happening when I copy and paste a legacy Dataverse operation into the new flow?

Was this reply helpful? Yes No