Versions and updates
Understand Studio, Vega runtime, template, renderer, and Power BI host versions when updating or troubleshooting a visual.
Version layers
| Layer | What it affects |
|---|---|
| Ataytis Vega Studio build | The editor, inspector, template workflow, Power BI integration, settings, and packaged runtime. |
| Vega provider version | Specification parsing, transforms, expressions, marks, signals, rendering behavior, and the schema used by the bundled runtime. |
| Template metadata version | The portable template structure, field placeholders, configuration, metadata, and import validation. |
| Power BI host version | The custom-visual host, marketplace package, data view, permissions, interactions, and Desktop or Service behavior. |
| Renderer | SVG or Canvas output and the performance or accessibility characteristics associated with that rendering mode. |
Version information in templates
Generated Studio templates record the Studio build, template metadata version, provider, and provider version used during export. This information lets the import workflow identify version differences and present a version-change message when relevant.
Visual update flow
- 1
Receive the marketplace visual update
Power BI loads the published Ataytis Vega Studio package through its visual distribution process.
- 2
Open an existing report copy
Retain the original PBIX while validating the updated visual against representative report pages.
- 3
Review version messages
Read any Studio or provider-version context displayed for the specification or imported template.
- 4
Validate the visual
Check parsing, data, rendering, interactions, responsive layout, templates, and both Desktop and Service behavior.
- 5
Save the validated report
Publish the updated report state after the required checks pass.
Compatibility checks
- Diagnostics contains no new parsing errors or Vega warnings.
- The bundled Vega schema and runtime support every transform, expression, signal, and mark used by the specification.
- The Power BI-backed
datasetretains the expected field names, types, helper fields, and row shape. - SVG and Canvas output remain consistent with the renderer used by the report.
- Power BI tooltips, selection, cross-highlighting, context menus, filters, and bookmarks retain their expected behavior.
- Existing templates import successfully and generated templates contain the expected metadata and field placeholders.
- The published report matches Desktop behavior under the target workspace and audience permissions.
Version details in support reports
A version-related support report includes the Power BI Desktop or Service version, Ataytis Vega Studio version, Vega provider version when shown, renderer, template metadata context, and whether the same behavior occurred before the update.