Avoid showing broken visuals in apps during report deployment and refresh

Description:
When we move a report through environments (Dev → UAT → Prod), the corresponding app can temporarily display broken visuals. This typically happens in the window between deploying the updated report and completing the first dataset refresh, and then updating the app. During this period, users who open the app may see broken visuals or errors, which creates confusion and the impression that the report is not working.

Desired behaviour:
It would be very helpful if the app could continue to serve the previous, fully working version of the report until:

1. The new report version has been fully refreshed, and
2. The app has been updated successfully.

Only after these steps should users see the new version. In other words, we would like a “graceful switchover” model where:

• The old report version remains visible and functional in the app while the new version is deploying and refreshing in the background.
• Once the refresh completes successfully, the app is updated and starts showing the new version to users.

Benefits:

• Prevents users from seeing broken visuals or partially updated reports.
• Reduces confusion and support tickets caused by temporary breakages during deployment.
• Allows BI teams to follow proper deployment practices (Dev → UAT → Prod) without impacting user experience.

This feature would greatly improve reliability and user trust in Power BI apps during deployment and refresh cycles.