Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
alfBI
Helper V
Helper V

Pipelines. How to copy a dataflow from a TST workspace to a PRO one properly ?

Dear colleagues,

 

We are using PBI pipelines to deploy dataflows between 2 workspaces (TST and PRO).

 

Unfortunately the TST workspace was not created after some time. Once created we copied the the dataflow from PRO to TST by export and importing its JSON definition.

 

Our problem now is that when we try to use the deployment pipeline, Power BI service is not able to identify both dataflows as the same (on TEST he marks it as new and on PRO as not in test)

 

Would exist a way to make PBI to know that both are the same? An obvious option would be to remove the PRO one and deploy again from TST but therefore the dataflow generate will have a differenent ID and all developments done on top of it will have to be reviewed. Someone does know a less invasive approach?

 

alfBI_0-1689146085780.png

 

Regards,

 

Alfons

1 ACCEPTED SOLUTION
blopez11
Super User
Super User

From your screenshot, it looks like you only have two items in test (one that is the same as in production, and the other which you want to promote to production).

 

Might be a little of a pain, but you could try the following:

- To be safe, save the json files for both dataflows in test.

- Remove everything in test workspace.

- Go to deployment pipeline and from the production stage perform a backwards deployment.

- Go to the test workspace and upload the json for the modified dataflow and reverify.

 

You should now be able to peform the deployment of the modified dataflow, and everything should be tied together in the pipeline.

View solution in original post

2 REPLIES 2
blopez11
Super User
Super User

From your screenshot, it looks like you only have two items in test (one that is the same as in production, and the other which you want to promote to production).

 

Might be a little of a pain, but you could try the following:

- To be safe, save the json files for both dataflows in test.

- Remove everything in test workspace.

- Go to deployment pipeline and from the production stage perform a backwards deployment.

- Go to the test workspace and upload the json for the modified dataflow and reverify.

 

You should now be able to peform the deployment of the modified dataflow, and everything should be tied together in the pipeline.

Many Thx. It worked. I missed the option  backwards deployment.

 

Regards

 

 

Helpful resources

Announcements
FabCon Global Hackathon Carousel

FabCon Global Hackathon

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!

September Power BI Update Carousel

Power BI Monthly Update - September 2025

Check out the September 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors
Top Kudoed Authors