Rolled back inserted record from table1 if record insertion fail in table2 in D365FO or AX2012

(0) Share

Report

Posted on by Shakoor Taj

Hello Experts,
I am trying to implement a transactional logic in D365FO. I have two tables, table1 and table2, and I want to insert a record in both of them. However, I want to make sure that if the insertion in table2 fails, the insertion in table1 is also rolled back. How can I achieve this using X++ code?

I have the same question (0)

All responses (3)

Answers (2)

Verified answer

Martin Dráb 237,878 Most Valuable Professional on at

Like (0)

Report
You need to use a concept called database transactions.

If you run several database operations (e.g. inserts or updates) in a single transaction, they're considered a single operation that must either succeed or, in case of a failure, all changes must be rolled back.

In your case, you can do something like this:

Table1 t1; Table2 t2; ttsbegin; ... populate fields... t1.insert(); t2.insert(); ttscommit;

The statements between ttsbegin and ttscommit form a single transaction. If an exception is thrown anywhere in the block, all database changes are automatically rolled back.

This is a super-important topic, because if you don't use transactions correctly, you may cause data inconsistencies in your (your client's) production database, potentially with serious consequences.

Was this reply helpful? Yes No
Shakoor Taj 32 on at

Like (0)

Report
Hi Martin,

Thank you for your quick reply as usual.

I have implemented the code as you suggested, below is my sample code.

InventTable inventTable; CustTable custTable; ttsBegin; inventTable.initValue(); inventTable.ItemId = 'Item1'; custTable.initValue(); custTable.AccountNum = 'Customer1'; inventTable.insert(); if(custTable.validateWrite()) custTable.insert(); ttsCommit;

This code run for InventTable and insert the new item "Item1" in the InventTable, but for CustTable insertion it check the validateWrite() and show me the error for Customer Group and not insert the record in the CustTable but it does not rollback the database change (InventTable).

Any suggestion.

Was this reply helpful? Yes No
Verified answer

Martin Dráb 237,878 Most Valuable Professional on at

Like (1)

Report
Yes, that's how you've implemented your code. You can't see it by walking through execution of your code in debugger, if the behaviour isn't obvious to you just by reading your code.

You don't throw any exception if validateWrite() returns false. You just skip the call of custTable.insert() and then you successfully commits the transaction.

If you want to throw an error and get the transaction aborted, use the throw statement. For example:

ttsBegin; ... inventTable.insert(); if (!custTable.validateWrite()) { throw error("Operation aborted"); } custTable.insert(); ttsCommit;

Was this reply helpful? Yes No

Join the conversation

Community site session details

Rolled back inserted record from table1 if record insertion fail in table2 in D365FO or AX2012

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

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

Featured topics

Product updates

Community site session details

Rolled back inserted record from table1 if record insertion fail in table2 in D365FO or AX2012

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

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

Featured topics

Product updates