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 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
Can you please confirm if there are changes in standard behaviour for depreciation?
Before CU13, even if the offset account's "do not allow manual entry" is marked we can proceed with the posting, but after update the still can be posted but it goes through another account which is suspense account 99999.
I have not heard that the activation / de-activation of this parameter causes a problem that you describe.
Can you have a developer looking at that?
Also, can you replicate the problem for other assets in a demo/test environment?
Thank you for your response. Actually I have tried in two test demo environments, they have different behaviour.
test environment 1 - AX will not allow posting.
test environment 2 - AX will show warning message but will still able to post to another account 99999.
that is why i'm a little bit confused on what is the real or should be behaviour of AX once the depreciation main account is set to do not allow manual entry when it comes to depreciation.
hope you can help me on this.
Good morning ace,
Many thanks for the update.
Interesting that your two test environments behave differently.
This indicates that they have a different setup.
One thing that I suspect that might be responsible for this is the GL parameter 'interrupt in case of error account'.
Can you check that this parameter is set identical in both of your systems?
Interrupt in case of error account' - are both unmarked in test environments.
It was confirmed just now by Microsoft that the change in behaviour was due to the CU13 update.
Business Applications communities