Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
I am getting the issue in D365 8.1 Version (PU 20).
While posting the General Journal we are getting the error "Operation canceled: Validating and posting journal". Journal Validation is OK. But, while posting the journal getting an error.
In Journal header, "Locked by System" field is automatically updated as Yes while posting journal.
Looks its MS bug. Is there any solution will be there or we need to raise a MS ticket for this?
please help me to resolve this issue.
Can you share the exact error? What type of journal lines are entered in this journal? Initially, I do think it is related to some setup or user input.
You used the tag 'development'. Do you have customizations in this area?
Its a daily journal (General Journal from GL module).
Errors: Operation Canceled: Validating and Posting Journal, Journal ##### is locked by system, Validation errors occured with journal batch number #####, see the message center for error details.
Yes, we have done some customizations in the tables (LedgerJournalTable & LedgerJOurnalTrans) and form(LedgerJournalTransDaily).
Its not a minor extension based development.
Is customization around locked field on the journal ? Did you try to uncheck lock field and try to post ? if its happening in all environments , you might want to remove ur customization and try to post.
If the journal is locked by the system, you have to change the value of the system blocked field on the LedgerJournalTable. There is no functional support for it. You can use a runnable class or direct SQL. As I do see the company USMF, I assume it is not a production environment. So, you do have access to change it yourself. It can be caused by a customization or system crash.
There is no customization on the System Locked field. Yes, I have tried to unlock the journal manually and tried to post again. But, still coming and System Locked field is updated automatically as "yes".
Yeah, I have tried to change the value of System locked field and its again automatically updated when clicking post button. Yes, this is not the production environment. Looks, something happening because of customization. Because, I have another environment with the same version, it's working fine(No Customizations).
During posting, the journal is indeed system blocked until the posting has ended or failed. You could have additional logic which breaks the current mechanism. So, review the customization.
We have added few fields in LedgerJournalTable and LedgerJournalTrans table to suite for business process.
Those fields are added as per extension concepts. After that, we have resolved by removing those fields and done the full build with dependency packages and have done the synchronization.
Then we tried to validate and post the journal.. It's working fine. Then we have added the required fields again to meet business process.
Thanks for all of your suggestions.
Business Applications communities