- the link to va-messaging.service.ts opened with a backtick and closed with a
quote, so it rendered as broken text
- the URL example was a plain URL wrapped in backticks inside a fenced block,
which shows the backticks; it is a text fence with the bare URL now
- restored the space the "updated- all from inside the same report" sentence lost
- closed the sentence about brush columns, and spelled out "primary key columns"
- two causes the banner reports were missing from the table: an entry with no
parameter before the "-", and a parameter mapped to two columns (the first
entry wins). Both come from parseVaParmap, so the table now covers every
message the banner can carry.
Checked against the merged code on release/7.20 (00df87f): the embed values and
their effects, the split at the last hyphen, the case-insensitive label match,
the plain-SAS-name rule, the anchor and period names, and the banner wording.
Tables are consistent, fences balanced, page is ASCII only, and both cross-links
(/filter/ and /developer-guide/browser-variables/) resolve.
Found by testing a report against a freshly configured instance: the DC
object showed its login card inside the report because the viewer's SAS
identity was not registered yet, which reads as a broken embed rather than
a permissions problem.
Replaces the two-sentence section with the steps a report author needs:
where the URL goes, that the parameter has to be bound into the object's
query or VA never sends it, and how to tell a working mapping from a broken
one when the report runs. Also drops the note about intnx argument names,
which was explaining a decision rather than the behaviour.
Screenshots taken against the demo estate with a licence key installed, so
no evaluation banner appears. The banner section now tabulates every cause
the editor reports, because the reader is the report author looking at the
Data Controller object and the URL is the only thing they can edit.
The SAS Visual Analytics Embed page now covers mapping report parameters to
DC columns from the URL, which the name-based match cannot do for two report
objects filtering the same column from differently-named parameters.
- new "Mapping parameters to columns" section: the `va_parmap` grammar, the
lower-case example, what overrides what, and the rules that matter to a
report author (last-hyphen split, label-then-name key matching, one parameter
to one column, no fallback to the name match)
- the warning banner is documented next to it, including that a parameter is
ignored rather than filtered on the wrong column
- the `?embed=` table now shows the Filter button per mode, so it is explicit
that `embed=true` keeps Data Controller's own filter builder while `embed=va`
hands filtering to the report
dc