Answered

Error when trying to copy a flow: xrm instance API not defined

(3) Share

Report

Posted on by jbtz

Good morning,

When trying to save a cloud flow with another name (create a copy), I receive the following error message, as per below screenshot: xrm instance API not defined. Does anyone know a solution to this?

Categories:

Building flows

I have the same question (0)

All responses (14)

Answers (1)

Hikari 14 on at

Like (2)

Report

Same problem here. Not sure then it started, but I spotted it a week ago.

Any ideas?

Was this reply helpful? Yes No
OhNoNotAgain 7 on at

Like (1)

Report

And another here as well. Tried different browsers as well...

Was this reply helpful? Yes No
Jakeiswhoiam 4 on at

Like (1)

Report

Same here.... very annoying

Was this reply helpful? Yes No
Community Power Pla... on at

Like (0)

Report

Hello. Same problem here. It's been failing for at least a week. The flows I need to replicate are pretty simple, but it is still taking a LOT longer to redo it from scratch every time rather than using the "Save as" function. Still no sign of any response here from anyone at Microsoft? Not even a "we're looking into it"?

Was this reply helpful? Yes No
petecuff 6 on at

Like (0)

Report

Same error message here when copying a flow. FWIW I can access PA on 2 orgs, and it's only on one of them.

Was this reply helpful? Yes No
Rolbear 3 on at

Like (0)

Report

Same problem. Would really appreciate a solution to this. Power Automate Desktop seems to work fine for new flows, but somehow I cannot access my flows from cloud 365 flow Version.

Was this reply helpful? Yes No
Verified answer

Garrana 29 on at

Like (1)

Report

Hi Guys,

Just a newbie here, so take this with a(ll) grain(s) of salt.

I was facing the exact same issue until I created a Table under Data (default options, including examples), on the said environment, then proceeded to create a Connection with Microsoft Dataverse.

It will take a while to create a table, it still presented the same error immediately after creating, but after 5-10 minutes all was automagically solved and I was able to copy the flow.

~~Btw I noticed it after doing the above and after opening the same flow under Power Apps, so there is a smaller chance that opening the same flow under Power Apps did the trick.~~

HTH.

Was this reply helpful? Yes No
petecuff 6 on at

Like (1)

Report

Rightly, wrongly, doesn't matter: @Garrana's hack above worked for me so recommend trying - many thanks G...

Was this reply helpful? Yes No
stack22 4 on at

Like (1)

Report

going off of @Garrana 's post, I simply added the Dataverse connection on the Desktop flows tab next to the Cloud flows tab in My Flows. Restarted my computer and 5-10 minutes later signed back in and successfully copied existing flow using Save As.

Seems like Power Automate is quietly forcing users to enable Dataverse imo

Was this reply helpful? Yes No
Garrana 29 on at

Like (1)

Report

Edited my post to strikethrough the past paragraph, since @petecuff and @stack22 confirmed my first guess is probably the right one.

Regarding @stack22 suspicion that Power Automate is "quietly forcing" users to enable Dataverse, I believe that besides the looks, it seems more likely to me that Power Automate simply doesn't have anywhere to "save" the data on the cloud and expects you to have Dataverse tables enabled. The current copy method probably was tested against this assumption, and when it's not there it simply throws the exception. Developer hindsight and/or something assumption inherited from PowerBI/PowerApps environments, who knows.

@jbtz let us know if this workaround worked for you. If it did, could you kindly mark as accepted solution to help future victims?

Cheers!

Was this reply helpful? Yes No