Scenario
An administrator attempts to hide a transaction field using form customization, but the field continues to appear on the transaction.
Common symptoms include:
- The field is marked hidden on the custom form but still displays.
- The field disappears for some users but not others.
- The field reappears after save or page refresh.
- The field cannot be removed from certain transaction types.
This is a common issue in NetSuite because some transaction fields are controlled by system behavior, workflows, scripts, or feature dependencies.
Solution
Review the different customization layers that can override or prevent field hiding behavior.
Common causes include:
- Standard NetSuite Required Fields
- Certain standard transaction fields cannot be fully hidden because they are required by NetSuite functionality or enabled features.
- Custom Form Configuration
- Verify the field is hidden on the correct custom form.
- Users may be accessing a different preferred form than expected.
- Field Display Settings
- Some fields may be configured as:
- Normal
- Disabled
- Inline Text
- Instead of fully hidden.
- Role-Specific Form Behavior
- Different roles may use different forms or personalization settings.
- Test using the same role experiencing the issue.
- Workflows
- SuiteFlow actions can dynamically show fields during record processing or state transitions.
- SuiteScript
- Client scripts and user event scripts may force fields to display regardless of form settings.
- Feature Dependencies
- Certain enabled features automatically expose related transaction fields.
- Examples include:
- Multi-Location Inventory
- Departments, Classes, or Locations
- Tax or shipping functionality
- Sublist or System-Controlled Fields
- Some line-level transaction fields are system-controlled and cannot be fully hidden through standard customization.
Notes
Hiding a field at the form level does not always guarantee the field will remain hidden in every context. Workflows, scripts, role preferences, and enabled features can all override display behavior.
When troubleshooting:
- Test using the Administrator role.
- Verify which form is actually being used.
- Compare behavior across roles and subsidiaries.
- Review active workflows and scripts affecting the transaction.
- Test on a standard form for comparison.
Testing changes in a sandbox environment is recommended before modifying production transaction forms.