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.
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!
Invalid SearchColumn after bundle update?
We have a bundled solution that includes a custom record that maps data from an external record to a corresponding NetSuite value. We recently made an update to that solution and we are offering it as a bundle from a completely different NS production account. When we install the updated bundle from this new account and run a flow in the customer's account we get the following error:
Error Code: SSS_INVALID_SRCH_COL
Error Message: An nlobjSearchColumn contains an invalid column, or is not in proper syntax
We tried a bunch of searches in the debugger and verified that all of the custom record fields are now invalid search column names and cannot be used in a nlobjSearchRecord request. Has anyone seen this issue before?
0