How to Display Non-Stored NetSuite Fields in Saved Searches?

Non-stored fields in NetSuite are not directly accessible for reporting in saved searches. To make this data available, the primary approach involves creating a new custom field configured to store its value, and then populating this new field with data from the non-stored field using either a workflow or a script.Potential Solutions:

• Scheduled Workflow Solution:

1. Add a new custom field, ensuring it is set to 'Store Value = T' and can be hidden if not needed for direct user interaction.

2. Create a scheduled workflow (e.g., running every 30 minutes) to set the value of this newly created stored field from the relevant line item's non-stored field.

3. Finally, use this newly populated stored field in your saved search.

   • Line Level to Header Aggregation: For scenarios requiring aggregated line-level data at the transaction header level (e.g., calculating margins), body fields can be utilized. These body fields can incorporate saved searches that calculate values based on line-level data.
   • Directly in Search (if possible): If the data can be derived or accessed directly within the saved search criteria or results formulas, that is often the most straightforward method. If direct inclusion is not feasible, copying the data to a stored field is the next best option. Workflows can be effective for populating fields on the 'Items' or 'Expense' sublists.Final Solution Considerations:While workflows, particularly with 'Sublist Action Groups,' can populate line-level fields (especially for the 'Items' sublist), scripting offers the most flexible and robust solution for complex scenarios or when dealing with sublists beyond 'Items' or 'Expense' lines. A script can efficiently retrieve live-level data and populate line item fields as needed. In many cases, the script required for this task would be relatively simple.