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
Filter Expressions
I have what to me seems rather odd. Lets say I want to do a regular expression type search on an itemid. The following works fine
nlapiSearchRecord('item',null,[ ["formulanumeric: REGEXP_INSTR({itemid},'^TY.0401.0.(CST|CCT)')","greaterthan","0")]])
however the following does not and throws SSS_INVALID_SRCH_FILTER_EXPR_OBJ_TYPE
var strRegEx = "^TY.0401.0.(CST|CCT)";
nlapiSearchRecord('item',null,[ ["formulanumeric: REGEXP_INSTR({itemid},'" + strRegEx + '","greaterthan","0")]]);
I need to build the regular expression dynamically and I can't see why a concatenated string passed as the first parameter of the filter expression produces a different result.
0