Here’s a cool feature that is just announced!
Now see who’s also Editing the Flow in parallel with you. Microsoft just announced this update is super-useful in teams working parallelly on a Flow – https://powerautomate.microsoft.com/en-us/blog/announcing-co-presence-in-power-automate/
Here’s a quick summary
Co-presence in Flow
Once a Flow is shared and if both the users happen to be on the same Flow in Edit mode at the same time, here’s how you identify
- Let’s say this Flow is being edited by CRM Admin and it’s shared with the user Priyesh Wagh too.
And it appears like a usual Flow which you are editing
- Now, on the other hand, Priyesh Wagh also logged in and opened this Flow to Edit. And when CRM Admin too is already editing parallelly, both parties will see the other participants like so –
- Both parties can continue to Edit. However, when either of them saves First after both have entered, there will be no issue.
Now, once any other party after that Saves their change i.e. 2nd save by other user than who first saved, they’ll see the below warning asking to choose an option to avoid the clash.
- Let’s say the user chooses to Save a copy, you’ll be asked to save this into a new Flow.
The new Flow saved will not be shared with other users and hence, will continue to exist outside of the Shared with me section into Cloud flows section
Hope this was useful
Here are some more Power Automate / Flow posts you might want to check out –
- Retrieve Metadata of Global OptionSets from Dynamics 365 in Power Automate | HTTP with Azure AD action
- Primary Key of Activity type entity in a Dataverse connector in Power Automate | Quick Tip
- Split On in Power Automate in SharePoint trigger for Item updates
- Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
- Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
- Invalid XML issue in Dataverse connector for List Rows action | Fetch XML Query | Power Automate
- FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
- Invalid type. Expected Integer but got Number error in Parse JSON – Error at runtime after generating Schema | Power Automate
- Asynchronous HTTP Response from a Flow | Power Automate
- Setting Lookup in a Flow CDS Connector: Classic vs. Current Environment connector | Power Automate Quick Tip