Discussions
Stay up-to-date with the latest news from NetSuite. You’ll be in the know about how to connect with peers and take your business to new heights at our virtual, in-person, on demand events, and much more.
New AI Community Guidelines. Please review and follow them to ensure AI use stays safe, accurate, and compliant.
Date format conflicts in scripted searches: mmddyyyy vs yyyymmdd
How do you guys work around this? I set one of my criteria like the following to exclude empty or otherwise bad dates:
filters[2] = new nlobjSearchFilter('custrecord_current_end_date', null, 'after','1/1/1990',null);
It works great except for users whose Date format preference doesn't have YYYY at the end. Seems to work with MMDDYYYY and DDMMYYYY equally well. If YYYYMMDD is used, an expected error is thrown.
Netsuite suggested using something like the following, but it throws an unexpected error no matter what format is used:
var myDate = nlapiStringToDate('1/1/1990');
filters[2] = new nlobjSearchFilter('custrecord_current_end_date', null, 'after', myDate, null);
0