ANS-0517 · WEB SERVICES & INTEGRATIONS
How Does Transaction Complexity Impact NetSuite REST API Performance?
NetSuite integration performance, particularly with REST APIs, is significantly influenced by the volume of data and the number of fields processed per transaction.
Short answer
NetSuite integration performance is directly tied to transaction complexity, including the number of line items and fields. While basic transactions are quick, complex ones can take longer. For optimal performance, especially with high volumes, leveraging NetSuite REST APIs and batching operations is crucial to mitigate processing times.
Scenario
Organizations integrating external systems with NetSuite often encounter varying performance when processing transactions. A common concern arises when attempting to insert or update a large number of records, such as invoices, through web services. The question is how the complexity of these transactions affects the overall integration speed and efficiency.
Solution
The performance of NetSuite integrations, particularly when utilizing REST APIs, is directly dependent on the amount of information passed within each record. This includes factors such as the number of line items, custom fields, and related sublist data. Historically, observations indicated that while basic transactions processed quickly, complex transactions with many fields could take up to one second per transaction insertion. For example, processing 900 invoices under such conditions could extend to approximately 15 minutes. To optimize performance for high-volume integrations and complex transactions, it is strongly recommended to leverage NetSuite REST APIs and implement batching operations. This approach allows for more efficient data transfer and processing, significantly improving throughput compared to older integration methods.
Expert NetSuite Support
Need help with this NetSuite issue?
Web Services & Integrations consulting and configuration support