Discussions
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Don’t miss your chance to meet our SuiteGurus—NetSuite Support professionals and subject matter experts with extensive experience in select product areas, including OneWorld, Advanced & Basic Accounting, Supply Chain Management, Receivables & Payables, CRM, Account Administration, and the SuiteCloud Platform. Full Conference attendees can prebook exclusive 30-minute one-on-one sessions for your product questions.
Spots are limited! Register through your Agenda Builder and find SuiteGuru under Agenda Enhancements.
2022.1 behavior of setSublistValue changes
This isn't really a question, because I know there's no answer. But I felt obliged to tell you anyway.
In a suitelet (suiteScript 2.1) I have:
ifLineSublist.setSublistValue({
id: 'itemctncnt',
line: lineIdx,
value: calcCartonCount(ifData.item_sublist[lineIdx].quantity, itemData)
});
That code ran just fine at 5PM yesterday in our sandbox. Now it pukes with
"type": "internal error",
"code": "INVALID_FLD_VALUE",
"details": "You have entered an Invalid Field Value 339.0 for the following field: itemctncnt",
The fix is to change the value property to
value: calcCartonCount(ifData.item_sublist[lineIdx].quantity, itemData).toString()
Hint: It's an integer. The function being called uses parseInt() to make sure it returns an integer. It used to automatically cast an integer to a string properly, and now it doesn't. Expect lots of production code to break, at great expense to you and your customers. Congratulations!