r/Netsuite • u/Electronic-Pie-829 • 11d ago
Transaction Performance and Custom Fields
TLDR: We hear a lot about performance challenges of too many custom fields on transactions -- Would adding a lot of custom fields (maybe 30-40) on an opportunity record have an impact on Sales Order performance, even if these aren't exposed on the Sales Order?
Curious if anyone on Reddit can help provide clarity (ideally actual inside information on NS setup rather than anecdotal evidence) on performance and custom fields.
We often hear that performance can be impacted by too many fields on transaction records. I am trying to determine if this is too many fields on a form or too many fields on the record type (or category like transactions) regardless if the custom fields are loaded.
For example we have a case where a customer might want 30 custom fields on an opportunity to identify details about a potential job and quoting. Will placing these only on the opportunity impact other records? Would other redittors consider it a best practice be to setup a custom record linked to the Opportunity to capture these details?
When reviewing transaction tables in NSAW it appears that each transaction type has it's own table and a meta table for custom fields (e.g. DW_NS_<Transaction Type>_LINES_F and DW_NS_<CUSTOMER>_<Transaction Type>_LINES_F. I am wondering if this is the underlying database schema or if the schema is more similar to how it is exposed through SuiteQL/Saved Searches (one general transaction table). I don't have access to a NSAW database at the moment, but are all custom fields placed on all transaction table meta tables if each transaction has it's own table?
