Hi Erick, The support team has confirmed (#4365429) that this is expected behavior for 2.0 since "const" is not supported. I'm not sure I fully understand why they chose to handle it this way instead of to error or parse as a normal var. This behavior is prone to cause hard to detect bugs, especially since it only occurs…

Hi Erick, I have a test script running in our account with a deployment ID of 587. Using "const testvar ..." Example Suitelet /** * @NApiVersion 2.x * @NScriptType Suitelet */ define([], function() { return { onRequest: function (context) { var output = []; for(var x = 0; x < 3; x++) { const testvar = { val: 1 };…