Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Whenever a record is created in AX, the createddatetime field in AX is showing 5 hours less than SQL createddatetime field for the same Table and both are in the same timezone.
Thanks in advance,
The actual value in the database is always stored in UTC time. But what you see in AX forms and table browser is adjusted to your user's time zone. Not the AOS server timezone. So the same database value is shown differently to users across different timezones.
Check "Preferred time zone" setting in user options -> General -> Miscellaneous. And also the time zone of the workstation of the user (where AX client is opened).
I checked it is in PST.
What is in PST? Do you still have some open questions or problems?
Yes, they can both be is PST but database doesn't store PST timezone. Database will store utc time, when you see that time in form, it adjust the time based on your timezone (PST) and that's what you see on screen.
Google what is utc time and difference between PST timezone and that will help.
Given AX works across the world, utc is the basis of storing date/times, you can even see different dates but all good when displayed in AX.
This is what I was looking for
Solution should be multiple AOS rather than customization in this area.
Business Applications communities