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.
Please note that on Saturday, April 18, 2026, at 8:00 PM Pacific Time, our Case Management System will undergo a scheduled maintenance for approximately 15 minutes. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
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