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

Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now

Reply
Kwarren35
Frequent Visitor

Deployment Pipelines - Publish over existing copies of reports not happening as expected

Hello,

 

When I attempt to move reports from Dev > Test > Prod, utilizing deployment pipelines feature, it is creating a separate report in the workspace instead of replacing the existing old report in the respective workspace I am deploying an updated report to. Does anyone know why? How can I replace the old version of report without having to manually delete the report in a workspace before deploying?

 

See "Shipping" report pictured below as my example. 

Shipping.PNGShipping - created new report.PNG

1 ACCEPTED SOLUTION
Nimrod_Shalit
Power BI Team
Power BI Team

@Kwarren35,

How did the 'Shipping' report got to production for the first time?

Today, pipelines only makes connections between items when they originated from each other.

That's the reason for assigning only 1 workspace in a pipeline.

 

If you already have production users using the report and you don't wan to remove it, i suggest you unassign both test and dev WS,

and then 'copy backwards' from production to test and then dev, to create all production items with links to test and dev instances.

this will allow you to update all content, and not create copies.

View solution in original post

2 REPLIES 2
MelissaM
New Member

Hello, 

This topic is old now but I had the same issue and found an explanation here: see-which-items-are-paired 

Nimrod_Shalit
Power BI Team
Power BI Team

@Kwarren35,

How did the 'Shipping' report got to production for the first time?

Today, pipelines only makes connections between items when they originated from each other.

That's the reason for assigning only 1 workspace in a pipeline.

 

If you already have production users using the report and you don't wan to remove it, i suggest you unassign both test and dev WS,

and then 'copy backwards' from production to test and then dev, to create all production items with links to test and dev instances.

this will allow you to update all content, and not create copies.

Helpful resources

Announcements
Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

February Power BI Update Carousel

Power BI Monthly Update - February 2026

Check out the February 2026 Power BI update to learn about new features.