This seems like a bug in the unary plus implementation. Have there been any recent patches to the scripting back-end in SuiteScript 2.1?
We have a map/reduce script that processes a queue of custom records (populated via CSV files from third-party logistics) and processes item fulfillments against orders. This script uses JavaScript unary plus to convert the imported line ID from string (because some 3PLs zero-pad it, some don't):
var numericLineSeq = +lineitem['custrecord_cm_ifqin_if_lineseq'];
Starting sometime on 9 Dec 2023, we show that the line IDs were being calculated as floats instead of integers, even though the incoming data format had not changed.
For example, the value "0007" in the custom field above would sometimes return as "7", and sometimes "7.0"--with no discernable reason on why it would return a float.
I had to rewrite the line to use Number.parseInt() to "strongly force" the value to never be a float.
// 2023.1212: hotfix to "strongly" convert line IDs to integers.
var numericLineSeq = Number.parseInt(+lineitem['custrecord_cm_ifqin_if_lineseq']);
if (Number.isNaN(numericLineSeq)) {
numericLineSeq = -1;
}
Am I missing something? (Granted the unary plus might now be redundant.)