A field required when another holds a value
The customer asks: A field must be filled when another field holds a value
- Verdict: Ready, with limits (1)
- Door: Save rules · area: Documents and print › Numbering and checks on save
- Recipe: Save rules
- Sample: none yet
- Checked: carried 2026-10-16 · not re-run
What you build
A save rule of kind required when, held on every save: Desk, imports and API writes. (The shop's own mandatory depends on is checked in the Desk form only.)
Limits
- On a till sale and the till close a save rule only flags, never refuses.
Tell the customer
The record cannot be saved without the field when the other holds a value.
What next
- Tell the customer the 1 limit above, and write it into the proposal.
- Start from: Save rules.
- Build and test it on your sandbox (request one if you have none; what is on it).
- Run the checks: your own tests, the kit's checks and the money kit's release gate (testing and release).
- Release through the customer's own release gate (14. Testing and release); an app other shops install goes through the App library.
Related needs
- A code must follow our pattern — Ready, with limits (1)
- A field filled in from other fields when the record is saved — Ready, with limits (2)
- Fields cannot be changed once the document is approved — Ready, with limits (1)
- The same item or code may not appear twice in one document — Ready, with limits (1)
Start a project shortlist with this need · Put it in your blueprint · Every need