Customer Engagement & Dynamics CRM Forum

Expand all | Collapse all

Issue with Flow after Copying Production to Non-Production

  • 1.  Issue with Flow after Copying Production to Non-Production

    Posted Nov 22, 2019 12:37 PM
    We copied our Dynamics Customer Engagement production instance down to our test (non-production) instance, as part of our standard non-production refresh.  We found that updating a record in our test environment that triggers a flow is causing the corresponding production flow to be fired, causing cross contamination between our environments.

    We have an issue logged with Microsoft but wanted to make others aware and wanted to know if anybody else has come across this issue?

    Shawn Hickey
    Burns & McDonnell
    Kansas City MO

  • 2.  RE: Issue with Flow after Copying Production to Non-Production

    Posted Nov 25, 2019 01:55 AM
    Hi Shawn, yes, I experienced this a couple of months ago, the last time we did our refresh of sandbox environment.
    I have also had a support case with Microsoft, and unfortunately they didn't find the cause of the issue, I had to delete and recreate the flow. By the way, flow was exported/imported separately because it was not in a cds solution, it didn't come over as a part of the environment cloning process. It seems that there are some leftovers in database when you clone an environment, and it's really scary that they didn't deal with that yet.

    My support case ticket id was 119040423000728, maybe you could point that out so they realize that many of us could be affected. Looking forward to see the answer you get from support, don't accept a solution to recreate as I did, at the time I had just a couple of flows, imagine cloning environment with many flows that start to trigger in production, Microsoft would not be able to help you with corrupted data.

    Zarko Radevic
    Dynamics CRM Programmer
    Digitale Medier 1881 AS


If you've found this thread useful, dive deeper into User Group community content by role