If your NetSuite integrations depend on concurrent SOAP web service requests, it’s important to understand recent governance changes that impact how these requests are managed. These updates specifically affect the Concurrent Web Service User setting on user records, particularly for accounts utilizing SuiteCloud Plus licenses.
Key Governance Updates
Before NetSuite 2017.2, accounts with SuiteCloud Plus licenses were guaranteed 10 concurrent SOAP requests per designated web service user. This provided a predictable limit for parallel requests, ensuring stability and performance.
However, with the governance update in 2017.2, key changes include:
- The 10 concurrent SOAP request guarantee per user has been removed.
- All SOAP and REST requests now contribute to the overall account-level governance limit.
- A designated concurrent web service user’s ability to execute 10 parallel SOAP requests now depends on other SOAP and REST requests being processed simultaneously.
- No reserved capacity is allocated to specific users, leading to a more dynamic resource allocation.
Best Practice: Shift to Token-Based Authentication (TBA)
To minimize service disruptions and optimize API performance, NetSuite recommends using Token-Based Authentication (TBA) instead of designating a Concurrent Web Service User. TBA provides several benefits, including:
- No manual user assignments for concurrent web services.
- Stronger security by reducing reliance on user credentials.
- Scalability with seamless authentication, bypassing governance restrictions tied to specific users.
Next Steps for NetSuite Users
If your integration relies on concurrent SOAP requests, take the following actions:
- Evaluate your web service calls to determine the impact of these governance changes.
- Implement Token-Based Authentication (TBA) to enhance reliability and security.
- Monitor your account’s governance limits to effectively manage SOAP and REST requests.
- Optimize API usage by leveraging asynchronous processing and batching where possible.
By adapting to these changes and switching to TBA, NetSuite users can ensure their integrations remain efficient, scalable, and compliant with the latest governance policies.