Interesting error: If a Client script references a...
# suitescript
e
Interesting error: If a Client script references a custom module that calls currentRecord.setValue, the first such call registers an error due to strict mode. However, if I include that currentRecord.setValue in the client script itself, no error. Any explanation to this? Seems like an NS issue…
Copy code
NLAPI.jsp?JSP_VER=1&NS_VER=2023.2&minver=16&locale=en_US&buildver=31123:4362 TypeError: 'caller', 'callee', and 'arguments' properties may not be accessed on strict mode functions or the arguments objects for calls to them
    at nsapiQueryScript (NLAPI.jsp?JSP_VER=1&NS_VER=2023.2&minver=16&locale=en_US&buildver=31123:4340:56)
    at nlobjContext.getTotalUsage (NLAPI.jsp?JSP_VER=1&NS_VER=2023.2&minver=16&locale=en_US&buildver=31123:3804:22)
    at nlobjContext.getRemainingUsage (NLAPI.jsp?JSP_VER=1&NS_VER=2023.2&minver=16&locale=en_US&buildver=31123:3841:70)
    at nsapiCheckUsage (NLAPI.jsp?JSP_VER=1&NS_VER=2023.2&minver=16&locale=en_US&buildver=31123:4487:28)
    at nlapiRequestURL (NLAPI.jsp?JSP_VER=1&NS_VER=2023.2&minver=16&locale=en_US&buildver=31123:2819:5)
It turns out one of my modules referenced has
use strict
but still the error is in Netsuite’s code
Update: digging in to the nsapiQueryScript error, seems like NS knows about this bug