These are illustrative scenarios showing how the products are used, not customer case studies.
The same sequence, twice
Today
- Add one option
- Edit the back-end list
- Edit the front-end list
- Lookup table forgotten
With SynaptaGrid
- Field points at a source
- Options resolve on read
- Preview before saving
- One list, read everywhere
The situation
Adding a status means editing an enumeration in the back end, a matching list in the front end, and a lookup table that some report still reads. Miss one and it surfaces as a validation error nobody can reproduce, or a dropdown offering a value the API refuses.
How it is approached
A choice field carries where its options come from: a fixed list, another record type, another field’s list, a registered database, or a REST endpoint. A live source resolves when the field is read, so it reflects the current data rather than a copy taken when the field was defined. What a source returns is previewed before the field is saved, and a long list loads as you type instead of being fetched up front.
What changes
One list, read by the form, the validation and the API alike. Adding an option becomes a change in the system that owns it, not a coordinated edit in three places.