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.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
No Limits. Just possibilities.
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Join us for complimentary one-day events around the world and step into a future fueled by AI and limitless potential. Explore new breakthroughs, sharpen your skills, and connect with experts who are shaping what’s next. Experience bold keynotes, interactive learning, and connections that span the global NetSuite community. Discover what's next at SuiteConnect Tour 2026.
Try Intelligent Payment Automation – Fee Free For Your First Month
Intelligent Payment Automation, powered by BILL (aka Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
Intelligent Payment Automation, powered by BILL (aka Bill.com), lets you automate payments, manage vendor details, and bank account information within NetSuite.
The SuiteApp is available to organizations based in the U.S. with a valid U.S. address, or to global customers (except Canada, China, and Japan) with U.S. business subsidiaries. It only supports payments to vendors operating in the United States.
For more information, visit this thread.
Community Articles: What Topic Should We Cover Next? Your idea could be our next feature—drop your suggestion now and spark the next big discussion!
REGEXP_REPLACE not working as expected in SuiteScript search
Hello,
I have a strange problem with a scheduled script I'm working on where REGEX_REPLACE does not seem to work correctly.
When used in a saved search in the UI the expression works as expected. But when using the exact same expression for a nlobjSearchColumn, it does not perform any replacements.
[CODE]columns.push(new nlobjSearchColumn('formulatext', null, 'group')
.setFormula("CASE WHEN {item.type} = 'Kit/Package' THEN REGEXP_REPLACE({item.memberitem}, '^([^:]+) : \1.*$', '\1') ELSE COALESCE({item.parent},{item}) END")
.setSort());[/CODE]
The reason for replacing like this is that we use multiple item records for different versions of the same item, e.g. 18751-1, 18751-2, 18751-3 which all have the parent item 18751. For demand planning I need to summarize our sales across all versions of the same item. However {item.memberitem} will come up as e.g. "18751 : 18751-2".
I have a strange problem with a scheduled script I'm working on where REGEX_REPLACE does not seem to work correctly.
When used in a saved search in the UI the expression works as expected. But when using the exact same expression for a nlobjSearchColumn, it does not perform any replacements.
[CODE]columns.push(new nlobjSearchColumn('formulatext', null, 'group')
.setFormula("CASE WHEN {item.type} = 'Kit/Package' THEN REGEXP_REPLACE({item.memberitem}, '^([^:]+) : \1.*$', '\1') ELSE COALESCE({item.parent},{item}) END")
.setSort());[/CODE]
The reason for replacing like this is that we use multiple item records for different versions of the same item, e.g. 18751-1, 18751-2, 18751-3 which all have the parent item 18751. For demand planning I need to summarize our sales across all versions of the same item. However {item.memberitem} will come up as e.g. "18751 : 18751-2".
0