web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Converting Flow to use...
Power Automate
Answered

Converting Flow to use Dynamics 365 Prod from Sandbox

(0) ShareShare
ReportReport
Posted on by Community Power Pla... Microsoft Employee

Good morning.

 

I have a Loader flow that has been developed and tested against a Sandbox instance of Dynamics 365.

Now I need to put it into production.

Converting any 'Read' actions is easy - just change the connection.

Converting 'write' actions seems to be an issue - If I change the connection, I have to re-enter all fields I am writing (I assume because potentially the underlying Dynamics schema may be different between prod and Sandbox).

 

The only way I can do it is to have two windows open - one with the Sandbox flow and one with the Prod Flow - and transpose between the two with the fields to be written.

 

Obviously this is error prone.

 

Is there anything obvious I have missed when changing the connection from one Dynamics Instance to another? Any other suggestions

 

Stan

 

Categories:
General topics
I have the same question (0)
  • Verified answer
    Community Power Platform Member Profile Picture
    Community Power Pla... Microsoft Employee on at

    **bleep** - whenever I publish a question, five minutes later I find the solution....

     

    Anyway - what needs to change is the org in the flow.

     

    Step 1 - make a teeny little flow connecting to the Production Dynamics environment. I put in a simple list records on the Contacts entity.

     

    Step 2 - export to json

     

    Step 3 - edit (visual Studio code) and look for something like 

                                        /datasets/@{encodeURIComponent(encodeURIComponent('org8262439b.crm6'))}
     
    Step 4 - copy the bit I have bolded (org8262439b)
     
    Step 5 - Export the Sandbox flow as a zip file
     
    Step 6 - Open the zip file and go to the directory Microsoft.Flow/Flows
     
    Step 7 Edit definition.json (visual Studio Code again)
     
    Step 8 - look for the org string in here and replace all org strings with what you saved above
     
    Step 9 - save the file (my version of zip was good enough to put it back into the zip file)
     
    Step 10 - Import the zip file (make a new flow up)
     
    Stan

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

News and Announcements

Welcome to the Power Platform Communities

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the February Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 304

#2
David_MA Profile Picture

David_MA 245 Super User 2026 Season 1

#3
Expiscornovus Profile Picture

Expiscornovus 243 Most Valuable Professional

Last 30 days Overall leaderboard

Featured topics

Share your ideas and struggles with building Power Automate flows!
Survey: Power Automate mobile app
How to Ask for Help with Your Power Automate Workflow
Flows are not visible for users who sign in with their personal accounts
Start and wait for an approval action
Restore a deleted flow
List of actions cheat sheet for Power Automate Desktop
Question for everyone : How are you using Create Text GPT in AI Builder?
Welcome to the Power Automate forum!

Product updates

Microsoft Power Platform Community release plans