The embed page had no picture of Data Controller actually running inside a report - the three existing images came from a local sandbox with the editor as the top-level document. These were captured from a Viya deployment with DC deployed at an app-loc and embedded as a data-driven content object.
What the images show
img/va-report-filters.png - the report viewer with two report parameters, a value list (SOME_DROPDOWN = Option 2) and a date (SOME_DATE = 12FEB1960), reaching one Data Controller object. The editor shows FILTER : ( ( SOME_DROPDOWN = 'Option 2' AND SOME_DATE = '12FEB1960'd ) ) and the one row that matches, so the filter is proven end to end rather than asserted.
img/va-report-filter-line.png - a crop of that header and FILTER line, because a date parameter is rendered as a SAS date literal exactly as a date filter built inside Data Controller would be, and that is the detail worth reading. It also matters that VA's own prompt containers in the report header show only the parameter label; the FILTER line is where the selected values are legible.
img/va-report-object-options.png - the report designer with the object selected, and Options > Web Content > URL holding the full ?embed=va&va_parmap=... URL. This is the step the page previously described in prose only.
Prose added
the URL is an object property, not a data source: the object needs no data assigned for DC to open its own table (a report whose only object is the DDC renders with no data source at all).
an unlicensed deployment, or one that has not had the EULA accepted, shows its licensing screen inside the object - the same "looks like a broken embed" shape as the missing-DC-user case, and fixed in the deployment rather than the report.
the debugging section now says the label inside the parameters array of window.__vaLastMessage.data is exactly what a va_parmap entry has to match.
Verification
mkdocs build --clean completes and all three images render in site/visual-analytics/index.html.
Every PNG was read back after capture: correct filter text including the date literal, the matching row, no demo/licence banner, no error modal, no roles overlay, nothing clipped.
The embed page had no picture of Data Controller actually running inside a report - the three existing images came from a local sandbox with the editor as the top-level document. These were captured from a Viya deployment with DC deployed at an app-loc and embedded as a data-driven content object.
## What the images show
- `img/va-report-filters.png` - the report viewer with two report parameters, a value list (`SOME_DROPDOWN` = Option 2) and a date (`SOME_DATE` = 12FEB1960), reaching one Data Controller object. The editor shows `FILTER : ( ( SOME_DROPDOWN = 'Option 2' AND SOME_DATE = '12FEB1960'd ) )` and the one row that matches, so the filter is proven end to end rather than asserted.
- `img/va-report-filter-line.png` - a crop of that header and FILTER line, because a date parameter is rendered as a SAS date literal exactly as a date filter built inside Data Controller would be, and that is the detail worth reading. It also matters that VA's own prompt containers in the report header show only the parameter label; the FILTER line is where the selected values are legible.
- `img/va-report-object-options.png` - the report designer with the object selected, and **Options > Web Content > URL** holding the full `?embed=va&va_parmap=...` URL. This is the step the page previously described in prose only.
## Prose added
- the URL is an object property, not a data source: the object needs no data assigned for DC to open its own table (a report whose only object is the DDC renders with no data source at all).
- an unlicensed deployment, or one that has not had the EULA accepted, shows its licensing screen inside the object - the same "looks like a broken embed" shape as the missing-DC-user case, and fixed in the deployment rather than the report.
- the debugging section now says the `label` inside the `parameters` array of `window.__vaLastMessage.data` is exactly what a `va_parmap` entry has to match.
## Verification
- `mkdocs build --clean` completes and all three images render in `site/visual-analytics/index.html`.
- Every PNG was read back after capture: correct filter text including the date literal, the matching row, no demo/licence banner, no error modal, no roles overlay, nothing clipped.
Adds the two screenshots the embed page was missing, both captured from a
Viya deployment with Data Controller embedded as a data-driven content
object:
- three report parameters (SOME_CHAR, SOME_DROPDOWN, SOME_NUM) reaching one
object, with the combined FILTER line and the single matching row in the
editor
- the object's Options pane, showing the URL as a Web Content property
rather than a data source
Also documents two things that make an embedded object look broken when the
deployment is fine: the URL is an object property and the object needs no
data assigned, and an unlicensed / not yet accepted deployment shows its
licensing screen inside the object. The debugging section now says the
parameter label in the postMessage payload is the key va_parmap matches.
allan
merged commit bd736bc91c into main2026-10-29 12:59:07 +00:00
allan
deleted branch docs/va-report-screenshots2026-10-29 12:59:07 +00:00
Reviewed the full diff: docs/visual-analytics.md prose additions and two new screenshots. The PNGs are binary, so only their alt text and placement were assessed.
docs/visual-analytics.md:175 the new sentence "the object needs no data assigned for Data Controller to open its own table" reads as contradicting step 3 at line 181 ("bind the parameter into the object (assign it as a source on the object's query)"). Say which one: no data source is required for DC to render its own table, while report parameters still have to be bound to the object before VA will send them - otherwise a reader follows the new sentence and concludes step 3 is optional.
docs/visual-analytics.md:210 the file still ends without a trailing newline (the diff shows "No newline at end of file" on the closing fence's paragraph). Terminate the file with a newline so later diffs stay one-line rather than rewriting the last line.
2 findings above for review.
Reviewed the full diff: docs/visual-analytics.md prose additions and two new screenshots. The PNGs are binary, so only their alt text and placement were assessed.
- docs/visual-analytics.md:175 the new sentence "the object needs no data assigned for Data Controller to open its own table" reads as contradicting step 3 at line 181 ("bind the parameter into the object (assign it as a source on the object's query)"). Say which one: no data source is required for DC to render its own table, while report parameters still have to be bound to the object before VA will send them - otherwise a reader follows the new sentence and concludes step 3 is optional.
- docs/visual-analytics.md:210 the file still ends without a trailing newline (the diff shows "No newline at end of file" on the closing fence's paragraph). Terminate the file with a newline so later diffs stay one-line rather than rewriting the last line.
2 findings above for review.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
hermes
The embed page had no picture of Data Controller actually running inside a report - the three existing images came from a local sandbox with the editor as the top-level document. These were captured from a Viya deployment with DC deployed at an app-loc and embedded as a data-driven content object.
What the images show
img/va-report-filters.png- the report viewer with two report parameters, a value list (SOME_DROPDOWN= Option 2) and a date (SOME_DATE= 12FEB1960), reaching one Data Controller object. The editor showsFILTER : ( ( SOME_DROPDOWN = 'Option 2' AND SOME_DATE = '12FEB1960'd ) )and the one row that matches, so the filter is proven end to end rather than asserted.img/va-report-filter-line.png- a crop of that header and FILTER line, because a date parameter is rendered as a SAS date literal exactly as a date filter built inside Data Controller would be, and that is the detail worth reading. It also matters that VA's own prompt containers in the report header show only the parameter label; the FILTER line is where the selected values are legible.img/va-report-object-options.png- the report designer with the object selected, and Options > Web Content > URL holding the full?embed=va&va_parmap=...URL. This is the step the page previously described in prose only.Prose added
labelinside theparametersarray ofwindow.__vaLastMessage.datais exactly what ava_parmapentry has to match.Verification
mkdocs build --cleancompletes and all three images render insite/visual-analytics/index.html.Reviewed the full diff: docs/visual-analytics.md prose additions and two new screenshots. The PNGs are binary, so only their alt text and placement were assessed.
2 findings above for review.