Separating Statuses for Sales Orders vs Purchase Orders
It is very confusing for users to filter on a status field when the list of statuses includes ALL statuses for ALL transactions.
How do we segregate the various statuses so that the user is no so confused and can actually filter based on a status related to the transaction set that they querying?
In the status criteria you can type the record type such as Sales Order or Purchase Order and then all the statuses for those particular records will populate.
If you have a consolidated list of statuses shared across all transactions types, you could create a custom list field that has those statuses. Then you could map the native NetSuite status fields to the custom list/dropdown with a submit workflow or script. Once you have that in place you could add this as the filter for your searches to reduce the noise your users are currently experiencing.
Great answer, thanks Jarens.
Have you done this before?
We use custom statuses for our SO’s and PO’s. There is some marriage between the native statuses and then additional statuses in between what NetSuite provides. So it is a similar solution, but mine needed to be done to add additional stages to PO/SO’s.
Is there a way to limit the listing in the filter to be only the ones relevant to that particular transaction type being queried? Users get confused if they see ALL statuses including those NOT related to the transactions that they are querying.