You can link views together so that the contents of one view are filtered based on items selected in a driving view.
dashboard elements - will be around for while as legacy...
So how does this work???
In the old world this was tied to dashboard elements
In the new world, your options for backing data.
- Screen → data: although what is this actually bound to?
- Legacy - parts of a dashboard created as dashboard elements
- Some AREAS component → each areas is tied to data
- Data-bound components → grid card etc. have their own data
Reinstate the dashboard element stuff as legacy documentation.
A grid view (grids only) will be automatically a driving view if any of the filter expressions in any of the zones reference the view by name. What is a zone? Any views that are drivers can be identified by the existence of the icon 
appearing in the top right of the view. Clicking on this icon will cause any dependent views and charts to refresh themselves based on the selection made in the driver grid view.
To make a zone dependent upon the driving view, set it up with a Filter which uses at least one condition with an expression containing the drivers view name. i.e ACCTS. When the Filter is evaluated, the view name ACCTS notation will contain the rows selected on the driving view. An example condition expression is:
AccountNum equals ACCTS.AccountNumber
Where AccountNumber is an Attribute on the driving view.
We can also drag a UID/ Primary key from a grid onto another area and it will dynamically create a background filter.
For Legacy Applications built Pre-9.0
A grid view (grids only) will be automatically a driving view if any of the filter expressions in any of the zones reference the view by name. What is a zone? Any views that are drivers can be identified by the existence of the icon appearing in the top right of the view. Clicking on this icon will cause any dependent views and charts to refresh themselves based on the selection made in the driver grid view.
To make a zone dependent upon the driving view, set it up with a Filter which uses at least one condition with an expression containing the drivers view name. i.e ACCTS. When the Filter is evaluated, the view name ACCTS notation will contain the rows selected on the driving view. An example condition expression is:
AccountNum equals ACCTS.AccountNumber
Where AccountNumber is an Attribute on the driving view.