Hiding and Requiring Fields on Forms: A Customization Guide

Hiding and Requiring Fields on Forms: A Customization Guide

Hiding and Requiring Fields on Forms: A Customization Guide

This guide provides a fact-checked walkthrough of how to customize your transaction and entity forms.

This guide provides a fact-checked walkthrough of how to customize your transaction and entity forms.

This guide provides a fact-checked walkthrough of how to customize your transaction and entity forms.

7 min read

Standard NetSuite forms are designed to be comprehensive, often displaying every possible field for a given record type. However, this can lead to cluttered interfaces that slow down data entry and increase the risk of errors. Effective form customization involves hiding unnecessary fields and making critical fields mandatory to streamline workflows and improve data quality. This guide provides a fact-checked walkthrough of how to customize your transaction and entity forms.


The Goal of Form Customization

By tailoring forms to your specific business processes, you can:

  • Improve Efficiency: Users see only the fields they need, allowing for faster and more intuitive data entry.

  • Enhance Data Integrity: By making key fields mandatory, you can ensure that essential information is captured every time a record is saved.

  • Reduce User Error: Hiding irrelevant fields minimizes the chance of users entering data in the wrong place.


How to Customize a Form

First, you must navigate to the correct form customization page.

  1. Access the Form List:

  • For transactions (e.g., Sales Orders, Invoices): Go to Customization > Forms > Transaction Forms.

  • For entities (e.g., Customers, Vendors): Go to Customization > Forms > Entry Forms.

  1. Select and Edit the Form: Find the form you wish to modify. If it is a standard NetSuite form, you must first click Customize to create an editable copy. If it is already a custom form, click Edit.

Customizing Header Fields

Header fields (or "body fields") appear once at the top of the record. You configure these on the Screen Fields subtab.

Setting

Description

Show

The primary control. If this box is checked, the field is visible on the form. Uncheck it to hide the field.

Mandatory

If checked, users cannot save the record without entering a value in this field. Use this setting judiciously.

Display Type

Controls how the field appears: Normal (editable), Inline Text (read-only), or Disabled (visible but grayed out).

Label

Allows you to override the default field name with a custom label that will only be used on this specific form.


Customizing Line-Item Fields

Line-item fields (or "column fields") appear in the sublists at the bottom of a record (e.g., the Items sublist on a Sales Order). You configure these on the Sublist Fields subtab.

  1. Select the sublist you wish to modify (e.g., "Items").

  2. A list of all available columns for that sublist will appear.

  3. Check or uncheck the Show box to control the visibility of each column.

  4. You can also drag and drop the columns to reorder them.


Strategic Form Design

Simply showing or hiding fields is just the first step. Good form design involves creating role-specific forms that are tailored to the tasks of different user groups.

Example: A Sales Order Form Strategy

  • Sales Team Form: Shows customer and pricing information but hides accounting and warehouse fields.

  • Warehouse Team Form: Shows shipping details and item quantities but hides all financial information.

  • Finance Team Form: Shows all fields, with a particular focus on payment terms, class, and department, which might be mandatory for this role.

To implement this, you create a separate custom form for each team and then assign it to the appropriate roles on the Roles subtab of the form customization page.


Best Practices

  • Test in Sandbox: For significant changes, always build and test your new forms in a sandbox environment before deploying them to production.

  • Be Cautious with "Mandatory": Overusing the mandatory setting can frustrate users and lead them to enter placeholder data just to save a record. Only make a field mandatory if it is truly essential for every single transaction.

  • Consult Your Users: Before hiding a field, confirm with the users of that form that it is not needed for their process. A field that seems irrelevant to you might be critical for someone else.

Communicate Changes: Always notify your users before you roll out changes to the forms they use every day. This prevents confusion and reduces support requests.

Standard NetSuite forms are designed to be comprehensive, often displaying every possible field for a given record type. However, this can lead to cluttered interfaces that slow down data entry and increase the risk of errors. Effective form customization involves hiding unnecessary fields and making critical fields mandatory to streamline workflows and improve data quality. This guide provides a fact-checked walkthrough of how to customize your transaction and entity forms.


The Goal of Form Customization

By tailoring forms to your specific business processes, you can:

  • Improve Efficiency: Users see only the fields they need, allowing for faster and more intuitive data entry.

  • Enhance Data Integrity: By making key fields mandatory, you can ensure that essential information is captured every time a record is saved.

  • Reduce User Error: Hiding irrelevant fields minimizes the chance of users entering data in the wrong place.


How to Customize a Form

First, you must navigate to the correct form customization page.

  1. Access the Form List:

  • For transactions (e.g., Sales Orders, Invoices): Go to Customization > Forms > Transaction Forms.

  • For entities (e.g., Customers, Vendors): Go to Customization > Forms > Entry Forms.

  1. Select and Edit the Form: Find the form you wish to modify. If it is a standard NetSuite form, you must first click Customize to create an editable copy. If it is already a custom form, click Edit.

Customizing Header Fields

Header fields (or "body fields") appear once at the top of the record. You configure these on the Screen Fields subtab.

Setting

Description

Show

The primary control. If this box is checked, the field is visible on the form. Uncheck it to hide the field.

Mandatory

If checked, users cannot save the record without entering a value in this field. Use this setting judiciously.

Display Type

Controls how the field appears: Normal (editable), Inline Text (read-only), or Disabled (visible but grayed out).

Label

Allows you to override the default field name with a custom label that will only be used on this specific form.


Customizing Line-Item Fields

Line-item fields (or "column fields") appear in the sublists at the bottom of a record (e.g., the Items sublist on a Sales Order). You configure these on the Sublist Fields subtab.

  1. Select the sublist you wish to modify (e.g., "Items").

  2. A list of all available columns for that sublist will appear.

  3. Check or uncheck the Show box to control the visibility of each column.

  4. You can also drag and drop the columns to reorder them.


Strategic Form Design

Simply showing or hiding fields is just the first step. Good form design involves creating role-specific forms that are tailored to the tasks of different user groups.

Example: A Sales Order Form Strategy

  • Sales Team Form: Shows customer and pricing information but hides accounting and warehouse fields.

  • Warehouse Team Form: Shows shipping details and item quantities but hides all financial information.

  • Finance Team Form: Shows all fields, with a particular focus on payment terms, class, and department, which might be mandatory for this role.

To implement this, you create a separate custom form for each team and then assign it to the appropriate roles on the Roles subtab of the form customization page.


Best Practices

  • Test in Sandbox: For significant changes, always build and test your new forms in a sandbox environment before deploying them to production.

  • Be Cautious with "Mandatory": Overusing the mandatory setting can frustrate users and lead them to enter placeholder data just to save a record. Only make a field mandatory if it is truly essential for every single transaction.

  • Consult Your Users: Before hiding a field, confirm with the users of that form that it is not needed for their process. A field that seems irrelevant to you might be critical for someone else.

Communicate Changes: Always notify your users before you roll out changes to the forms they use every day. This prevents confusion and reduces support requests.

Ready to Work Together?

Ready to Work Together?

Ready to Work Together?

Let us talk about your NetSuite challenges and how we can help. No pressure, no sales pitch. Just a straightforward conversation.

Let us talk about your NetSuite challenges and how we can help. No pressure, no sales pitch. Just a straightforward conversation.

Author

Michael Strong

Michael Strong

Founder & Principal Architect

Founder & Principal Architect

Tags

Read More

Read More