The Microsoft Dataverse Actions Missing

[sperry1625]

UPDATE:  This is not related to the environment.  I imported the flow into a prod environment and I have the same issue, the Dataverse actions are not available.  Under what conditions am I not permitted to use the Microsoft Dataverse connectors?

UPDATE: I have opened a ticket with Microsoft to find out what is causing this issue.  Will update everyone once I have a resolution.

I am trying to Update a record in dataverse but the only Dataverse connector I see is the Legacy Microsoft Dataverse connector.  Why?

I use true Development environments in my tenant for development, than deploy to Prod and Production.  I am developing a flow that needs to update Dataverse but I do not see the proper connector.  I see it in my other environments, but not Development environments. Is this by design or do I need to configure something?

Thanks.

[kapilsingla27]

Hello,

Have you got any update from Microsoft

[sperry1625 · Accepted solution]

I have an update from Microsoft.

Short Answer: Rebuild the flow from scratch.

Longer answer: Microsoft stated that there was an issue with the flow that is causing that connector not to be available. They could not identify the exact issue, but the most likely fix was to recreate the flow from scratch. I am happy the flow was not very large. I recreated the flow and the problem went away.  Not an ideal resolution, but at least it was resolved.

[kapilsingla27]

Thanks for the answer but my flow is too large 😞 so rebuilding will be time consuming

[Braaank]

In my case, it doesn't appear any connector regarding to Microsoft Dataverse from scratch nor in Connectors page.

Is there anything we are missing or Microsoft just remove this connector?

[LenC]

I am trying to copy and re-use an existing Flow, which used SharePoint, and now needs to use Dataverse.

I saved a copy of the original Flow. In this new version, the Dataverse connector and activities do not show up. Only the 'Dataverse (Legacy)' connector is available.

If I create a new Flow in the same environment, the Dataverse connector shows up just fine.

Is there some switch on the Flow that allows it to see the latest Dataverse connector?

[DaniloSalgado]

Hello everyone!

In order to not recreate the flow from scratch, I recommend using the "Save As" functionality to generate a copy of the flow that is created clean and from scratch automatically.

I tried it and in the copy the flow has the actions, which had been lost, working correctly 👌.

Best regards.

[stefano_mazzi]

Hello everyone,

I'm working with the "Solutions" but I can confirm that nowadays the problem seems to persist.

I opened a ticket 2 weeks ago to the Microsoft unified enterprise support but, the answer was no such positive response.

The problem is going on, even with the "Save as" function.

I remember that few months ago if you tried to make a copy of your flow with "Save as", new flow saved in "My flows" and not directly in my solution.

I think it's a problem that Microsoft must resolve and they are still looking for a solutions.

Create a flow from scratch could be a valid way if the flow is not so big, but in my case I have many flows that are very big and it will be a waste time if I have to create them from scratch.