<@U9U62UJMD> what happens if you hard code the str...
# suitescriptj
jkabot
08/22/2018, 6:12 PM@fkrauthan what happens if you hard code the string values instead of using template literals
test it with
'custrecord_123456_tran_payer'custrecord_${config.client.id}_tran_payers
stalbert
08/22/2018, 9:43 PMis this bug documented anywhere? I've heard it come up before but haven't run into it myself. Is there a reliable repro case?
stalbert
08/22/2018, 9:43 PMseeing NS behaving badly with my own eyes helps cement it in my memory 🙂
j
jkabot
08/22/2018, 9:59 PMIf you have access to the usergroup it's described here
https://usergroup.netsuite.com/users/forum/platform-areas/customization/suitescript-2-0-custom-code/427569-record-getvalue-errors-if-field-name-is-built-programatically
jkabot
08/22/2018, 10:05 PMrunnable in script debugger
Copy code
require(["N/search"], function(search) {
var dynamicValue = "foo";
var filterExpr = [
"formulanumeric: case when regexp_like({memo}, '(^|\\W)" + dynamicValue + "(\\W|$)') then 1 else 0 end",
"equalto",
"1"
];
log.debug({ title: typeof filterExpr[0] }); // string
log.debug({ title: typeof filterExpr[1] }); // string
// throws SSS_INVALID_SRCH_FILTER_EXPR_TYPE: Malformed search filter expression, first two elements must be strings.
search.create({
type: search.Type.SALES_ORDER,
filters: filterExpr,
});
var x = 0;
});s
stalbert
08/22/2018, 10:09 PMis it a problem specifically with how filter expressions are parsed, or does it seem to have a fundamental problem with the javascript implementation? filter expression syntax is a bit special because there must be some layer of Java language parsing those string expressions (and probably building Java nlobjFilter objects).
j
jkabot
08/23/2018, 2:35 PMthe author of the usergroup thread discussed problems with getValue (but the error message was less clear), so it's not limited to searches
currentRecord.getValue({ fieldId: 'custrecord_myrecord_' + month + '_quantity' }) // SSS_MISSING_REQD_ARGUMENT