Build a reusable view

A view owns a useful section from data input to visible output. Keep components together when they share a dataset or local selection. Create separate saved views for unrelated dashboard sections.

Build in FlowCopy Anchor Link

Add a source read or reusable saved query. Choose its result step, declare parameters and map its fields to components. Native queries need an explicit Run when their output fields cannot be inferred from metadata.

The canvas shows data dependencies, interactions and referenced workflows. A data flow is not another rendered component. Inspecting a specific chart focuses its dependencies; showing the full view reveals its siblings.

Use the canvas menu for source/component creation and display options. Expanding a reference inspects the same saved item. It does not duplicate its definition.

Arrange in DesignCopy Anchor Link

Use Design to position and resize components. The shared component inspector edits content, appearance, actions and rules. A form or detail field editor retains its parent context and Back navigation.

Choose content-driven height for collections that should grow with their records. A fixed dashboard placement needs enough height for the title, legend, axes and data. Preview both wide and narrow layouts.

Bind inputs deliberatelyCopy Anchor Link

Declare input names, types, defaults and required values. Map those inputs to dataset parameters. For example, an accountId input can restrict all reads belonging to an account section.

Bindings can also read a selection, form value or earlier dataset result. Those dependencies determine when a read can run. A required record input keeps dependent reads waiting until a valid selection exists.

Search pickers and manual entry are input presentations. They do not authorize a record. Use the source/workflow permission model and database business rules for that boundary.

Preview and saveCopy Anchor Link

Use the selected view/component's preview action to inspect its configured content. Supply required inputs and explicitly load live data when needed. Preview can display real data; it is not a sandbox for workflow effects.

Saving configuration and loading data are separate. A button or form only runs its workflow when explicitly triggered. Test effects against an appropriate test destination before publishing them.

Reuse and composeCopy Anchor Link

Place the saved view on a dashboard or open it through an interaction. An embedded view component can compose existing views with explicit parameter mappings. Shared datasets should stay shared rather than being copied to each metric.

Existing multi-component definitions remain valid. Organize into sections uses dependency analysis to split independent sections while keeping shared calculations and controls together. Review the resulting sections and save/publish the intended composition.