Unanswered

Can't Remove Cloud Flows after export

(0) Share

Report

Posted on by PerL

When we create cloud flow connections in a power pages site (under Set up / Cloud flows) and then export the solution and import it to another environment, the connections URL are still pointing to the original environment. We then want to remove and re-add the flow to get the correct URL. But Remove does not work.

Is there a predered way to handle this?

/PerL

Categories:

Administer & monitor

I have the same question (0)

All responses (3)

Answers (0)

Sort by

oliver.rodrigues 9,482 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi, I just replied your other thread and I think these are related.

So this is exactly what I am facing in my environment, I have a support ticket open with Microsoft to see if they can help, as a workaround I had to create a copy of my Flow, basically adding an unmanaged layer to my environment, which is not ideal.

Was this reply helpful? Yes No
AsaurdiffADTill 125 on at

Like
a
(0)

Report
Copy link

Link copied!

So this is a bit old and the issue of not being able to migrate flows to another environment and alter URL to reflect environment change is still happening.
Like the @OliverRodrigues we copied the flow for each environment. The key is to import the flow into the solutions if they aren't in there and turn it on first. Then once in the environment "add existing flow" to the site. DONT DO IT IN YOUR DEVELOPER INVIRONMENT. This won't help you. Make sure you add in the environment you want. Then it will give you the proper url. Doing this does not add a solution layer.
On the site we did a conditional on the page it's the flow is being triggered to interpret if the url the site is on has "dev" or "test" and to use the URL of the flow we need.
Hope this helps anyone who stumbles on this someday.

Was this reply helpful? Yes No
oliver.rodrigues 9,482 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi all, this should have been fixed as part of: Power Pages Release Version 9.6.2.x - Release Notes | Microsoft Learn

Was this reply helpful? Yes No