Embedding inside SAS Visual Analytics¶

Data Controller can be embedded inside a SAS Visual Analytics report as a data-driven content (DDC) object. This unlocks scenarios where a user can safely modify the values in an underlying SAS table, and have the visualisation updated - all from inside the same report.

URL¶

Open the editor as a DDC by appending ?embed=va to the editor route:

https://yourserver/DC/#/editor/<library>/<table>?embed=va

The ?embed= parameter accepts three values:

Value	Data Controller header and navigation	Filter button	Report drives filtering and columns
`true`	hidden	shown - Data Controller's own filter builder works as usual	no
`va`	hidden	hidden - filtering comes from the report instead	yes
`false` (or omitted)	shown	shown	no

The header and navigation means the Data Controller title bar (with its user menu), the back button and the sub-nav - everything Data Controller would normally show around the grid.

embed=true hides that and nothing else: the editor behaves exactly as it does outside a report, including the Filter button, Add Record, and any filtering you apply yourself.

embed=va hides the same furniture and hands these over to the report:

filtering - the report's filters are captured and applied as selections change, in either live mode or confirm mode (see Filter Modes below). The first table load is already filtered, so there is no unfiltered flash.
column visibility - the grid shows the columns the report sends, controlled from the report's Edit Report interface; primary-key columns are always kept visible.
the Filter button is not offered - filtering belongs to the report in this mode.
Add Record is not offered - rows are still added from Edit mode's "Add Row".
a "Back to Edit table" bar appears on the stage, approve and review pages, so a user who follows the review workflow can return to the editor without knowing Data Controller's page paths.

The two filters are not combined. A filter built inside Data Controller and a filter driven by the report are alternatives, not layers: applying one replaces the other, and in va mode the report's filter is re-applied the next time the selection changes. Showing the button there would offer a filter that silently stops applying as soon as the report is touched, which is why it is hidden rather than disabled.

How VA drives the editor¶

VA pushes a JSON payload to the iframe via window.postMessage whenever the selected rows change. Data Controller listens for these messages and:

Resolves each VA parameter to a DC column by matching on column label.
Builds a filter (using existing Filter machinery) over the selected values.
Hides any VA columns marked as brush so the grid stays focused on the user-editable columns (primary key columns are always shown).

If VA sends an empty / unmatched message the editor falls back to the unfiltered view but stays in VA mode.

More logic available in va-messaging.service.ts.

Mapping parameters to columns¶

By default each VA parameter is matched to a DC column by name: a parameter whose label is a column of the table filters that column. That means two DC instances in the same report can only filter the same column from a parameter of the same name - so two report tabs cannot hold different filters on one column.

The va_parmap URL parameter overrides the name match, one entry per mapping, <VA parameter>-<DC column>:

https://yourserver/DC/#/editor/<library>/<table>?embed=va&va_parmap=REGION_TAB1-REGION

Repeat the parameter to add mappings. A report with two tabs, each holding its own instance of the same table and filtering the same column from its own report parameter:

Report tab	DDC URL
Tab 1	`...?embed=va&va_parmap=REGION_TAB1-REGION`
Tab 2	`...?embed=va&va_parmap=REGION_TAB2-REGION`

The applied filter is visible in the editor, above the grid - here the parameter DROPDOWN_TAB1 filtering SOME_DROPDOWN, which is not its name:

A va_parmap mapping filtering a column

The mapping is per parameter, and additive:

a mapped parameter always filters the column it names; that column's type in the table decides how the value is formatted, exactly as for a name match
a parameter with no mapping keeps the default name match, so a single instance can mix mapped and unmapped parameters
the key is matched case-insensitively against the parameter's label
an entry is split at its last -, so a label may itself contain hyphens (Sales-2024-DEPT maps the label Sales-2024 to DEPT)
if the named column is not in the table being opened, the parameter is ignored rather than falling back to the name match - a typo cannot silently filter the wrong column
a column name that is not a plain SAS name is ignored
the mapping applies to filtering only; which columns the grid displays still follows the columns VA sends

When a mapping cannot be used¶

A wrong mapping would otherwise look like a working filter over the whole table, so the editor puts a banner above the grid naming the parameter, the column, the table, and what to change:

Each line names one cause, and the parameter it concerns is skipped rather than falling back to the name match - a typo never silently filters the wrong column:

What the banner says	What it means
`is not a column of <libref>.<table>`	the mapped column does not exist in the table being opened
`is not a date or datetime column`	a date anchor (`ADD`/`RANGE`) was applied to a column that holds something else
`VA is not sending`	no message has named that parameter - usually a spelling mistake in the parameter side of the entry
`all filter <COLUMN> ... different values will show no rows`	two parameters map to one column with different values, so the AND can never match
`a range needs one value`	a `RANGE` mapping was sent several values - one `BETWEEN` carries one period
`N of its M values was not a date`	part of a multi-value parameter could not be read as a date, so only the rest is applied
`was ignored: it needs a "-"` / `is not a transform`	the entry itself is malformed
`the VA parameter name is missing`	the entry starts with the `-`, so there is no parameter to map
`already maps to <COLUMN>, and a parameter can filter only one column`	the same parameter is mapped twice; the first entry wins

