September 15, 2026
โ๏ธโ๐ฅ Explicit interaction syntax for Canvas Dashboard
enhancement
Canvas dashboard's explicit_interactions list now states every active connection directly, so what's written is what's active, nothing is assumed.
Also, you can name target blocks directly across FilterInteraction, PopInteraction, and DateDrillInteraction without CustomMapping wrapper needed.
Before and afterโ
-
โ Before (Old Syntax)
// Old syntax - only the disabled links are visible, not the active connectionsinteractions: [FilterInteraction {from: 'f1'to: [CustomMapping {block: ['v3', 'v4']disabled: true}]}] -
โ After (New Syntax)
// New syntax - active connections stated directlyexplicit_interactions: [FilterInteraction {from: 'f1'to: ['v1', 'v2'] // Bare block names, no CustomMapping wrapperfield: r(model.field) // Set once on the entry, not per target}]
Migration to new syntaxโ
We don't support mass conversion yet, but the transition is seamless:
- New dashboards automatically use the
explicit_interactions:syntax. - Existing dashboards convert when you next update their control or cross-filter setup.
- Legacy
interactions:syntax remains functional, without breaking changes.
Learn more: AML Dashboard Interactions