Both images on the embed page were still captured from a local sandbox with the
editor as the top-level document, so neither showed the report around it.
- va-parmap-filtered.png: the report viewer, prompt DROPDOWN_TAB1 (relabelled on
the report, not matching any column) and SOME_DATE, with
FILTER : ( ( SOME_DROPDOWN = 'Option 1' AND SOME_DATE = '01JUL1960'd ) ) over
21 rows - the mapped parameter filtering a column that is not its name
- va-parmap-banner.png: the same object with a malformed entry
(va_parmap=SOME_DATE, no hyphen), showing the warning banner over a populated,
filtered grid
The caption for the mapping now says the date parameter beside it is
name-matched, which is what the picture shows.
va-parmap-transform.png is removed rather than replaced: the deployment used for
these captures predates the ADD/RANGE work, so there is no honest in-report
picture of a date anchor to take, and a sandbox capture would be the one image on
the page without the report around it. The section keeps the syntax, the anchors
and the examples table.
Captured from the report viewer at 1920x1100: two prompts (a value list and a
date), 21 rows returned by
FILTER : ( ( SOME_DROPDOWN = 'Option 1' AND SOME_DATE = '01JUL1960'd ) ).
- drops the header/FILTER crop, which had no VA chrome, and the sentence it
illustrated
- drops the "single row it matches" wording, which no longer describes the
picture
- documents the date clause as a code block instead of a second image
Replaces the three-parameter screenshot with a two-parameter one - a value
list and a date - and adds a zoomed crop of the DC header and FILTER line.
The date parameter arrives as a display date and is rendered as a SAS date
literal ('12FEB1960'd), the same as a date filter built inside Data
Controller. That is worth showing because VA's own prompt containers in the
report header show only the parameter label: the FILTER line is where the
selected values are legible.
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.
The route is hyphenated like the other multi-word docs paths (dcc-*, pre-edit-hook).
The page has not been published under /visualanalytics/, so only the embed-va
redirect map needs to point at the final path.
dc