Skip to content

Checkbox, autocomplete, and tags on edit forms

Use the Demo Projects HQ contact edit page to see how App Connect restores boolean, autocomplete, and tag-style controls before editing starts.

The contact edit page fills a gap that many edit-form examples skip: not every restored control is a plain text box. This page restores a related client in autocomplete, a boolean primary-contact state, and tag-style metadata before the editor makes any changes.

Load the current contact record first.
Restore each control type from that record.
Keep boolean, autocomplete, and tag state as trustworthy as text fields.

The edit form starts from one contact record and one lookup list

Section titled “The edit form starts from one contact record and one lookup list”

sc_contact provides the saved record, and sc_clients supplies the client options that the autocomplete control can resolve against. That pairing is what makes the whole page restorable instead of leaving each control to guess its own state.

Autocomplete must restore a visible relationship, not just an ID

Section titled “Autocomplete must restore a visible relationship, not just an ID”

#contact_client shows why relationship fields need more than a hidden value. The stored client_id has to resolve back into a human-readable client option so the editor can confirm the right relationship before making changes.

Boolean state must restore the intended choice, not just a checked box

Section titled “Boolean state must restore the intended choice, not just a checked box”

#contact_primary is the clean boolean example. The page keeps both the hidden fallback value and the checkbox, but the visible control still has to reflect the saved is_primary state before the editor decides whether this contact stays primary.

Tag widgets still need the saved record before editing begins

Section titled “Tag widgets still need the saved record before editing begins”

#contact_tags is a reminder that widget-style controls are still edit fields. The Tagify input has to start from the saved contact tags so the user is refining the existing metadata instead of rebuilding it from memory.

Edit-form restoration is only complete when the less obvious controls are correct too. Autocomplete, checkbox, and tag widgets all need the same reliable source record, or the page quietly stops feeling trustworthy.

Restore relationship controls visibly, not just by hidden IDs.
Treat boolean state as real record state, not a UI afterthought.
Keep tag-style widgets aligned with the saved record before editing begins.