While we can efficiently carry out tasks within our current environment using Power Automate flows, there might be situations where we need to perform operations in an environment different from the current one.

In a recent update, Microsoft unveiled a new action within the Microsoft Dataverse Connector, simplifying the process of connecting to and executing operations in various environments.

Using these actions, we can access records, as well as add, update, and delete records in various interconnected environments. Additionally, we can execute both bound and unbound actions within the alternative environment.

Our clients have specific needs where they need to carry out operations in their Production environment that correspond to the actions performed in the UAT environment. Essentially, when any account record is added in the UAT environment, a corresponding copy of that account record should be created in the Production environment, following the actions taken in UAT as a reference.

Here’s an example illustrating how we can establish connections to different environments and execute operations based on the current environment. In this scenario, whenever an account record is created in the present environment, we will simultaneously create an identical copy of the record in the other environment.

To accomplish this, we will set up a Power Automate flow as depicted below:

1) Here we have added a step to trigger this PowerAutomate flow when any account record is added to the current environment.

2) Now we will connect the other environment to perform the operations. To connect to other environments, select the Microsoft Dataverse connector.

3) Upon selecting the connector, you’ll encounter a variety of actions available for carrying out different tasks in alternate environments. Since we want to create a record in the connected environment, we’ve opted for the “Add a new row to the selected environment” action.

4) Once you’ve chosen the action, you will have the option to access the Environment dropdown, enabling you to pick the specific environment you wish to establish a connection with.

5) As we want to create a duplicate account record we will select the Account table and set the Account Name value which was created in our current environment to create a record with the same name.

This Power Automate flow will initiate its execution when a new account record is added to the current environment. It will then proceed to duplicate this record in another connected environment.

Not only do we can add rows, but the Microsoft Dataverse connector allows us to perform various operations by establishing connections with different environments.

Performing bound and unbound actions, Updating and deleting rows, and uploading, and downloading files in different environments can be possible with this recent update of the Microsoft Dataverse connector.

Conclusion

In summary, this blog detailed the process of connecting diverse environments within a Power Automate flow to our current workspace and demonstrated how we can execute a range of actions in different environments through the Microsoft Dataverse connector.

The post Exploring Cross-Environment Connectivity with the Microsoft Dataverse Connector first appeared on Microsoft Dynamics 365 CRM Tips and Tricks.

Please Follow the Source

The post Exploring Cross-Environment Connectivity with the Microsoft Dataverse Connector appeared first on Microsoft Dynamics 365 Blog.

The first thing to notice would be our fav button is no longer there – it has been there forever and not finding it there – first impression – what did I do to lose that button –

Dataverse search was enabled in the environment and

you now enabled the 2022 wave 1 updates…

You lost the button to Modernization

And how do I do my searches now…

The table list showed very few tables in comparison to what the environment has – I did search for a table called Position and did not find it in this list. Looking at list of tables, it looks to list all tables that are included in the app that I am currently logged into. In my case, the Sales Hub app

This means the new search restricts the search to tables included in the app and does not offer a global search that the earlier Advanced find was that allowed us to search across entities irrespective of the app we are in. This would be a major limitation for me, often I have used advanced find to have a look at System job or one of the behind the scenes entity.

Once you choose the entity, you are provided with the now familiar advanced filter screen that was introduced in the earlier release wave

It pulls up the default view that has been set for the selected entity and bring up the filter screen for you to modify the filters if required

Make the changes as required click Apply to update the view that you see behind with the results of the changes you just made

Notice the (*) against the view name that denotes the filter for the view has been modified

To save this view as a personal view click on the view selector to see the Save As ad Manage Views option now available here.

Choose Save as to save this as a personal view

Choose the Manage and share views to share the view with other users if required

Notice the Sort options now available

Personal before system – List all personal views at the top followed by System Views

System before personal – this is how it used to be earlier by default

A to Z – irrespective of type just list it alphabetically.

Click on the ellipsis against the view to get the management options

The Edit info option only allows to edit the name and description of the view. If you wish to edit the filter criteria of the view choose the same Filter buttons available on the home page

And now you get the option to either save this as a new view or update the current view filter criteria

Note: This feature is an opt-in feature and not enabled by default in an environment that has update wave 1 enabled.

To confirm if your environment has the wave update enabled navigate to your environment in Power Platform Admin Portal

Once you have confirmed that your environment has received the update, check and enable this feature. For this navigate to the Settings section for the selected environment

Navigate to Product -> Features to bring up the features screen and scroll down to see these options for Modern Advanced Find in model driven apps

Conclusion:

While the new updates look to be in line with the new modern interface that the product is moving towards, a couple of complaints that I would have is

• too many clicks to get there – in the earlier advanced find screen – we select the entity, set the criteria – execute and see the results – in the same screen – easier to go back and edit the criteria if the results weren’t as expected…
• I don’t get to see all the entities and as developers I have often looked for behind the scene entities
• How do I get my FetchXML???? Goto FetchXML Builder

Please visit the Source and support them

The post New look Advanced Find in Model Driven Apps for Dynamics 365 CRM / Dataverse appeared first on Microsoft Dynamics 365 Blog.