Hi @stribor45, as @danextian already mentioned, you shouldn't be doing "open heart surgery" on your published reports.
The typical professional report life-cycle uses 2-3 separate workspaces, depending on the size of your team:
1) One for development (usually named something like "YourWorkspaceName_Dev") => This is the one where anyone that actually develops their reports would apply any changes within the Power BI / Fabric Workspace.
2) One for test (usually named something like "YourWorkspaceName_Test") => This is where your report is deployed for your Testers (e.g. selected coworkers from the target department that will use the report later) and where any testing happens - as the name suggests. Only when the testers agree that everything works and looks right you would deploy the report to your production Workspace, where the final users will be given access to the report. In smaller companies/teams the Dev + Test workspace are sometimes merged into a single Workspace for development or testing. Separating it into two Workspaces has the advantage that it's easier to keep track of which versions the testers are looking at vs what you might still be working on in parallel (e.g. if they are testing Page1 and you're still working on Page2 )
3) One production workspace (usually named something like "YourWorkspaceName" or "YourWorkspaceNameProd"), which is where your end-users access the report. Since they only see the report there (or via a PowerBi App published from there) you can work on your report in Dev/Test without impacting the productive version.
Depending on the size of your organization, there are different ways on how you can move your Reports-Versions between the different Workspace-Layers.
The probably most common version for smaller teams is that the report developers work on a local version of the report (e.g. stored in a OneDrive or Sharepoint Folder) via Power BI Desktop and then just publish it to the target Workspaces. E.g. Dev just to test themselves how the report looks in the Browser, then to Test for the testers, then to Prod once the Testers agree that everything looks and works as intented.
The "cleanest" solution is to use Deployment Pipelines in the Power Bi Service/Fabric to automatically push the reports from Dev > Test > Prod with an approval Workflow, which requires a Power Bi Premium Capacity, Premium per User Workspace or Fabric Workspace.
https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/get-started-with-deployment-pipel...
If this post helped resolve your issue, please mark it as the solution to make it easier for future readers to find.
