We are using standard SD lifecycle environments where the developers create their flows in dev and then they get promoted to higher environments. We have locked down the export/import feature to prevent users from exporting a flow and importing it into a private tenant and getting at firm data. My steps are as follows:
1) Get Flow as Admin
2) Create Flow (using output from above)
However, the output of Get Flow does not match the input to Create Flow. I managed to find a working simple example (found here) but it come nowhere close to the actual documentation found here. What am I missing? Or is there a better option?
Hi @wettsten
Are you getting any error? because flow setup like this should work :
-------------------------------------------------------------------------
If I have answered your question, please mark your post as Solved.
If you like my response, please give it a Thumbs Up.
thanks Deepak! i'm one step closer. i was able to create the flow in the other environment successfully using Get Flow instead of Get Flow as Admin. however, the trigger is broken. that particular flow was using an azure devops connection. how do i make sure to copy the connection properties to the new flow too?
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
Learn to digitize and optimize business processes and connect all your applications to share data in real time.
User | Count |
---|---|
28 | |
27 | |
23 | |
17 | |
10 |
User | Count |
---|---|
61 | |
54 | |
29 | |
27 | |
25 |