Unused custom forms can make a NetSuite account harder to manage, but deleting them too quickly can create risk. A form may look unused but still be assigned to a role, referenced in documentation, used by a small team, or connected to a business process.
Archiving or restricting an unused form first is often safer than deleting it immediately.
Scenario
An admin reviews custom forms and finds several that appear outdated.
Examples may include:
- old transaction forms
- duplicate entry forms
- test forms
- retired approval forms
- forms created for a previous process
- forms no longer assigned to most users
The admin wants to clean up the account, but needs to avoid disrupting users or breaking an existing process.
Solution
Review the form first, then archive or restrict access before deleting.
Instead of removing the form right away, mark it clearly as inactive, deprecated, or archived, depending on the available setup and account process. This gives the admin time to confirm whether anyone still needs the form.
What to Check Before Archiving
Form Usage
Confirm whether the form is still being used by any team or role.
Check:
- assigned roles
- preferred forms
- recent user feedback
- related business processes
- documentation or training references
Field Layout and Required Fields
Review whether the form contains fields or layout behavior that differs from other forms.
A form may be old but still used because it shows certain fields or hides others for a specific process.
Scripts and Workflows
Check whether any scripts or workflows depend on the form.
Examples:
- workflow conditions based on custom form
- scripts that check the customform field
- form-specific validation logic
- role-based form behavior
Removing the form too quickly may affect automation.
User Access
Confirm whether users can safely move to another form.
If the form is still assigned to a role, update form assignments carefully and test the replacement form before removing access.
Archiving Approach
A safe cleanup approach may include:
- rename the form with an archive label
- remove it as the preferred form
- restrict access to only admin roles
- document why it was archived
- monitor whether users report any issue
- delete only after confirming it is no longer needed
Example form name:
ARCHIVED - Old Vendor Review Form
This makes the status clear to other admins.
Example: Archive an Old Vendor Review Form
An admin finds an old form named:
Old Vendor Review Form
Instead of deleting it right away, the admin archives it first.
Navigation
NetSuite:
Go to:
Customization > Forms > Entry Forms
Or, for transaction forms:
Customization > Forms > Transaction Forms
NetSuite Next:
Click Explore (hamburger icon in the bottom left corner beside the home button). In the menu, go to Customization > Forms > Entry Forms or Transaction Forms. Then, on the next page, click on the needed Form
3-Step Archive Approach
Step 1: Rename the Form
Change the form name to:
ARCHIVED - OLD Custom - Assembly Build Form
This makes it clear that the form should no longer be used.
Step 2: Remove or Restrict Access
Make sure the form is no longer the preferred form for users.
If needed, limit access to admin roles only.
Step 3: Document and Monitor
Document why the form was archived, then monitor whether any users, workflows, or scripts still depend on it before deleting later.
Result
The form is clearly marked as archived, removed from normal use, and kept temporarily for safe review.
References
- SA: Custom Forms (Answer Id: 10117)
Notes
- Do not delete forms without checking role assignments.
- Review workflows and scripts that may reference the form.
- Rename or restrict old forms before deleting them.
- Keep documentation of why a form was archived.
- Test replacement forms with the affected roles.
- Clean up test or duplicate forms carefully.
- Use sandbox first when changing forms used by critical processes.
Summary
Archiving unused forms before deleting them helps reduce cleanup risk. By reviewing form usage, role assignments, workflows, scripts, and replacement forms first, admins can avoid disrupting users or removing something that still supports a process.
A cautious archive-first approach keeps the account cleaner while giving teams time to confirm that the form is truly no longer needed.
Disclaimer: The sample code described herein is provided on an "as is" basis, without warranty of any kind, to the fullest extent permitted by law. Oracle + NetSuite Inc. does not warrant or guarantee the individual success developers may have in implementing the sample code on their development platforms or in using their own Web server configurations.
Oracle + NetSuite Inc. does not warrant, guarantee or make any representations regarding the use, results of use, accuracy, timeliness or completeness of any data or information relating to the sample code. Oracle + NetSuite Inc. disclaims all warranties, express or implied, and in particular, disclaims all warranties of merchantability, fitness for a particular purpose, and warranties related to the code, or any service or software related thereto.
Oracle + NetSuite Inc. shall not be liable for any direct, indirect or consequential damages or costs of any type arising out of any action taken by you or others related to the sample code.
Share your insights and experiences in the NetSuite Admin Corner.
