cancel
Showing results for 
Search instead for 
Did you mean: 

Ability to fix connection issues centrally

I have noticed that when importing PA/Flows from a solution, if using the CDS connector (not CDS Current Environment) or a number of other connectors, the connections break and each individual node needs to be specified as what connection it should use. Sometimes this is problematic as Flows can be quite large and each individual node can be buried in condition and loop logic. 

 

I believe there should be the ability to fix these connections centrally. The reason I say this is that the "Save As" functionality already does something similar. However, this is not a viable fix for the issue because it leaves the broken Flow there, and the new one is no longer inside the solution.

Status: New

That's great idea to maintance the incresing flows and PowerApps, especially for the repeated connectors. Pleae consider it.

 

I knew it's may very hard to achieve it in coding-level based on a complex set of rules, and there's nothing out-of-the-box that can achieve the functionality our client is looking for.

 

Comments
Microsoft
Microsoft
Status changed to: New

That's great idea to maintance the incresing flows and PowerApps, especially for the repeated connectors. Pleae consider it.

 

I knew it's may very hard to achieve it in coding-level based on a complex set of rules, and there's nothing out-of-the-box that can achieve the functionality our client is looking for.

 

Advocate I

I am building a flow that updates a separate row for each form submission and the constant breaking connections is making Automate almost unusable.

 

I dont understand why the connections dont auto repair. My account details haven't changed, its infuriating.