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.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Keep an eye out for upcoming NetSuite events, including meetups, workshops, and webinars. These sessions are a great way to connect with peers, learn from experts, and stay current on the latest NetSuite updates and best practices. Registration links are provided in each event.
Save $30 - limited to first 1,000 registrants
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
Join the NetSuite community to innovate, connect, and discover what’s next.
SuiteWorld brings thousands of innovators, builders, and leaders together to learn, connect, and shape what’s next. This October, explore how to build a stronger foundation for growth through inspiring keynotes, major product reveals, hands-on sessions, and unforgettable moments—all in one place for our biggest event of the year. Register now
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