Share
ReportHi all,
i am managing an already running power automate process, composed by many flows, all belongin to a solution.
The majority of these flows uses a parent-child logic.
I am now adding a new requirement to the process, and in order to do that i created another sharepoint site for development-testing purpose, with all the sharepoint libraries-lists required.
After doing that, i have started copying the flows in a new 'test' solution.
This process has caused some problem, because the child flows cannot exists outside a solution, so i have removed the 'respond to an app or a flow' connector, saved again the file with a new name, and finally added to the new solution.
When i tried to save them, i received an error:
Flow save failed with code 'WorkflowUnderWrongSubscription' and message 'The child workflow '{workflowIdWasHere}' must be under the same subscription as the parent workflow.
More in general, the entire process is dangerous and time-consuming.
Have you found a way to automate the whole versioning-porting process for a complex power automate solution?
Are there some tips or know-how you can give me to help me follow a reasonable 'software best-practices compliant way' of doing such things?
Why there are not things like branching-merging in power automate?
Many thanks,
Stevan
All responses (
Answers (
293
