Yes, we have the same issue. Even if we target the "current" environment with the connector we still have to re-authenticate the connection for each flow step when we deploy the flow to a new environment.
There is another CDS connector which is Common Data Service (current environment) which has more/different functionality to the original CDS connector. e.g. associate or disassociate records and use fetchXML as a filter for list record criteria.However, I think you still need to re-establish the connection when you deploy the solution to a new environment.
We've found with the CDS (current environment connector) that even though the CDS connections at each step are showing an error, if the flow is deployed to a new environment via a solution then it can still be turned on and will still run without re-authenticating each step
Matthew Slack CRM Functional Specialist T: 0161 953 7500 Extn: 3500
AQA Devas Street, Manchester M15 6EX
We hope this email was meant for you. If that's not the case, we apologise and would appreciate it if you could let us know and delete the message without sharing it or doing anything else with it.
We take great care to ensure that the personal data that we've used to send you this email is protected and you can find out more about our commitment to keeping customers' data safe at http://www.aqa.org.uk/about-us/privacy-policy
AQA Education (AQA) is a registered charity (number 1073334) and a company limited by guarantee registered in England and Wales (number 3644723). Our registered address is AQA, Devas Street, Manchester M15 6EX._________________________________________________________________________________
Wow @Zarko Radevic, this was a tricky bug you had, Never happy when those type of strange behaviours.
@Matthew Slack, the behaviuor you have is rather strange to. Happy that it works fine even with the error shown.... Unfortunatly, I just tested it and doesn't work for me.
For the moment, I will just removed flows for our AzureDevOps release pipeline and managed them manually, I am quite sure that this will be temporary. Flows are rather new and they improve quickly!
Adding myself to this thread as I'm in the same boat, trying to figure out best practice for moving flows from one environment to another.
I'm guessing additional, clearer documentation is out there, and this frustration is simply remedied... I just haven't found it yet. ... Or maybe we're caught somewhere in an documentation gap between the CDS, D365 CE, PowerApps, and Flow teams as far as documentation goes? Any helpful links?
Maybe if I figure this out, I'll write a blog to tell the story.
Hi @Ryan Perry,
Thank you for all these details on your research. Hopefully documentations will get updated and deployment process will improve.
I will participate to the Event "Colaborate Canada" in Ottawa in two weeks. There will be some conferences about Flows in Dynamics, including deployments considerations. I hope to learn thinks there and discuss to other people and gets clues about how this will evolve.
I will let you know if I found a solution or at least documentation!
Hi @Niels Lønberg,I just test the scenario again, and unfortunatly the issue is still there.
Moreover, The link in my previous post seems now to link to the page about environment variables in solutions. This seems to be a great feature!, yet not sure that it will address the issue about connections not automatically created. And the date of availability is november not october, So I will have to check this in the following weeks.
If you've found this thread useful, dive deeper into User Group community content by role