web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

July 8, MS update issue: Write failed for table row of type 'VendInvoiceJournalLineEntity'.

(1) ShareShare
ReportReport
Posted on by 50
Hello, 
 
On July 8th, we MS pushed through some changes to D365FO which seemed to have caused an issue with our Power Automate solution.  Now we are receiving the following message: 
 
/An error has occurred.  Write failed for table row of type 'VendInvoiceJournalLineEntity'. Infolog: Info: Cannot edit a record in Ledger journal table (LedgerJournalTable)./An update conflict occurred due to another user process deleting the record or changing one or more fields in the record../
 
Some records are posted and the others error out.  My best guess is that it is timing related, i.e. we need to wait 5 seconds between transactions before posting the rest but am not sure.  
 
Any ideas on how we could resolve this?
I have the same question (0)
  • André Arnaud de Calavon Profile Picture
    300,911 Super User 2025 Season 2 on at
    Hi M Christopher,
     
    Are there some changes related to this entity or what changes were applied to your environment?  
  • Suggested answer
    Hana Xue Profile Picture
    Microsoft Employee on at
  • M Christopher Profile Picture
    50 on at
    @Hana Xue:
    I will take a look at the blogs to see if those solves the issues and get back to you.  
     
    @Andre Arnaud de Calavon
    I don't believe there is any relationship but could be wrong.  What I know is the Power Automate script worked perfectly up to July 7th and then on Monday (July 10th) it stopped working.  When I checked Feature Management, I saw that new features were introduced into the system:

     
    Every time the script break seems to coincide with when features are added.  I will review the blog that Hana suggested and provide an update.
  • Suggested answer
    M Christopher Profile Picture
    50 on at
    So we were able to solve the problem.  I had to delete the previous Fin & Ops connector and re-add it. 
     
    Someone mentioned it is likely that the connector has to be re-certified every time an update is pushed.  If this makes sense, is there a way to manage this?
  • André Arnaud de Calavon Profile Picture
    300,911 Super User 2025 Season 2 on at
    Hi M Christopher,
     
    Maybe Microsoft also changed the connector, but I haven't heard of continuously editing your flows after updates. However, it is a good learning that a kind of connector refresh can actually solve particular issues. Thanks for coming back with this information.

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

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
Martin Dráb Profile Picture

Martin Dráb 664 Most Valuable Professional

#2
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 522 Super User 2025 Season 2

#3
Sohaib Cheema Profile Picture

Sohaib Cheema 303 User Group Leader

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans