Do you create a Solution and use the "Current Environment" when creating Flow for Dynamics?
26/06/2020 8:19 AM by
When creating workflows in Dynamics developers take for granted when a solution file is moved across environments, things just work. To achieve the same with Flows we need to make sure that when connecting to Dynamics using the Comm Data Service connector, we in fact connect with Common Data Service (Current Environment) connector. This connector is environmentally aware and will immediately work when the parent solution is deployed to another environment, it doesn't require any post-deployment steps.
Tip: When searching for Common Data Services (Current Environment) it’s very easy to pick the wrong one:
Do you feel this rule needs an update?