Toggle Auto Save for Dynamics 365 CRM environment | Power Platform Admin Center

September 28, 2021 priyeshwagh777 Power Platform Admin Center auto save, dynamics 365 crm, Power Platform Admin Center

There have been many changes over the years to the Features / Behaviors which previously used to sit in System Settings in classic Dynamics CRM. Now, that things have moved to the Power Platform Admin Center, here’s how you can change the Auto Save On / Off

Power Platform Admin Center

Let’s see how you can change the Auto Save feature for each Dynamics 365 instance

Go to https://admin.powerplatform.microsoft.com/, in Environments, select the Environment whose Auto Save you want to change – click on Settings.
Expand the Product tab and go to Behavior.
In Behavior settings, you’ll see Auto save which could be On or Off based on the current setting which you can toggle.
Finally, once you change simply click on Save and the bottom right corner which must’ve been highlighted to Save if you changed a Setting.
And that’s it, the records won’t be saved until you deliberately Save upon updating data in the same.

Hope this helps!

Here are some more Dynamics 365 / Power Apps Admin Center posts you might want to check –

Thank you!

Co-presence in Power Automate | Multiple users working on a Flow

September 15, 2021 priyeshwagh777 Power Automate co-presence, parallel editing, Power Automate

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 –

Thank you!

Create Teams Meeting invite from Power Automate

September 15, 2021 priyeshwagh777 Microsoft Teams, Power Automate Microsoft Teams, Power Automate, Project Operations

Here’s an example of several use cases which can let you create a Teams meeting from within Power Automate based on your business use case.

In my example, I’m using Power Automate to schedule a meeting from a Project in Project Operations inviting all Team Members for a follow up!

PS: Creating an Appointment in Outlook doesn’t set the Teams call. 😊

Scenario

For example, in Project Operations’ sample Project example – I want to simply put a Teams meeting to all the Project Team members of this sample Star Piping Project.

Here are my Project Team Members whom I want to send the Teams invite to.
And I should just be able to run a Flow from the Project itself to send an invite to all the Team Members.
I’m calling my Flow as ‘Teams Roundtable Meeting’
And my Flow is asking me when this meeting should be. So, I’ll mention the same.
So, I want the meeting to be on 16th Sep 2021 and start at 10:30am

And End it by 11:30am
And once the values are accepted, the Meeting should be on the Teams of all the Team Members

Let’s see how I built this Flow.

The Flow

Now, this is subjective – in your case, this could be anything we can imagine!!

I’m accepting the important parameters in the form of Dataverse (Legacy) connector [Because, this connector let’s you Run the Flow in the context of the record, the new Dataverse green connector doesn’t allow this.]

These are the values which we filled when we ran the Flow on the Project.
Further, I have some steps to retrieve the Team Members, then eventually their Email addresses (In Project Operations, you need to retrieve the Email addresses from the Bookable Resources and further – see if User record has these email addresses or not)
Next, I’ll create a variable of type Array to collect the Email Addresses which the meeting invite should go to.
Now, I’ll append all the Email Addresses I retrieved from the Team Members in the array.
Now, the Array is formed with all the Email addresses separated by commas. But, we are not done yet. We need to form a string.

So, I use Join operation to join the email addresses into a string separated by semicolon (just like how you enter in the To field of emails)

The result will be a string of Email addresses separated by semicolon

Finally, once all the important data is collected, we can proceed towards creating the Teams invite.

Create a Teams meeting

Here’s how you can create a Teams meeting from Microsoft Teams connector in Power Automate

Look for Microsoft Teams in Power Automate
Now, in this Meeting, I can set the parameters based on how I want the meeting to be created.
I’ll fill in the information which is required for the Invite to be created.
The Start Time and End Time need to be set in the date-no-TZ format, hence, I’ve arranged the same accordingly
Select Calendar Id as Calendar (Other options are Birthdays and United States Holidays)
The Outputs are from the result of the Join operation we performed to form the string of Email addresses to be added as attendees.
Finally, you can select these optional parameters to make sure the invite is created based on your preference.

And that’s it!

Teams Invite vs Calendar Invite

Now, if you have a normal Calendar Appointment, it’ll look like below – It doesn’t have a Join button

Whereas, the Teams Calendar Invite has a Join button on it

Caveats

Some caveats worth mentioning –

In case you are planning to have Appointments created in D365 and eventually either sync it to Outlook using Server-Side Sync, the invite will not be a Teams Invite.
No option to later retrieve this Outlook Appointment in Flow and convert/update it to a Teams call.

Hope this was useful!

Thank you!

Join action in Data Operations in Power Automate

September 9, 2021 priyeshwagh777 Power Automate data operations in power automate, flow, join array, Power Automate

One of the commonly used connectors to perform operations in Flow is Data Operations

To describe this action in simpler terms, it is “Joining values in an array with a value”.

Join

Here’s how you can use the Join operation in Power Automate

Look for Data Operations connector in Power Automate.
In Join, you’ll see that you’ll need two fields that takes a source and by what character you want to Join into the String result this Action will output.
Example – I want to Join numbers by a hyphen “-“. Here’s how it can be done.
Here’s how my From and Join With fields will be populated.
And this will return a String value by joining the items in the array by the value we entered in Join With.

To be sure this is string, you can click on Show raw outputs and see the results

Hope this was useful!