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 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 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
We have some transactions made on 02/29/20. Today (03/02/20), end user is getting below error when running February transactions.
"The value of DMY2Date parameter 1 is outside of the permitted range. The current value is 29. The permitted range is :from 1 to 28.
How or where can I chance the number of dates for February?
This is indeed strange. Just tested the example provided with
This is working like a charm.
I think that you should check with debugger the code where this is coming from and test out with the simple prototype
Day := 29; month := 2; year := 2020; outputdate := DMY2DATE(Day, month, year); MESSAGE(Text1000, Day, month, year, outputdate);
If this does not work either then the best bet are:
1. Outdated platform number for your NAV 2017 version. Test using the latest platform file.
2. Year that you pass by is not 2020 but something else
3. Worth checking if you pass 2020 or 1920 or whatever else. Debugger never lies.
Business Applications communities