ANS-0932 · CUSTOM FIELDS, RECORDS & FORMS
How to Manage Custom Transaction Field Visibility and Data Storage in NetSuite?
Understanding how custom transaction field application settings impact form visibility and data storage.
Short answer
A custom transaction field's visibility and data storage are controlled by its 'Applies To' settings. While a field might appear on a custom form, its ability to store values is active only for the transaction types specified in its application settings. Changing these settings dictates where the field functions.
Scenario
A user needs to understand how custom transaction fields behave when their 'Applies To' settings are modified. Specifically, they want to know if a field originally applied to purchases will continue to store values on purchase forms after its application is changed to sales.
Solution
Create a custom transaction field and initially apply it to purchase transactions.
Edit the relevant custom purchase form to arrange or position the field as needed.
Subsequently, edit the custom field's definition and change its 'Applies To' setting to sales transactions, removing its application to purchase transactions.
While the field may remain visible for customization on the purchase form, its functionality and data storage capabilities will be governed by its updated 'Applies To' settings. This means it will no longer store values on purchase transactions if 'Purchases' is removed from its application.
Expert NetSuite Support
Need help with this NetSuite issue?
Custom Fields, Records & Forms consulting and configuration support