Scenario
A custom transaction body field appears on a transaction form, but users cannot edit it.
Common symptoms include:
- The field is visible but grayed out.
- Users can edit the field on some transactions but not others.
- The field was previously editable and suddenly became read-only.
- Administrators can edit the field, but standard users cannot.
This issue is common in environments using workflows, field sourcing, custom forms, or SuiteScript customizations.
Solution
Review the customization layers that can force a transaction body field into a read-only state.
Common causes include:
- Field Display Type
- Open the custom field configuration.
- Verify the display type is not set to:
- Disabled
- Inline Text
- Read Only
- Custom Form Configuration
- Review the transaction form settings.
- Some forms override field accessibility differently than others.
- Test using a standard transaction form where possible.
- Role Permissions
- Confirm the user’s role has permission to edit the transaction and related fields.
- Certain permission restrictions can make fields read-only for non-admin users.
- Workflow Actions
- Review active workflows affecting the transaction type.
- Workflow states or actions may lock fields conditionally during approval or processing stages.
- SuiteScript Customization
- Client scripts and user event scripts may disable fields dynamically.
- Review deployed scripts affecting the transaction.
- Field Sourcing or Formula Logic
- Sourced or formula-driven fields may not allow manual edits depending on configuration.
- Transaction Status
- Approved, closed, fulfilled, or locked transactions may restrict field editing automatically.
Notes
A field can appear editable at the customization level but still become read-only due to workflows, scripts, transaction status, or role restrictions.
When troubleshooting:
- Test using the Administrator role.
- Compare behavior across forms and roles.
- Review workflow states and script deployments.
- Test on both new and existing transactions.
Testing changes in a sandbox environment is recommended before modifying active transaction customizations in production.