Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2022 Release Wave 1 PlanDynamics 365 release plan for the 2022 release wave 1 describes all new features releasing from April 2022 through September 2022.
2022 release wave 1 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
In Ax 2009, If transaction lines are exist in the journal lines, we cannot delete the Journal header. While trying to delete, System throws an error as"The record may not be deleted. Transactions exist in table 'Journal lines'.
But In AX 2012, System allows to delete the Journal header without any restrictions.
Can you please let us know, Is there any parameters or settings to restrict the Journal header deletion in Ax 2012.
Thanks and Regards,
The functionality has been changed in AX 2012. But it is not without any precautions. Now you will first get a question if you want to delete the journal completely; so with all lines.
If you confirm this question, then the journal and the lines are deleted.
It is possible to restrict deleting the journal table itself by use of security roles.
If you really want to restrict deleting when lines do exist, you can customize it or create an eXtensional Data Security (XDS) policy to restrict deleting records based on conditions.
More information about XDS can be found here: technet.microsoft.com/.../hh272862.aspx.
Hii Andre How we can do this with XDS policy.
You mean to say that we can shop open Journals only on that form by applying XDS policy or any other way.
I have checked this the other day, and Microsoft has changed it between R1 and one of the CUs in R2 and above.
If you want the old behavior, change the LedgerJournalTable form, and edit the validateDelete() method on the form datasource to call super() instead of returning true. This way the old delete action on LedgerJournalTrans will prevent removing the journal by blindly clicking YES on the popup dialog (I would consider this to be user error).
This was for the General Journal, you might need to check the other journal posting forms if they did the same yourself.
Business Applications communities