cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
MarrinerDev
Advocate II
Advocate II

Power Automate ALM broken

REALLY sick of how fragile everything to do with PowerApps/PowerAutomate ALM is. Another example below....

 

shot1.jpg

 

Upon importing an unmanaged solution from a Dev to a new production environment, we are getting a lot of errors (basically because the whole ALM/environment variable mechanism is pathetic and fragile).

 

The screen shot above is one of them. Very simply, from a PowerApp, we call this flow to create a folder in a given document library. The site and library are supplied as environment variables. In the new environment, when we click test, we get the error shown. Note several things:

1) When we delete the create folder step and replace it with the most innocuous thing we could find - i.e. Initialise a Variable, so there's no SharePoint activity at all, we STILL get this error.

2) If we create a new Flow from scratch in this environment, which is IDENTICAL to this one (i.e. create a folder using the same environment variables), it works.

3) This is only one of many Flows which fail with this error. We have other flows which call SQL (nothing to do with SharePoint) which also fail. (So don't get caught up with the parameters, data types etc, manual trigger etc - they aren't the issue).

4) We can't keep creating Flows from scratch as we need to regularly update/import the PowerApp (which calls many Flows) and the import process will trash the Flows again.

0 REPLIES 0

Helpful resources

Announcements
Register for a Free Workshop.png

Register for a Free Workshop

Learn to digitize and optimize business processes and connect all your applications to share data in real time.

September Events 2022

Check out all of these events

Attend in person or online, there are incredible conferences and events happening all throughout the month of September.

Users online (2,245)