Notifications
Announcements
No record found.
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?
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?
Hi tl2022,
Can you elaborate on the exact error(s) and what records are then in the application for this entity?
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.
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Martin Dráb 559 Most Valuable Professional
André Arnaud de Cal... 464 Super User 2025 Season 2
Sohaib Cheema 250 User Group Leader
