Publish and share
Move an applied Studio visual from Power BI Desktop into a saved report, Power BI Service, and supported sharing or export workflows.
From editor state to published report
| State | Meaning |
|---|---|
| Staged editor changes | JSON has changed in the Studio editor but has not yet been applied to the visual. |
| Applied visual | The current specification and configuration render in the Studio preview and are stored in the visual state. |
| Saved report | Power BI saves the applied visual state, field assignments, report filters, and layout in the PBIX. |
| Published report | Power BI Service receives the saved report state and renders the visual with the published semantic model and report context. |
Publishing workflow
- 1
Apply the specification
Confirm the current Vega JSON and configuration render without Diagnostics errors.
- 2
Return to the report canvas
Verify the visual at its final size with report filters, bookmarks, tooltips, selections, and cross-highlighting.
- 3
Save the PBIX
Store the applied visual state and report configuration in Power BI Desktop.
- 4
Publish through Power BI
Publish the report to the required workspace and connect it to the intended semantic model and permissions.
- 5
Validate in Power BI Service
Open the published report and confirm rendering, interactions, responsive sizing, focus mode, and access under the target audience permissions.
Viewing and editing
Report viewers receive the rendered visual in the normal Power BI report experience. Studio authoring actions belong to report editing: a user needs the relevant Power BI edit permission and access to the visual's Edit action to change the specification.
Sharing a report and sharing a template are different
| Method | Contains | Use |
|---|---|---|
| Power BI report sharing | The visual state inside the report together with the report model connection, layout, filters, permissions, and Power BI sharing controls. | Deliver the completed report experience to viewers or editors. |
| Studio template sharing | Portable specification, configuration, field placeholders, metadata, and an optional preview image without Power BI dataset rows. | Reuse the visual design in another report by assigning new fields. |
Published-report validation
- The applied specification is the version saved in the PBIX.
- The published semantic model supplies the expected fields and data types.
- Report, page, and visual filters produce the expected Vega datasets.
- Selections, cross-highlighting, tooltips, and context menus work with the surrounding report visuals.
- The visual remains readable at its report size and in focus mode.
- SVG or Canvas output behaves as expected in Power BI Service.
- Audience permissions provide the intended report and semantic-model access.
- Supported subscription-email and PowerPoint export scenarios have been checked when they are part of the report delivery workflow.