Notifications
Announcements
No record found.
Hello,
Are there any triggers or cause where modified date is earlier than the created date time?
I don't think there is any control, but due to the nature of ax, considering the places where the values are set, it didn't seem possible to me
thank you for this. are you aware of any cause when fetching in sql, there are missing rec ids. query used is just order by created date time and rec id (for any table)
If you have a date-time range did you consider timezone
Hi,
Perhaps you set "modifiedDateTime" as yes firstly and then you set "created DateTime" as yes.
Please set both of them as yes and sync table then check Does it correct in new transaction or not
i'll check on this. does the timezone refer to the aos where the transaction was made?
TimeZone is defined on the user.
"Ax utilizes the utcDateTime data type to store date time information in the database using the Greenwich Mean Time definition of time"*
However, while displaying it to the user, it takes into account the user's timezone. In some cases (especially at midnight), the day the user sees and the day kept in sql may be different. Depending on the codes, a situation such as "why it did not come(to report etc.)" may arise.
However, as far as I saw from the other post you opened, your situation is different. Don't rely too much on recIds, the correct field for filters like this is createdDateTime
* stoneridgesoftware.com/.../
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 565 Most Valuable Professional
André Arnaud de Cal... 450 Super User 2025 Season 2
Sohaib Cheema 250 User Group Leader
