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!
Update your Profile with your Support type to get your Support Type badge.
Don't miss out on our Question of the Week! You only have until tomorrow, October 30, 2025, 2PM ET to comment your answers and earn rewards! Click here for more details.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
NetFlex faults descriptions
Hi All!
A short introduction first - our team is working on NetSUite-Outlook integration, invilving NetFlex web services. Sometimes we face issues that are likely to appear on this forum
Thus the first one follows...
NetFlex fault descriptions seem to be processed ambiguously.
It appeared that NetSuite could response using different types of objects while writing elements nested inside detail element.
For example in case of supplying wrong credentials it responds like this:
<invalidCredentialsFault xmlns="urn:faults_1_3.platform.webservices.netsuite.com">
<code>INVALID_LOGIN_CREDENTIALS</code>
<message>....</message>
</invalidCredentialsFault>
0