Challege: When a user runs a Saved Search and receives a “Field Not Found” error, it typically stops them in their tracks and generates a support request because they can clearly see the field on the record.
Tip: Most likely when this happens, you are dealing with a custom fields. To ensure custom fields are visible in Saved Search results, whether it is a custom fields on a NetSuite record (i.e. Customer) or a custom record, be sure that the appropriate access level is defined in the “Level for Search/Reporting.” The users or roles that need access to the field in the search results need to be accounted for in the “Level for Search/Reporting” dropdown and permissions table.
If this occurs with a standard NetSuite field, make sure that the role and/or user has permission to the record where the field is on (e.g. To view a Customer Record field, the role should have access to the Customer Record).
Understanding and fixing a “Field Not Found” error saves valuable time, quickly gets users back up and running, and allows searches to be created more efficiently. In most of these instances, understanding what the custom fields will be used for saves you time when setting up. And unless you know the field should not be available in search or reporting, it should default to being always available.