...
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Introduction
You can link data together so that the contents of one
...
grid view, form or card component is filtered based on
...
item(s) selected in a different grid view, which is referred to as 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.
...
For example, in a driving view grid the user selects a business and in a second view a list of contacts for that business is displayed.
Setting up Links Between Two Views
A grid view is automatically a driving view when any filter expressions in a second grid view reference it by name.
To make a grid view dependent upon the driving view, set
...
up
...
a Filter which uses at least one condition with an expression containing the
...
driving view's name.
...
e.
...
g. Business. An example condition expression is shown below, Name is an Attribute in the driving view:
| Code Block |
|---|
...
BusinessName equals |
...
BUSINESS. |
...
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.
...
NAME |
| Tip |
|---|
A view filter can be setup automatically by dragging any attribute header from one view onto a second view, form or card container. The first view will become 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
...
| title | Legacy Stuff for Dashboard Elements |
|---|
Setting up Links Between a View and Form
Grid views can be used to filter the content displayed on a form, as illustrated by the screenshot below.
This is setup by dragging the header for the attribute UID from the grid view directly onto the desired form. This will automatically setup a background filter on the screen element that will look similar to the example below e.g. filter the content for a selected record:
| Code Block |
|---|
UID equals BUSINESS.UID |
| Tip |
|---|
To edit the filter:
|
Setting up Links Between a View and Card Container
To filter a card container based on a driving view, set up a Filter which uses at least one condition with an expression containing the
...
driving view
...
| Code Block |
|---|
AccountNum equals ACCTS.AccountNumber |
Where AccountNumber is an Attribute on the driving view.
...
's name. This will be setup automatically if you drag an attribute header from the grid view onto the card container. This is illustrated below:
