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.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
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!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
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.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
NetSuite - Concur connector error
Hi, we have recently started getting the following error from NetSuite when using our connector with Concur to import invoices, first happened on 19th July:
"You have entered an Invalid Field Value 0 for the following field: custbody_ava_transport"
It looks like Avalara have found a similar error but fixed it per their website, but it doesn't give details of what the error was:
https://help.avalara.com/FYHP/Connector_for_NetSuite/Avalara_Connector_for_NetSuite_Release_Notes
Concur support have been thoroughly unhelpful as usual and are pushing it back onto us. Has anyone come across this error and does anybody know how to fix it?!
0