Hey y'all,
When I am creating a flow initially I am running it and pointing it at my Dynamics 365 test environment for obvious reasons. The issue is when I change the environment setting, after testing is complete, to my PROD environment, it clears out all of my field definitions that I have put in.
Does anyone know if there is a way to change that environment setting without clearing those out?
Thanks,
Kelby Turk
System Administrator
Solved! Go to Solution.
Hey @kturk
I wish there was a workaround but looks like there is none at the moment. These Id's are the only way that the appropriate metadata is referenced to in Dynamics/CDS connectors.
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
Hi @kturk ,
Would you please take a try to definite the environment information in a variable, and insert the variable to the Environment field?
Best regards,
Alice
Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @kturk
The way the CDS/ Dynamics connectors work is, you first provide the Environemnt and based on that environment you will be provided with a list of the entities present in that environemnt and when you select a particular entity, only then any thing related to that entity (example the attributes) are going to show up. For the test environment and the prod environment, these definitions and ID's change and therefore when you change the environment on the flow action, everyhting gets cleared so that you can access the components from the selected environment (makes sense?)
Variabalising the environemnet name and such details will not work in my opinion. And there is no way that you can get rid of this. (The moment you change the environment, the settings n the action will be gone and you will have to configure all of those all over again)
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
@yashag2255 Yes I understand the difference I guess I was just hopeful there was workaround, in most cases the entities are pretty much identical except for the id, due to the environment change.
Hey @kturk
I wish there was a workaround but looks like there is none at the moment. These Id's are the only way that the appropriate metadata is referenced to in Dynamics/CDS connectors.
Hope this Helps!
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!
User | Count |
---|---|
12 | |
11 | |
8 | |
6 | |
5 |
User | Count |
---|---|
19 | |
14 | |
11 | |
10 | |
9 |