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.
Now is the time to ask your NetSuite-savvy friends and colleagues to join the NetSuite Support Community! Refer now! Click here to watch and learn more!
Stay in the Know
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Be sure you're subscribed to NetSuite communication to stay in the know about monthly happenings, updates and announcements. Subscribe
Please note that on Friday, March 20, 2026, at 8:00 PM Pacific time, our Case Management System will undergo a scheduled maintenance for approximately 4 hours. During this time, case creation via SuiteAnswers will be unavailable and inbound calls will be routed to Customer Service.
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