Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
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.
Solved! Go to Solution.
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.
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.
User | Count |
---|---|
23 | |
20 | |
11 | |
9 | |
7 |
User | Count |
---|---|
49 | |
31 | |
20 | |
18 | |
15 |