dashboard (Legacy v1)
The dashboard aggregation node stores a v1 facade JSON payload and creates or updates a session dimension with DashboardVersion="Legacy" for ui/legacy.
When to use it
Use only for backward compatibility with existing v1 layouts and payload keys. New work should use dashboard-v2 on ui/dashboard.
Limitations
- Expects legacy top-level keys (for example
Map,combined-custom-charts,stats-summary), not$heat-dataservice. - Layout mount ids in
layoutConfigurationoften differ from payload keys (layoutMapDisplayvs dataMap). See Legacy dashboard components. dashboardUsers(camelCase) controls access; omitting it limits visibility to the runner service account.
Configuration (required)
| Property | Description |
|---|---|
dataSourceName | Data source for stored payload |
layoutConfiguration | Array of legacy row/layout specs |
dashboardName | Display name for the dimension |
Optional: autoCreateScenarioInstance, scenarioName, scenarioFromIsoKey, scenarioToIsoKey.
Input payload (summary)
{
"Map": { },
"dashboardUsers": ["<user-guid>"]
}