WHAT YOU WILL LEAVE WITH

Connect a selector and detail widgets so users see the intended related records.

Model the Data Before the Page

Grist documents selection-driven links between widgets, including same-record and filter linking. The source widget acts as a selector; the receiving widget shows the related context. A visually adjacent pair of widgets is not automatically linked.

For a hypothetical customer service page, a Customers table can select one customer while a Projects table shows that customer’s projects. A separate contact card could show details for the selected customer. Decide which record each widget represents before arranging the layout.

Documentation: Grist: Linking Widgets

Make Selection Direction Unambiguous

The useful question is “when I choose this record, what should change?” Write that sentence for every connection. Avoid a layout where selecting a project unexpectedly changes the customer selector unless that behavior is intentional and understandable.

A customer with no projects is a necessary example. An empty project panel should mean there are no matching projects for that selection; it should not make the operator wonder whether the page failed to load. Add nearby explanatory text in the page design if the distinction matters.

Check a Small Master–Detail Workflow

Create synthetic customers Aster and Beacon. Give Aster two projects and Beacon one. Add Cedar with no projects. These names and counts are an illustrative fixture, not a test result from this project.

  1. Confirm every project references its intended customer.
  2. Create the customer selector widget.
  3. Add a project widget and choose the documented selection link.
  4. Select Aster, Beacon and Cedar in turn.
  5. Compare the displayed projects with the expected relationship list.
  6. Change the selected project and check whether unrelated widgets move unexpectedly.

Documentation: Grist: Linking Widgets

Keep Interface Filtering Separate From Access

A useful master–detail display helps users focus, but the layout does not itself express who is entitled to read every underlying record. Treat access as a separate requirement and validate it with the appropriate sharing and access-rule configuration.

If the wrong projects appear, inspect the selected source widget, target table and relationship column before changing records. A direction or relationship mismatch can look like missing data. Keep the data model intact while isolating the display problem, then confirm the corrected page against all three fixture customers.

WORKING EXAMPLE / SYNTHETIC DATA

Hypothetical selection-to-detail contract

This is an illustrative worksheet to adapt to your own evaluation. It is not a measured product test or a claim about results in your installation.

Hypothetical selection-to-detail contract
Selected CustomerExpected ProjectsInterpretation
AsterA-1 and A-2Two related project records
BeaconB-1One related project record
CedarNoneValid empty relationship
No intended selectionDefined by page designDo not assume an empty panel is an error

A linked page works when a selection leads to a predictable record set, including a deliberately checked empty case.

Inspect the official interface evidence

These previously captured interfaces provide orientation. Their versions and dates are distinct from the documentation review above.

INTERFACE SPECIMENS / ANNOTATED

Inspect the interface, with its context.

Open a specimen to see the source image and the observations it supports. A vendor demonstration is distinct from a self-hosted installation.

GristOfficial public demo · Demo identifies v1.7.20
Official public demoDemo identifies v1.7.20
Grist official Lightweight CRM demo showing a contact list, selected contact card and interactions table with fictional sample data.
The official Lightweight CRM template combines a contact grid, a detail card and an interactions table. The demo identifies its sample data as fictional. This hosted v1.7.20 demo is separate from the v1.7.21 core licence check.
  1. Contact gridThe left widget lists sample companies and follow-up tasks.
  2. Detail cardThe upper-right widget presents fields for the selected contact.
  3. Related interactionsThe lower-right widget displays the sample interaction history.
Interface and sample template © Grist Labs. Browser capture by OwnStack Atlas; numbered annotations are separate overlays. Reviewed 25 October 2026.Open official source ↗Enlarge original ↗
SOURCE REGISTER

Check the facts and their boundaries.

Official documentation supports the product statements. The evaluation procedures and synthetic examples are editorial guidance. We have not independently run the installation, migration or recovery procedures described here.

Grist: Linking WidgetsPrimary source ↗

Selection-driven same-record and filter linking. Reviewed 2026-11-01.