Perform a changeset request in Dataverse connector in Power Automate

You must’ve noticed Perform a changeset request in the Dataverse connector in Power Automate.

Purpose of this Action is to perform batch of available Dataverse connector actions successfully or rollback the batch performed inside this changeset request.

Here’s what it does.

Perform a changeset request

Here’s how to use the connector action

Select Perform a changeset request in the Dataverse connector Actions list.
Now, since this works like a batch of operations to perform all actions successfully or “rollback” operations, you’ll see this working like a Scope but only for Dataverse actions.
You have the below Actions available to perform.
Now, let’s design an example changeset batch here.
First, I’ll create an Account and then a Contact.
When this Flow runs, for example, if the Contact creation fails, the Account creation too will be rollbacked unlike having these steps outside of the “Perform a changeset request” action.
Please note that the Outputs of the Changeset request itself or even within the steps within a changeset request cannot be captured or referred to in Dynamic Content.

Hope this helps!

Here are some Power Automate posts you want to check out –

Authenticate Dataverse connector using Service Principal in a Power Automate Flow

August 9, 2022 priyeshwagh777 Dataverse, Power Automate azure active directory, Dataverse, Microsoft Azure, Power Automate, service principal

Many times, users/admins are not comfortable using their credentials being used as Connections. Some connectors do provide the ability to authenticate using Service Principal.

Let’s jump into this! 😊

Setting Up App Registration for Dynamics 365 CRM

Here’s how you setup an App Service to be used as a Service Principal for Dataverse connector in Power Automate –

