Dates are getting written to CDS differently but they are entered on the same Contact form with the same format applied.
The bad dates get rejected on import. The attached shows an example in entry sequence, as show in Excel date formatted column.
10/25/2020 12:00:00 AM - Rejected
05/08/1985 00:00 - Accepted
8/27/1979 12:00:00AM - Rejected
I have another issue with UK dd/mm/yyyy versus US mm/dd/yyyy formatting as the Environment is configured UK but I can look into that next!.
Also. If a date is keyed in without using the dropdown then everything resolves to 12/31/2019 e.g 2/3/2020, 15/12/2020.
Any hints on where to start to look please? Cheers Richard
Solved! Go to Solution.
There are three issues here.
Issues 1 & 2 relate to the overall environment setting and the user personalization setting which can override.
The 3rd issue is how the problem initially revealed itself. Dataflows from one environment to another failed on valid dd/mm/yyyy formatted dates.
The reason is that DataFlows will only recognise US mm/dd/yyyy formatted dates by design.
Microsoft have put it on their road map to fix but no ETA yet!
HI @Gatwick ,
Could you please share a bit more about your issue?
Do you mean that the date value stored as different format in your Contacts Entity?
Further, do you create a Date time type field or Date only field in your Contact Entity?
Regarding the issue that you mentioned, I think this issue may be related to time zone. I have made a test on my side, and don't have the issue that you mentioned.
Actually, all date/time data is stored in the Common Data Service as a UTC value. The way the data is displayed determines if just the UTC value is used or if the value gets translated to the user’s local time.
If you created a Date only field in your Contacts Entity, but you set it to ‘Time Zone Independent’ or ‘User local’ rather than "Date Only" in your Entity, when storing date value into this Date only field, it would include timestamp will cause the date to appear differently for different users.
Please check and see if the following blog would help in your scenario:
So if you created a Date Only field for your Contacts Entity, please make sure you changed the "Behavior" option to "Date only" for the Date only field in your Contacts Entity:
Thanks for the suggestions.
The 'date only' Contact Birthdate is standard default. Looking again at the Excel export it reveals the field is populated in both date and text format. There is only one form revealed to users for input so I'm puzzled as to how this has happened.
Can you shed some light as to how I could check further please? (Next post has Excel picture)
Correction. The Birthdate is set as date and time, not just date, and the picker does not reveal the time.
Looking at the contents in both the Date and Text formatted field the time is shown as either 12:00:00 AM or 00:00. No problem.
From the documentation I'd checked the individual contacts, both are blank for personal Time Zone settings.
Still puzzled why text and date contents?
It seems that text dates in the field are acceptable on import.
The problem is the DD/MM/YYYY - MM/DD/YYYY formatting.
I missed this originally as all No.119 contact records with text dates were rejected.
They couldn't be converted as all No.119 user entered birthdates were greater than 12 for the DD, when seen as MM = invalid!
So I need to get to the bottom of US UK dates.
Hi @Gatwick ,
Based on the Date time format site setting you set in your Portal, I think there is something wrong with it. On your side, you should configure a "DateTime/DateTimeFormat" Site Setting in your Portal as below:
The Value field set to following formula:
More details about accepted date/time format in your PowerApps Portal, please check the following article:
Date time Site Settings in PowerApps Portal as below:
The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.
The Super User program for 2022 - Season 2 has kicked off!