The banner is shown to the report author, inside the report, because that is where the entry is edited: the only fix available from the editor is to change the va_parmap entries in the URL of the Data Controller object.

Note

A parameter label containing & must be percent-encoded (%26), because & separates query parameters. A space may be written as + or %20.

Deriving dates from a parameter value¶

A mapping can resolve the parameter value through a named date anchor before the filter is built, by appending a transform to the column name:

https://yourserver/DC/#/editor/<library>/<table>?embed=va&va_parmap=SELECTED_DATE-D_DATE:ADD(QUARTER_START,-1)

A report that sends SELECTED_DATE = 27FEB1961 then filters D_DATE on 1961-02-27 and 1960-10-01 - the selected date, plus the same point one quarter earlier:

In the screenshot below the mapping is SELECTED_DATE-SOME_DATE:ADD(QUARTER_START,-1) against the demo table, and the parameter sends 27FEB1961:

A date anchor applied to the filter

The clause carries both values, so the row for the selected date and the row for the previous quarter are both included.

Transform	Result	Filter
`ADD(<anchor>,<offset>)`	the value, plus one anchor beside it	`D_DATE IN (01OCT2026, 01JUL2026)`
`RANGE(<period>,<offset>)`	one closed period	`D_DATE BETWEEN 01APR2026 AND 30JUN2026`

The anchors are QUARTER_START, QUARTER_END, MONTH_START, MONTH_END, YEAR_START and YEAR_END; the periods are QUARTER, MONTH and YEAR. The offset is a whole number of periods - negative for earlier - and defaults to 0. Names and arguments are case-insensitive.

va_parmap=SELECTED_DATE-D_DATE:ADD(QUARTER_START,-1)
va_parmap=SELECTED_DATE-D_DATE:ADD(MONTH_END,-1)
va_parmap=SELECTED_DATE-D_DATE:RANGE(QUARTER,-1)
va_parmap=SELECTED_DATE-D_DATE:ADD(YEAR_START,-1)

Notes:

the arithmetic is anchored on the parameter's value, never on today, so a saved report selects the same rows whenever it is opened
the result is always a single filter clause, so a transform combines with other parameters exactly as an unmapped one does
a transform only applies to date and datetime columns; on any other column the parameter is ignored and the warning banner says so
the offset is a whole number; unknown anchors, periods and operations are rejected with a warning naming the entry

Filter Modes¶

When running in embed=va mode, the editor provides two filter modes, controlled by the Auto-apply checkbox:

Live (default) - the editor updates automatically as you select rows in the VA report, so the data you see always matches your current selection.
Confirm - filter changes are held until you click the Apply button. This is useful when editing, where an automatic reload would discard unsaved changes.

A status indicator shows whether a filter change is pending, loading, or idle. In edit mode, a pending filter is held until you leave edit mode, so your unsaved edits are never lost.

Configuration in VA¶

The mapping lives entirely in the URL of the report object, so the job is to get the right URL onto a Data-driven content object and make sure the parameters it names actually reach it.

Add the object. In the VA Report Designer, insert a Data-Driven Content object, or select the one already on the page.
Point it at Data Controller. Open Options on the right and paste the SAS Job Execution URL of your DC deployment into Web Content URL, with embed=va and one va_parmap entry per parameter:
```
https://yourserver/SASJobExecution/?_file=/YOUR/APPLOC/services/DC.html#/editor/YOURLIB.YOURTABLE?embed=va&va_parmap=REGION_TAB1-REGION
```
Everything before the # is the normal deployment URL; the #/editor/... part is the DC route, and ?embed=va plus the va_parmap entries are what this page describes. One object per report tab, each with its own entry, is what lets two tabs filter the same column differently.
Make the parameter reach the object. VA sends an object only the parameters its query uses. A report parameter that the object's data does not reference never arrives, and the mapping then has nothing to map - DC reports it as VA is not sending ... in the banner. So bind the parameter into the object (assign it as a source on the object's query, as you would for any other visual), rather than only defining it at report level.
Save the report, then open it. DC shows the applied filter above the grid, so a correct mapping is visible without opening the editor:
```
FILTER : ( ( REGION = 'Europe' ) )
```
Something wrong shows the banner instead, with the cause and the fix - see When a mapping cannot be used above.

Note

The URL is read when the object loads, so a change to va_parmap takes effect when the report (or the page holding the object) is next opened.

Who the object runs as¶

The object runs as the person viewing the report, using their SAS identity - there is no service account behind it. That person must therefore be a registered Data Controller user: if they are not, DC shows its login card inside the object instead of the editor, which looks like a broken embed rather than a permissions matter.

Register everyone who will open the report before you ship it (Users in DC), and test the report as one of them rather than as the person who built it - the author is usually an administrator, so a report that works for them can fail for everyone else.

Debugging¶

A hook script can tell an embedded editor from a standalone one without any client-side inspection: work.browser_info carries the page URL and referrer, and work.browser_url_vars carries embed=va. See Browser Variables.

The following snippet can be used in console to dump the values being provided to DC from VA:

console.log(JSON.stringify(window.__vaLastMessage?.data, null, 2))