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
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
"Cannot create a record in Ledger journal table (LedgerJournalTable). Name: Vend_p, Vendor Payments. The record already exists"Getting above error when create payments.
This look like the issue is with the duplicate journal num.
Can you please give any solution to set the journal num?
Check the number sequence for this journal. Is it marked as continuous? It should usually not be necessary to have it continuous, so just remove the Continuous checkbox from the number sequence settings.
If you need to have it continuous (basically if you have requirement that this internal "technical" id sequence has no gaps) you can remove the problematic number from the Status list of the number sequence.
We cannot make it non continuous as it was maintain continuous from very beginning and here, journal number generated was duplicate so we have to change the journal number that is generated at the time of create payment.
Can you please give a way to set the next journal number ? or from where the journal number sequence maintain?
Number sequences are maintained in Organization Administration - Number sequences - Number sequences.
First check if the Next value of the number sequence is ok. If not, change it to some value that is really free (not yet used).
If the Next value is ok, then the problem is that some already used value exists in the Status list of the number sequence. In that case just delete that value from the Status list.
Also please note that continuous number sequences should be used only when it's really required (for example because of legislation) that there are no gaps in the sequence. Journal numbers are just technical sequences inside AX so there should not be any legal requirement for those to be continuous. Continuous number sequences are slower to initialize, and can sometimes have issues like the one you have. So you need to pay some price (slower performance, using time to investigate issues) for the continuous number sequences.
We got the solution for this.
The number sequence having the list generated for specific number sequence and that number sequence is used at the time of create payments.
We have delete the entry from list form
List button open the status of the number sequences and we have cleared that entries.
Now, It works for us.
Thank you for all your replies.
Great to hear that!
Please mark the helpful answer(s) as verified so that others can benefit from them. Thanks!
I am not able to mark answer as verified. Can you help me?
Next to the suggested answers you see text "Was this answer helpful?" or something like that. And you can click Yes.
It is showing only in your responses. There is no link shown in my own response. :)
Yes, that's right. Since I provided the suggested answer. If it was helpful, please mark it as verified.
You're supposed to mark the answer(s) as verified, not your own question. The idea is that others can see which answers / suggestions were helpful.
Also, you are not supposed to mark your own questions / messages as "Make post a suggested answer" when you post them. Since they are not suggested answers to the problem.
Business Applications communities