Skip to main content

Notifications

Dynamics 365 Community / Forums / Finance forum / Cannot create a record...
Finance forum
Suggested answer

Cannot create a record in Audit trail (TransactionLog). The record already exists

Posted on by 29
Hi all,
 
        After using data migration toolkit to move the data from D365FO On-Premises to D365FO cloud and starting UAT with a very good results for 2 days, we started to face the error Cannot create a record in Audit trail (TransactionLog). The record already exists
 
We searched for this error and found customization solution as in â€œCan not create a record in Audit trail (transactionLog). Dynamics Ax 2012 R3
 
Any idea for a reason and a solution without customization?
 
Thanks in advance
 
 
  • M.Hammam Profile Picture
    M.Hammam 29 on at
    Cannot create a record in Audit trail (TransactionLog). The record already exists
    Hi  Andre/Jody,
     
              Thanks a lot for your advise,
     
    I submitted a SR with Microsoft and their initial checking pointed to the limited performance of UAT environment and they promised to do a further investigation.

    By the way Jody, I did not follow the mentioned blog https://community.dynamics.com/blogs/post/?postid=113821c4-f8aa-4cf0-9692-429f6dea7997 as it involves customization and I look for a solution without customization.
     
    Best regards,
     
    M.Hammam
  • Suggested answer
    Judy Profile Picture
    Judy Microsoft Employee on at
    Cannot create a record in Audit trail (TransactionLog). The record already exists
    Hi, may I know if you have encountered any issues following the mentioned blog. It is recommended that you submit an SR to Microsoft for further solutions without customization.
  • Suggested answer
    André Arnaud de Calavon Profile Picture
    André Arnaud de Cal... 290,451 Super User 2024 Season 2 on at
    Cannot create a record in Audit trail (TransactionLog). The record already exists
    Hi M. Hammam,
     
    Thanks for your question. There are two system fields that are filled with internal kernel logic or SQL sequences. These fields are the RecId and createdTransactionID. In case you don't have customizations, I suspect that a wrong value for one of these fields is taken, causing a duplicate. Then the error can occur. I would suggest creating a support ticket for Microsoft Support to get some help where they can check the background if it was due to e.g. the data migration from on-premises to the cloud.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Dynamics 365 Community Update – Sep 16th

Welcome to the next edition of the Community Platform Update. This is a weekly…

Announcing Our 2024 Season 2 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Dynamics 365 Community Newsletter - September 2024

Check out the latest community news

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 290,451 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 228,353 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,148

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans