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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
phlppnsk
Frequent Visitor

Deployment Pipeline makes report unusable until refreshed

Hello,

 

let me introduce this post by explaining the setup. We have a pipeline set up with Dev, Test and Prod. In Dev we refresh the dataset with only a limited amount of data using some parameters. Once it is published to Test, we refresh the full scope of data to test, and once everything seems fine, we publish to Prod, where the report(s) are published to the users using an App. So far, so good.

 

Now here is my issue:

 

Every time we make a change to the report which affects the data model, the report inside the app "breaks" until the data model inside the Prod workspace is refreshed. In some cases, this can take over an hour in which users cannot really use the app/report(s). So far, I did not find a way around this issue, other than how we used to do it before deployment pipelines, which was making changes in PBI Desktop, publishing to a Test workspace, refreshing it in that workspace with full data, downloading the file from the service again, opening it on PBI Desktop again to eventually publish it to the Prod workspace. As you can read, this is super cumbersome with lots of manual steps... which is why I was super stoked when I discovered the pipeline feature - which, however, as described above, is quite the frustrating experience, too. Especially if you, for example, add a new field parameter to the report, which breaks entire visuals until the paramter is "initialized" in the respective workspace (or whatever it is called exaclty)... 

 

So, IS there a better way of using the piplines to prevent the above mentioned from happening?

If there is not, it would be awesome if the service could at least be changed in a way that a change to the data model is not pushed to a workspace's app until the app is refreshed, as is already the case with changes to a report's "front end".

1 ACCEPTED SOLUTION
v-yueyunzh-msft
Community Support
Community Support

Hi, @phlppnsk 

As far as I know, the case scenario you described: every time we make a change to a report that affects the data model, the in-app report "breaks" until the data model in the Prod workspace is refreshed, which is actually the logic of running the item in the background of the deployment pipeline of by design, which is the official documentation answer to the question you mentioned:

 

Data in the target Power BI item, such as a dataset or dataflow, is kept when possible. If there are no changes to a Power BI item that holds the data, the data is kept as it was before the deployment.

In many cases, when you have a small change such as adding or removing a table, Power BI keeps the original data. For breaking schema changes, or changes in the data source connection, a full refresh is required.

 

For more information, you can refer to :
Deployment pipelines, the Power BI Application lifecycle management (ALM) tool, process - Power BI |...

 

Thank you for your time and look forward to your understanding, if you have any ideas for improving Power BI, you can post ideas and vote on them on this site:

https://ideas.powerbi.com/ideas/

 

Thank you for your time and sharing, and thank you for your support and understanding of PowerBI! 

 

Best Regards,

Aniya Zhang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

 

View solution in original post

1 REPLY 1
v-yueyunzh-msft
Community Support
Community Support

Hi, @phlppnsk 

As far as I know, the case scenario you described: every time we make a change to a report that affects the data model, the in-app report "breaks" until the data model in the Prod workspace is refreshed, which is actually the logic of running the item in the background of the deployment pipeline of by design, which is the official documentation answer to the question you mentioned:

 

Data in the target Power BI item, such as a dataset or dataflow, is kept when possible. If there are no changes to a Power BI item that holds the data, the data is kept as it was before the deployment.

In many cases, when you have a small change such as adding or removing a table, Power BI keeps the original data. For breaking schema changes, or changes in the data source connection, a full refresh is required.

 

For more information, you can refer to :
Deployment pipelines, the Power BI Application lifecycle management (ALM) tool, process - Power BI |...

 

Thank you for your time and look forward to your understanding, if you have any ideas for improving Power BI, you can post ideas and vote on them on this site:

https://ideas.powerbi.com/ideas/

 

Thank you for your time and sharing, and thank you for your support and understanding of PowerBI! 

 

Best Regards,

Aniya Zhang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

 

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors