Interaction and actions: parameters, navigation, inserting rows

Dashboard parameters: pick one, everything follows

The goal: a region dropdown across the top, and picking East narrows the bar chart, the pie and the detail table to East.

1. Add a selector — a data-bound Dropdown on the orders table's Region (clean) column, whose options come from that column, or a non-data dropdown whose options you type in.
2. Under its ⋮ → Add Parameters, name the parameter, region say.
3. For every component that should follow: Edit Inline → Data → Basic Filter. Column Region (clean), comparator equals, and switch the value from a fixed value to Parameter, choosing region.
4. Leave edit mode and try the dropdown.

A Date Picker works the same way: the parameter is a date, and the component filters on a date range or an equality against it. Several parameters can coexist.

A filter's value has three possible sources: a fixed value, another column, or a Parameter referencing a control.

Navigate

⋮ → Navigate, or Link to Dashboard — clicking the component goes to:

• A dashboard — another one in the workspace. This is how you drill from overview to detail.
• An external link — any http address.

Navigate with Parameters passes a value from the row you clicked (a customer name, say) to the target dashboard as a named parameter; the target's components filter on the same name, so it opens already narrowed to that customer.

Insert Row

⋮ → Insert Row — Click to add a row to the table. Add Target Table picks the table, then you map parameters (usually the values of input components) onto columns. Combined with a text input and a date picker, that is a "log it" button. On a table with a unique index it updates rather than appends, which makes a "change the status" button.

Display fields of submitted row

Pairs with a form component: after a submission it shows the row that was just written so whoever filled it in can confirm.

Embed Dashboard

⋮ → Embed Dashboard drops another whole dashboard in — how you assemble a wall display.

Debugging order

When interaction doesn't work, check in this order: the parameter names match; the field type of the column being compared is right (a text parameter against a numeric column never matches); and whether the component references an existing view whose own filter has already emptied the data.