Toggle Experimental Features in Power Automate | Quick Tip

If you are working in Power Automate, you might want to check if you are already using the Experimental Features or not.

Here’s how you check and toggle between turned on and off.
Also, please note that it is not recommended to use Experimental Features on a Production instance. Please use Experimental Features only for Sandbox environments.

Experimental Features

Here’s how you can turn Experimental Features On or Off.

While making Flows, you can click on the Gear Icon to go into Settings on the top right corner.
When you click on it, you’ll see the dialog box where the Experimental Features could either be already turned on or off.
And that’s it. You can just save and this dialog box will be closed.

Identify Experimental Feature Turned On/Off

In order to identify how the Experimental Features are turned on or now, here’s what you check –

When turned OFF, the Dynamic Content will load on the right hand side as it always used to from the start.
And when turned ON, the buttons to choose either the Dynamic Content or the Expressions will show when clicked on a field in a Step. And then you can choose either to show the menu.

And the menu will look like this upon clicking –

Here’s official Microsoft Documentation on Experimental Features – https://docs.microsoft.com/en-us/power-automate/experimental-features?WT.mc_id=DX-MVP-5003911

Hope this was useful!
Here are some more Power Automate posts you might want to check –

Thank you!!

Auditing Enhancements for Dynamics 365 CRM in Power Platform Admin Center

February 10, 2022 priyeshwagh777 Power Platform Admin Center delete audit logs in crm, new auditing in d365 crm, Power Platform Admin Center, record access auditing in dynamics 365, user access auditing

Audit Management has improved lately in the Power Platform Admin Center (https://admin.powerplatform.microsoft.com/), let’s review what’s new!

Auditing in Power Platform Admin Center

Given that you are in the Power Platform Admin Center, let’s look at an org CFT 158’s Audit Settings –

You’ll now see an Auditing section in the environment –
And if you click on Manage as shown below, you can see what all is Enabled / Audited.

In Manage, you’ll see the below Auditing enabled and also how long the Audit Logs can be Retained for –
And you can choose for a particular environment, as to how long you want to retain the logs for. Let’s say, you don’t want to retain Audit records for Sandbox environments for more than a certain time.

Audit Log Deletion

Now, you have the ability to select what Audit Logs you want to delete based on a certain Table, People/System or from selection of Dates. –

Under the Free up capacity label in the Auditing summary on the Environment in PPAC, you’ll find a link for Delete logs.
In this menu, you’ll be able to select what Audit Logs you want to delete.
You can select from within a Table, Date selections or Access logs, by people and systems.
Beginning to Date Range
Now, let’s select by Date i.e. Deleting Logs from beginning and up to the selected Date.
Now, these are the Audit records for a sample account.
Now, I’ll select a Date i.e. 5th Jan – so, it’ll delete the Audit everything till 5th Jan (will leave 5th Jan probably because of the Timezone issue on my end.)
And once you set this, you’ll be asked for confirmation.
Once you confirm, a Bulk Delete System Job will run and look like below
And if I check my System Jobs (It probably left out 5th Jan’s logs because of time zone not set correctly)
And everything prior to 5th Jan will be deleted.
So, to verify this, I added 1 more Auditing record and then ran another job for 6th Jan to verify if 5th Jan is deleted or not.
And it deleted the 5th Jan records
Table
Now, you can also select a specific table/entity you want to delete Logs for.
And select the Tables you want retaining others. I choose Contact for example.
And it’ll ask for confirmation as well. Once I select Confirm, it’ll Delete Audit Logs only for Contact.
And the third type is to delete the Access Logs.

Note: Please note that at times, some Bulk Delete Jobs could be waiting to be submitted.

Hope this summary was useful!

Here are some more Dynamics 365 Administrator related posts you might want to check –

Thank you!

Flows with Dataverse triggers not working after Minimal Copy in Sandbox instance | Power Automate

February 4, 2022 priyeshwagh777 Power Automate callback registrations, Dataverse, flow not working, minimal copy, Power Automate

There are 2 possible ways the Flows are not triggering on the Sandbox instance after a Minimal Copy.

Let’s look at both the scenarios!

Administration Mode

Let’s get the more obvious options out of the way first. So let’s look at the Administration Mode scenarios where the Background Processes are turned off right after the Minimal Copy is completed –

In Power Platform Admin Center (https://admin.powerplatform.microsoft.com/), you can navigate to the environment and look if the Administration Mode is enabled or not.

And if it is, the Background Processes are still turned ON or not.
Now, the Administration Mode can stay ON, the Background Operations however should be Enabled.

If not, then the Administration Mode itself can be disabled entirely which will keep the background operations enabled.

But even if this doesn’t help and your Flows are not triggering, below is another possibility.

Callback Registrations in Dataverse

Callback Registration records are created when you create and Save Flows –
Microsoft Docs on Callback Registrations here – https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/developer/entities/callbackregistration?view=op-9-1?WT.mc_id=DX-MVP-5003911

Now, the reason the Flows are not triggered are because of the Minimal Copy, the Callback Registration records on the Environment also got deleted.
So, you can now create a new Flow to query all the Callback Registration records on the environment.
Add Row Count as 100 or something so that you don’t get a Flow Checker warning. 😊
Now, when you read what Callback Registration records are retrieved, you’ll only find 0 records because all the Dataverse trigger Flows are deleted
And all the other Callback Registration records which should belong to the other Flows (which has Dataverse as the trigger and not other Flows) in my environment are not listed!
And that’s why, the Flows are not triggered which are supposed to be triggered from Dataverse/CRM.

Solution

There are 2 solutions to this –

First is to Delete the Trigger itself
And then re-add the same trigger
And make sure it has all the right steps which it was supposed to have and then Save.
Now, if you Run the on-demand Flow to check the Callback Registrations, 1 record must now have been created.
And it belongs to the entity which you created the Trigger for. Annotations (Notes), in this case.
And now, if you perform the operation in Dynamics – the Flow will be triggered.
Second solution is to Re-import the Flow or the Solution in which you Flow belongs.

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

Thank you!!

Ribbon button visibility based on a null value in field in Dynamics 365 | Ribbon Workbench

February 1, 2022 priyeshwagh777 Ribbon Workbench dynamics 365 crm javascript, Ribbon Workbench, show hide ribbon button, valuerule in ribbon workbench

In case you are using ValueRule already for showing / hiding a ribbon button, but wondering how you can check for the same field for null values i.e. showing the ribbon button only when the field contains data?

I’ll explain in this post –

You can also refer this post for showing/hiding button based on a certain value – https://d365demystified.com/2021/01/08/ribbon-button-visibility-based-on-a-field-value-in-dynamics-365-ribbon-workbench/

ValueRule

Let’s consider an example where you want to show a Subscription button based on the Group Code field on the Account form –

I have a Group Code button on the Account Form, if this contains data, only then the Subscription button/flyout button should show.
So, in the Ribbon Workbench, you can select your button and start by adding a Display Rule (Assuming you don’t have other Display Rules already set which you’ll need to take care of)
In the Display Rule, you can select the type as ValueRule
In the value Rule, the field you are checking for in this example is Group Code (Name: cf_groupcode)

At this point, if I leave the Value as blank in the above screenshot, the button will be hidden if the value is blank in the above shown Display Rule. This acts as Show when “Group Code Does Not Contain Data“

In this case, the button will be shown when the Group Code field is blank.

And hidden when the Group Code field Contains Data
Now, if we choose to Invert Result, you’ll get this – This will act as Show when “Group Code Contains Data”

Now, in this condition, the Ribbon button will be shown is the Group Code has data in it.

And will be hidden when the Group Code field is blank.