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
This week, on the Dynamics GP blog roundup:
Writing on his
AzureCurve blog, Ian Grieve stated that recently a client
reported that they could not post any journals and were receiving a
particular error message when they tried.
This error occurred for all users in only one of their more than
10 companies. There were no issues when the client posted a journal
in any of the other companies. The first thing Grieve wanted to
know was what had been changed or deployed in that database. The
After some investigation, Grieve happened upon a blog post that
offered information related to the exact error the client was
receiving. Grieve passed that information on to the client and told
them what to look for. This information was what the client needed
to straighten the issue out.
Business Applications communities