Bind data

Where in the UI. Layout inspector → value source; Structure → Field bindings node; Edit filter watch list; action targets.

A binding is a typed pointer. The picker writes that pointer. The runtime resolves it against the current item (or another item if you choose “item from” a variable that holds that item’s id).

Where you bind

• Layout inspector — widget content and many style props.
• Field bindings node — write an expression into a stored field every paint.
• Edit filter — which refs, when changed, may fire “on edited” scripts.
• Actions — set-value targets.

Choosing a kind

Title and geometry → item field. Domain extras → category property (the owning category). Another item’s field → item field or category property with “item from” = an item variable that holds that item’s id (scripts set the pointer). Clock/user/theme → runtime context or theme color. Counts → item metric. Scratch → item variable.

Localized copy is not a binding

Button labels and Containd text keys live in the translations matrix. They are not DataRefs. Bind data; translate chrome. See Where data lives.

Reference: DataRef kinds and item fields.