Ataytis Vega Studio documentation.

Choose Inspect visual from the command bar or press Ctrl + backquote to open and close the inspector. The inspector remains connected to the current applied Vega view and updates as the visual renders.

Data table displays a selected dataset from the Vega view. Use it to confirm field names, data types, transformed values, helper fields, row counts, and whether a transform produced the records you expected. The table supports sorting, a fixed header, pagination, and configurable page sizes of 10, 25, 50, 100, 150, or 200 rows.

• Start with dataset to validate the Power BI input.
• Select a derived Vega dataset to inspect transforms step by step.
• Look for NaN, circular, infinite, object, or truncated-value placeholders that point to unexpected data shapes.
• Compare field names here with every field and datum[...] reference in the specification.

Live signals lists the signal names available in the current Vega view and reads their current values safely. It is useful for testing selections, hover state, responsive calculations, parameter controls, brushes, and event-driven updates.

Diagnostics presents specification and configuration parsing errors plus Vega warnings at the selected log level. If no warnings or errors are present, the inspector reports that no log messages require attention.

1. 1

   Open Diagnostics

   Resolve JSON parsing errors before investigating data or styling.

2. 2

   Inspect dataset

   Confirm the expected rows and fields reach the Vega view.

3. 3

   Inspect derived datasets

   Find the first transform whose output differs from your expectation.

4. 4

   Inspect signals

   Confirm parameters and event-driven state have the expected live values.

5. 5

   Reduce the specification

   Temporarily remove later marks or transforms until the smallest failing section remains.

6. 6

   Reapply and retest

   Apply one correction at a time, then validate both the Studio preview and Power BI report canvas.