Bundle updates can change or add fields, forms, scripts, workflows, or other customization components. After a bundle update, custom forms should be reviewed to confirm that users can still enter, review, and save records correctly.
Validating custom forms after bundle updates helps reduce user disruption and catch issues before they affect business processes.
Scenario
An admin installs or updates a bundle in NetSuite.
After the update, users may report issues such as:
- fields missing from a custom form
- new fields appearing unexpectedly
- required fields blocking record save
- form layout changes
- scripts or workflows behaving differently
- role-specific forms not showing the right fields
Even if the bundle update completes successfully, related forms may still need review.
Solution
Review and test affected custom forms after the bundle update.
Focus on forms connected to the bundle components, especially forms used by high-volume users or critical business processes.
What to Validate
Field Visibility
Confirm that important fields still appear on the correct forms.
Check whether:
- required fields are visible
- newly added fields appear where expected
- old fields were not removed unintentionally
- hidden fields are still hidden where needed
Required Field Behavior
Test whether users can still save records.
Review whether the update introduced new required fields or changed field behavior in a way that blocks normal entry.
Form Layout
Check whether the form is still easy to use.
Review:
- tabs
- subtabs
- field groups
- field order
- line-level fields
- buttons or custom actions
A bundle update may add fields that need to be repositioned.
Role-Based Access
Test with the roles that use the form.
A form may work for an administrator but fail for a standard user if permissions, role access, or form assignments are different.
Scripts and Workflows
If the bundle includes scripts or workflows, confirm that they still behave correctly on the affected forms.
Check whether:
- scripts trigger on the expected forms
- workflows still show, hide, or update fields correctly
- validation messages appear only when intended
- execution logs show errors after testing
References
- SA: SuiteBundler Overview (8082)
- SA: Custom Forms (10117)
Notes
- Test in sandbox before applying bundle updates to production when possible.
- Review forms used by critical business processes first.
- Test with the same roles that users will use.
- Check both create and edit scenarios.
- Review scripts and workflows connected to the updated components.
- Document any form changes made after the bundle update.
- Communicate important form changes to affected users.
Summary
Custom forms should be reviewed after bundle updates to confirm that fields, layouts, required settings, scripts, workflows, and role access still behave as expected. Even when the bundle update is successful, form-level testing helps catch issues that users may experience later.
A short validation review can help reduce production disruption and keep business processes running smoothly.
Share your insights and experiences in the NetSuite Admin Corner.
