This site was built to compliment the existing NetSuite Professionals Slack Community by adding a means for members to easily find answers to common questions and to create a searchable database of those questions and answers.

NetSuite Professionals

Seeing date objects not being able to be set in Leading accounts (2025.2.0.30061)

Aka: new Date() always returns invalid value now

hmm i wonder if that's why StrongPoint is producing so many date errors

I’m always the old guy who always say use the native NetSuite API methods, but people never listen and I’m always crazy…
If all your date operations are always handled by the ‘N/format’ module, you will never have this problem…

I think you may be on to something haha, just hoping it’s not an undocumented change - we have some cases where we’re utilizing format but unfortunately most of our code bases are all JavaScript dates in some manner.



The fact is new Date() is simply a native JavaScript function that could be handled differently depending on the Transcompiler used by NetSuite at any given time (Rhino, etc)... That can change but they will update their documented API methods...

I use this a ton and haven't run into it (yet)

for those with Strongpoint issues (failing workflow) you can actually tweak the script to fix it, this is what I did.

the offending script is `SP_WFA_CLSystemNoteUpdate.js`

```for (var j in resultobj) {
                //++ 382132 convert dates properly before setting
                if ((j == 'custrecord_flo_actual_change' || j == 'custrecord_flo_system_note_date' || j == 'custrecord_flo_temp_changedate') &amp;&amp; resultobj[j]) {
                    thisRecord.setValue({ fieldId: j, value: format.parse({value: dateUtil.toSaveFriendlyDateTime(resultobj[j]), type: format.Type.DATE}) });
                } else if ((j == 'custrecord_flo_system_note_available') &amp;&amp; resultobj[j]) {
                    thisRecord.setValue({ fieldId: j, value: resultobj[j] == 'T'});
                } else {
                    thisRecord.setValue({ fieldId: j, value: resultobj[j]});
                }
            }```

they tried to setValue on a date field to a string, and on a checkbox field to ‘T’

apparently it “works in their account”

surprised their bundle scripts were not locked

Recent changes are making it quite hard to have anything locked anymore.

Luckily this isn’t strongpoint any plain new Date Object not working in leading accounts.  

Waiting for a defect to be issued 