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 2 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
So, we've hit some problems importing to a custom entity in Dynamics 365 Sales (online). The custom entity has a date field set to date / time with date only showing. The source data in Excel is in date only format set to UK (dd/mm/yy). The system is set to UK format and the logged in user is set to UK format.
When the data is imported the entries in the date field are being converted into US format (mm/dd/yy) - some get imported (incorrectly) and some don't as they don't match the format.
I've seen lots of blogs about this but most seem to point to the user / system settings which I am confident are set correctly.
Oh - if we do it via CSV using the same data - it works fine.
Does anyone know what's going on here?
Try setting Excel to ISO standard YYYY/MM/DD. That generally eliminates ambiguity, and then your CRM will still render UK standard dates since the CRM database is storing it all as ISO anyway.
Thanks for replying. I find it hard to believe that is the answer. Does this not suggest a problem with the import process from XL?
Excel and CRM's data types aren't 1:1. There's also limitations like Excel freaking out if you have two display names on attributes that are the same. It could be a bug, or it could be a design limitation. Either way, changing the date standard in Excel should be a valid workaround. But yes, you might also want to submit that as a bug, so MS can see it.
Business Applications communities