Support and bug reporting
Classify a problem, collect safe and useful diagnostic evidence, and report bugs, feature requests, or security concerns through the appropriate channel.
Decide what you are reporting
| Type | Typical signs | What to do |
|---|---|---|
| Ataytis Vega Studio bug | The editor, preview, template workflow, inspector, Power BI integration, or another Studio feature behaves incorrectly and can be reproduced. | Follow the evidence checklist below and send a bug report through AtaytisTech Support. |
| Vega specification problem | Diagnostics reports a parse or runtime error, a field name is missing, or a scale and mark refer to different fields. | Start with Troubleshooting, Data table, and Diagnostics. Reduce the specification to the smallest example that still fails. |
| Feature request | The current behavior is working as documented, but a new capability or workflow would be valuable. | Describe the user problem, desired outcome, and why the current workflow is insufficient. |
| Power BI or tenant issue | The visual cannot be added, marketplace access is disabled, downloads are blocked, or the same host problem affects other visuals. | Check Power BI permissions and tenant policy with your Power BI administrator before reporting a Studio defect. |
| Security concern | You believe report data, permissions, isolation, or another security boundary could be affected. | Use the private security-reporting process below. Do not publish the details in a public issue or discussion. |
Before reporting a bug
- 1
Reproduce the problem
Repeat the action and record the exact sequence from a known starting state.
- 2
Check Diagnostics
Copy relevant errors and warnings, including the phase, location, and message text.
- 3
Inspect the data shape
Confirm the fields, data types, row count, and transformed datasets involved. Share schema only unless sample values are essential and safe.
- 4
Reduce the example
Remove unrelated marks, transforms, signals, and fields until you have the smallest specification that still reproduces the problem.
- 5
Check versions and renderer
Record the Power BI Desktop or Service version, Ataytis Vega Studio version, operating system, and whether the visual uses SVG or Canvas.
- 6
Test once more with safe sample data
Where possible, reproduce with invented or anonymised data rather than a production PBIX file.
Evidence checklist
- A concise title describing what failed and where.
- The result you expected and the result you actually received.
- Numbered reproduction steps beginning with a newly added visual or another clear starting state.
- Power BI host and version, Ataytis Vega Studio version, operating system, and SVG or Canvas renderer.
- The smallest reproducible Vega specification and any relevant configuration JSON.
- Diagnostics messages copied as text.
- A sanitised field schema and a few invented sample rows when the data shape is relevant.
- Screenshots or a short recording when they reveal layout or interaction behavior that text cannot show.
- Whether the problem occurs in Power BI Desktop, Power BI Service, or both.
Copyable bug-report template
Use the Copy button, replace each prompt, and remove any section that does not apply.
Title:
Summary:
Expected result:
Actual result:
Steps to reproduce:
1.
2.
3.
Environment:
- Power BI host and version:
- Ataytis Vega Studio version:
- Operating system:
- Renderer: SVG / Canvas
Diagnostics output:
Minimal Vega specification:
Field schema or invented sample data:
Frequency: Always / Sometimes / Once
Attachments: Screenshots or recording, with sensitive data removedSubmit the report
Send the completed report through the AtaytisTech contact page and identify Ataytis Vega Studio as the product. Keep one problem per report where possible so that reproduction, prioritisation, and resolution can be tracked clearly.
Report a security concern privately
For a suspected vulnerability, use the AtaytisTech contact page and begin the subject with Security vulnerability — Ataytis Vega Studio. Include a clear impact description and safe reproduction details, but do not include live credentials, production data, or exploit the issue beyond what is required to demonstrate it.