Solved! Go to Solution.
When you build a flow from a solution you need to pick the 'Common Data Service (Current Environment)' connector. Do NOT pick 'Common Data Service' connector.
These are two different connectors and they behave completely differently. The former will allow you to import without having to re-authentication and status of the flow will be 'On'.
NOTE: 'Common Data Service' does let you set the Environment to '(Current)' don't be fooled by this, you will still need to re-authentication the actions that use this after an solution import.
NOTE: the trigger for the 'Common Data Service (Current Environment)' connector is a bit flaky if you edit the flow, toggling the scope normally fixed it for me.
Hey @aggggg1
This is the expected behavior for flow exported as a part of a solution or exported individually too.
In the ones that are exported individually, you just have to provide the connections at the beginning. But the ones that are a part of a solution needs to have the connections updated on the actions itself.
Currently there is no way to automate this process (automating deployment from a devops build has been recently added for entire solutions in PowerApps but there is too less you can do about the connections)
You can try creating an idea post or upvote already existing similar ones in regard to this over here: https://powerusers.microsoft.com/t5/Flow-Ideas/idb-p/FlowIdeas
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
When you build a flow from a solution you need to pick the 'Common Data Service (Current Environment)' connector. Do NOT pick 'Common Data Service' connector.
These are two different connectors and they behave completely differently. The former will allow you to import without having to re-authentication and status of the flow will be 'On'.
NOTE: 'Common Data Service' does let you set the Environment to '(Current)' don't be fooled by this, you will still need to re-authentication the actions that use this after an solution import.
NOTE: the trigger for the 'Common Data Service (Current Environment)' connector is a bit flaky if you edit the flow, toggling the scope normally fixed it for me.
Check out new user group experience and if you are a leader please create your group
See the latest Power Automate innovations, updates, and demos from the Microsoft Business Applications Launch Event.
User | Count |
---|---|
24 | |
14 | |
12 | |
7 | |
6 |
User | Count |
---|---|
46 | |
22 | |
17 | |
15 | |
10 |