You’re offline. This is a read only version of the page.
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?
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.
Depending on the other items in the flow, yes it is normal. You can use the legacy connector. If you start a new flow and add the new Dataverse connector to every step, skipping all the other steps, and then add your other connectors/steps it is possible to build almost any flow using the new connectors. But I don’t’ think that’s worthwhile. Just use the legacy connector.
@UI1222 Is this the normal behavior? I only see the legacy connector when I try to add an action of dataverse in an existing flow. Is it okay to use the legacy connector for now?
@mlengenfelder1 i have learned since i made this post that if you move or create the flow in a solution, you can pick and/or upgrade which Dataverse connector you are using.
Flows outside solutions doesn't have this feature. I hope this changes soon, cause its quite confusing.
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?
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.
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?
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.
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.
#1
WarrenBelz
146,743
Most Valuable Professional
#2
RandyHayes
76,287
Super User 2024 Season 1
#3
Pstork1
66,079
Most Valuable Professional
Share
Report
All responses (
Answers (