Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
Slow initialization of NetSuiteService that now inherits SoapHttpClientProtocol
Hi all, hoping someone has successfully dealt with this in the SuiteTalk context.
We had noticed that when our application gets ready to call the NetSuite endpoint there is a 20+ second lag, and stepping through the code revealed that time is spent instantiating the NetSuiteService, which in recent API versions inherits the .NET class SoapHttpClientProtocol. A little research turns up that this is a common challenge with proxy classes but there's a way to effectively pre-package the Web Reference by using sgen to create the "XMLSerializers" DLL then drop that into the refs list and then the solution should use that DLL instead of having to build it each time it runs.
0