I need your help the scenario is that "Whenever an account record is updated in Dynamcis 365 then those fields that got updated from Envinoment A then all the account records that are available in other environments B,C or D then their all existing account records need to be updated whatever the fields got updated from Environment A into an Environment B,C or D"
Need your guideline or step by step process that how should it be accomplished ? Looking forward to get solution from you..!!
I don't think its inherently possible to create a Flow that runs in one environment and have it connect to and change values in another environment.
If you use the CDS connectors then I believe you can pick the envrionment for each action
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.
I agree, but I don't think you can get two CDS connectors configured in a single Flow that point to different environments. I haven't tried it for CDS, but I know it doesn't work for some other connectors.
This is the commentary I saw on it last November. It may have changed since then.
Here's a breakdown of the three connectors you're looking at :
Common Data Service - this connector actually supports both versions of CDS, but it will be dependent based on the environment that you're in. So if you're in an environment that has a CDS1.0 database, it will connect by default to that environment. If you have a CDS2.0 database, it will connect by default to that environment.
Experimental Connector - this is similar to the previous connector, but it includes experimental features in development by our team, and isn't recommended for production use. Generally you should only be using this connector if there is a specific feature we announce in the experimental connector you wish you use.
Dynamics 365 Connector - this is similar to the base CDS connector, however it can only connect to CDS2.0 environments. It also has the ability to connect across environments. So you can be in Env1, but connect to a database in Env2. The normal CDS connector will only connect to the database within the environment you are building your app in.
Yeah i did but was not able to form the logic that at what basis it will update to other environment's records. I also tried on the baeis of an Account Number however in next step wherein i did create a step to update in other environment but couldn't find the logic of field in "Record Identifier" ?
If you have an account number, then you can use the Lists Records action and pass in the account number into the Filter query. This will then return the guid from the other environment and you can use this as the identifier to update the record.
You can also update across environments. The CDS triggers and actions allow you to specify the environment. In the example below, i trigger an update from one CE instance and, look up the account number in another CE instance and then update it.
Check out the winners of the recent 'Can You Solve These?' community challenge!
Join us for an in-depth look at the new Power Automate features and capabilities at the free Microsoft Business Applications Launch Event.
Features releasing from October 2020 through March 2021
Fill out a quick form to claim your user group badge now!