The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
Now Available in Community - New TechTalk Videos for 2020
Read More about New TechTalks for 2020
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 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
Dear Dynamics 365 Lovers,
If we are supporting / implementing in Polish localization, we need to be aware of some recent issues in fixed asset module while creating depreciation proposal.
Lets explore together.
It can have two business scenarios~
1: In Polish Localization, business can use standard depreciation method, such as Straight line method- and for this, there will be no issue.
2: However, In Polish Localization, business can use Polish Localization depreciation method, such as ReducingBalance_PL & StraightLinePercentage_PL, on this scenario, there is an issue and an error is experienced.
Affected Depreciation methods are as follows, also I have added the exact error text below.
Even though the error seems a show stopper, luckily its not, which means, you/business user can continue and post the journal, THATS A GOOD NEWS!!
Microsoft already fixed this BUG in 10.0.14 and can be avoided this error from there.
And this is happening because of the below remarks by PG team.
Validates while calculating depreciation proposal if depreciation date is null then need not find previous month of this day.
I hope this will be useful for you.
Microsoft Dynamics 365 Consultant | Educator | Blogger
Business Applications communities