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.
Expand your NetSuite knowledge by joining our Ask A Guru Live sessions. RSVP on this event now.
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!
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.
Nominate Your Peers for NetSuite Support Community's Choice of the Quarter! Submit your nomination today.
Intelligent Payment Automation version 1.0.3 is now available in the SuiteApp Marketplace. The SuiteApp, powered by BILL, lets you automate payments, manage vendor details, and bank account information within NetSuite. Learn more
Last Modified Date
We are processing sales orders in an onsite system, which queries NetSuite for new orders based on the "lastModifiedDate" field. The issue is we have had occurences where that date is recorded in NetSuite in the future. This causes our system to bring the order each time we query until that time passes. The description of this field in the documentation is:
Field Name: lastModifiedDate
Type / Length: dateTime
Req.: N
Mapping: None: hidden
Notes: This is a read only field. When updating a record, this field defaults to the current system date and time.
So it seems that the system generates this from the current time on the system. How could this be in the future? Has anyone dealt with this?
0