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!
Update your Profile with your Support type to get your Support Type badge.
Uncover the power of data with the Analytics Hub —your ultimate guide to mastering NetSuite Saved Searches and Reports. Simplify the complex and unlock your organization's true potential. Dive into the Analytics Hub now and soar to new heights!
NetSuite 2025.2 Release Notes - This document summarizes the changes to NetSuite between 2025.2 and the previous release.
To help you get the most out of your 2025.2 Release Preview account, review the topics outlined in the 2025.2 Release Preview Guide.
SuiteWorld October 6 - 9, 2025: Agenda Builder is live!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
Read on for the latest updates including:
• Agenda Builder launch
• SuiteWorld On Air registration
• New NetSuite Prompt Studio Contest
• And more!
Check out this thread to learn more!
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