Go to the Azure Portal (https://portal.azure.com/) and the look for Azure Active Directory.
In Azure Active Directory, look for App Registrations in the menu.
Now, create a + New registration record.
Now, give this App Registration a suitable name. And you can select your preferences on how the tenant type should be. I’ve left it to Single tenant or simplicity of the example.
Now, once this is created, go to the API Permissions section.
Now, look for a button to Add a permission.
Then, select Dynamics CRM and select it.
Once this is selected, you’ll get to select user_impersonation. Then, clicked Add permissions.
Once added, you’ll see that the Status column is blank. Then, click on Grant admin consent for <TenantName>.
Once you click on Grant admin consent button, you’ll be asked for confirmation. Confirm the same.
Once you confirm, you’ll see the status as Granted as shown below.
Then, go to Certificates and secrets. Once in that, click on + New client secret.
You’ll be asked the the Description, do so and Save it.
Now, you need to copy the value onto Notepad.
Now, let’s move to adding this App Registration to the Power Platform Admin Center so that you can then give appropriate permissions so that it can be used for Authentication into Dataverse.

Add Application User in Power Platform Admin Center

Go to the Power Platform Admin Center (https://admin.powerplatform.microsoft.com/) and the to the Environments section and select the correct Dataverse environment –

Select the environment which will have your Flow that will use the Dataverse connection in question.
And click Settings.
Now, expand Users + permissions section and look for Application Users.
Now, in Application Users, you’ll need to add the App Registration as a User and give Roles. Now, click on + New app user.
Now, click on + Add an app.
Now, any App Registration that has not yet been created in the current environment as user will automatically appear. Select the one you created – “Dataverse Service Principal” in this case and click on Add.
Now, select the BU.
Next, click on Security Roles’ pencil to give roles.
I’m just giving System Administrator for simplicity of example.
Now, you should be good to create this user. Click on Create.
Finally, your Application Record will look like this –
Now that your Application User is set in Dynamics / Power Platform Admin Center, you are all set to add this to authenticate the Dataverse Connector in Power Automate. Let’s do that!

Authenticating using Service Principle in Dataverse action

Now, let’s say you are starting a Flow with the Dataverse connector –

Select the Dataverse trigger you want to use. I’ll pick a common one.
Now, click on the three dots and look to add a new Connection if it already authenticated using the logged in user which is the default behavior.
Now, you’ll see the option to select –
Now, you’ll see these fields to fill in.
Now, first give the connection itself a suitable name.
Now, for Client ID – Go to the App Registration in Azure and look for the Client ID in the information section. It’ll look like this –

Paste it in the Client ID field and it’ll look like this –
Now, look for Client Secret – open the Notepad where you saved the Secret we copied while creating the Client Secret record in Azure.
Now, finally – Go to the App Registration record and you’ll find the Tenant ID here –

And paste is where it says Tenant. Now, Create this connection!
Ensure that the Connection is selected.
I’ll just add an extra variable in order to save this simple Flow and then we’ll create an Account (simple example if you see the screenshot below) in order to Run this Flow.
My Flow looks ready to be tested.
Now, I’ll create an Account in my Dynamics 365 CRM.
And the Flow would have Run already.

Validate

In order to ensure the connection is run by the Service Principal itself, you can do this –

In advanced options, you can choose to “Run as” as “Flow owner“
And when you check the details in the Flow Run, you can check the attribute in the trigger “RunAsSystemUserId“
And if you check this GUID, it belongs to the Dataverse Service Principal user we set up.

And that’s how you can setup to run the Dataverse action to use Service Principal instead of user credentials!

Hope this was useful!

Here are some Power Automate posts you want to check out –

Thank you!

Remove attachments from Dynamics 365 CRM Notes using Power Automate | Dataverse

January 18, 2022 priyeshwagh777 Dataverse, Power Automate delete crm notes attachments, delete notes attachments in crm, notes, notes attachments in crm, Power Automate

If you are looking to remove or delete the attachments from Notes (Annotation entity) in Dynamics 365 CRM / Dataverse (and not delete the Note itself), hopefully this will help!

Disclaimer: I’m not covering ‘how you can save your attachments elsewhere’, I’m only covering how you can delete from Notes given that you have handled your attachments before deleting them.

Identifying Attachments

Here are some points which will help you identify once attachments are included when you create a Note in Dynamics 365 / Dataverse.
Note that these are not in Attachments entity.

You can have a Flow that is triggered on the create of a Note (annotation) in Dataverse.
So here, the Document is Note is attached on a Note.

And the Trigger of the Dataverse connector in Flow is on the create of a Note
And when the Note is attached, the triggerOutputs body will show this data that denotes the attachment on the Note.

Clearing Attachments

Here’s how you can clear the attachments from the Notes (by not deleting the actual note). If you want to move to SharePoint, it’s a recommendation, but that’s not something I intend to cover here (Assuming you are doing something with the attachments and then wanting to delete them) –

Now, in this example, I’m attaching a Note which will be further cleared using the Update step which I’ll show.
Here’s an update step I have on the same Note which will set the Document Body & Name to null in order to clear the attachment.
To test this, I had another Flow which is triggered on the update of the Note i.e. the step above.
Once there’s nothing in the Document (documentbody), the filesize will be 0 & isdocument flag to false automatically. Also, setting the Name to Null is important – Else, you’ll still see the attachment on the Note (Just that you can’t open it)
And when you refresh the Timeline, you’ll see that the attachment is now removed.

Hope this was helpful! Here are some more Dynamics 365 posts which you might be interested in –

Thank you!!

Configure Dataverse Search in Power Platform Admin Center | Dynamics 365

October 25, 2021October 25, 2021 priyeshwagh777 Dataverse, Microsoft PowerApps dataverse search, Dynamics 365, model driven apps, power apps

Relevance Search in Dynamics 365 CRM recently got renamed to “Dataverse Seach” as you might have seen some updates.

Here’s how to configure the Dataverse Seach in the new Solutions Explorer!

Scenario

Now, in case you search on the Global Search bar for a record and the table which it lies in doesn’t show up – In this case table I’m looking in is ‘Subscription’ – that means that this entity is not configured for Dataverse Search

Dataverse Search

Here are some points on the Dataverse Search –

Dataverse search is enabled directly is you are opted in to 2021 Wave 2 Updates on your environment.
Go to https://admin.powerplatform.microsoft.com/ and open the desired environment’s Features section from Settings.

You’ll find that Dataverse Search is already ON.
Now, navigate to https://make.powerapps.com/ to configure the Dataverse Search for a specific entity.
Go to Solutions and look for the Solution which has your entity
In this example, I’ll use the custom entity I’ve created called as ‘Subscription’
In any solution which has this entity, I can click on Overview on the left.

And then if you look at the right hand side – click on Manage Index
It’ll show the entity which is not enabled for Search – But, notice that it is unchecked – means it is not enabled.

Now, enable and save it

Check if Table is enabled for Dataverse Search

Enable the Table for Search Results. Now, when you are in the Solution in the new Solution Explorer – Look for the Table. In my example, it is Subscription table.
I’ll open the Settings of the Table.
In the Settings of the Subscription table, you’ll need to expand the Advanced options.
Now, scroll below and you’ll see the option for Appear in Search Results is enabled.
And once this is enabled, the results will show up in Dynamics 365