Scenario
A custom checkbox field is checked during record creation or editing, but after saving the record, the checkbox becomes unchecked again.
This issue commonly occurs on transaction forms, entity records, and custom records where the checkbox appears to save correctly during editing but does not retain the selected value afterward.
Solution
Review the field configuration and any custom logic that may be resetting the checkbox value during save or record processing.
Common causes include:
- Field Sourcing or Defaulting Logic
- Check whether the field is sourced from another field or record.
- Review default values configured on the custom field.
- Workflow Actions
- Review active workflows on the record type.
- A workflow may be setting the checkbox value conditionally during before-submit or after-submit processing.
- Client or User Event Scripts
- Check SuiteScript deployments associated with the record.
- Scripts may overwrite the checkbox value during save operations.
- Field Display or Store Value Settings
- Verify the field is configured to store values properly.
- Certain field configurations or formula-based fields may not persist user-entered values.
- Form-Level Behavior
- Test using a standard form instead of a custom form.
- Some custom forms may contain display or sourcing configurations that affect field behavior.
Notes
Checkbox fields can be affected by multiple layers of customization simultaneously, including workflows, sourcing, scripts, and form logic. Even if the checkbox appears editable, another process may overwrite the value before the record finishes saving.
When troubleshooting:
- Test using the Administrator role.
- Disable workflows temporarily in a sandbox environment.
- Review execution logs for scripts affecting the record.
- Compare behavior across forms and roles.
Testing in a sandbox is strongly recommended before modifying active customizations in production.