web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Check out the Community Spotlight Video Series
News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / Problems with date typ...
Customer experience | Sales, Customer Insights,...
Suggested Answer

Problems with date type fields with January 1900 dates

(1) ShareShare
ReportReport
Posted on by DS-29040812-0 3
Entering dates to January 1900 reduces one or two days to the date entered. 

Passes with date type fields (Date only). I've tried all types of time zone settings because that would be the problem, but it doesn't seem to be the case. 

For example, in the CRM I put a date of January 1, 1900 and it changes it to December 31, 1899. But, if I put a date after January 1900 the date doesn't change.

 
 
 
I have the same question (0)
  • Dengliang Li Profile Picture
    Dengliang Li Microsoft Employee on at
    Hi,
     
    In my testing I found that this is related to the time zone the user is in.
    I have created the following three date fields in the contact entity with the following behavior: Date Only,User Local and Time zone independent.
     
    The current time zone is GMT+12.
     
    In Dataverse you can see that the time zone adjustment is set to the User Local field is affected by the time zone and the date is reduced one day.
    And the other two fields are unchanged.
     
    The same results are fetched through the WebAPI.
     
    If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more.
    If you have further questions, please feel free to contact me .
     
    Best Regards,
    Dengliang Li
     
  • Suggested answer
    DS-29040812-0 Profile Picture
    DS-29040812-0 3 on at
    I have conducted tests after your response, but the dates in the Dataverse table still appear incorrect to me.
    The View
    WebAPI
    Time zone


    What I don't understand is why they appear incorrect in the view and table, but in the form and in the webAPI it shows what it should show.
     
    Could it be because of the time zone? And why only with dates prior to January 1900? Why don't you change the other dates?
     
    Thanks
     

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.

Helpful resources

News and Announcements

Check out the Community Spotlight Video Series

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the June Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Manoj - ManoVerse Profile Picture

Manoj - ManoVerse 77 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 41

#3
Chris1968 Profile Picture

Chris1968 20

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans