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

Announcements

News and Announcements icon
Community site session details

Community site session details

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

Auto-remove OData entity if error encountered

(0) ShareShare
ReportReport
Posted on by 103

Hello, I have noticed that when I run into any errors when I POST OData entities (e.g. VendInvoiceJournalHeaders) they still remain in the system, and I have to either remove them manually or have a routine in my code to remove them.

Is it possible to have them be auto-removed if an error was encountered so I don't have to handle it myself?  

I have the same question (0)
  • huijij Profile Picture
    19,813 on at

    Hi sir,

    Are you trying to delete the wrong OData record? You can use the data entity to delete the record.  OData enabled data entities can be used to delete records as well. What is your real bussiness requirement?

  • André Arnaud de Calavon Profile Picture
    306,725 Super User 2026 Season 2 on at

    Hi tl2022,

    Can you elaborate on the exact error(s) and what records are then in the application for this entity?

  • tl2022 Profile Picture
    103 on at

    Hello, so here is an example of what we are very likely to run into. We post to VendInvoiceJournalLines entity with the invoice information, but the user has mistakenly entered an offset account that does not exist in the system. The POST request comes back with an expected error (e.g. "message":"Write failed for table row of type 'VendInvoiceJournalLineEntity'. Infolog: Error: The MainAccount 12345 for LedgerChartOfAccounts STORE does not exist.; Error: Error found when validating record..",...), but if I go to the vendor invoice journal in the UI, I see the line was still submitted, albeit with alot of missing information. I don't know why this happens instead of the system just not writing a line.

  • Suggested answer
    Anton Venter Profile Picture
    21,091 Super User 2026 Season 2 on at

    When data is entered into the system via a data entity, not all data fields are validated and checked in the same way as manually entering the same data in the user interface. The user interface will not allow an invalid field to be selected, or entered, where as a data entity in theory might allow this, depending on the specific data entity of course.

    When manually entering data in the system, the user interface makes many calls to all the validation methods on the tables and in code, depending of the form of course.

    In your invoice scenario, the data is entered via a data entity and not fully validated, but the system is however going to validate the data when posting the invoice.

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

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders

These are the community rock stars!

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

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 288 Super User 2026 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 276 Most Valuable Professional

#3
Anton Venter Profile Picture

Anton Venter 225 Super User 2026 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans