BC Friday Tips #13 Be careful with the hidden 𝗖𝗼𝗺𝗺𝗶𝘁!

Time for BCFridayTips for the BC consultants.

Be careful with the hidden 𝗖𝗼𝗺𝗺𝗶𝘁!

When a 𝗖𝗼𝗺𝗺𝗶𝘁 statement is executed, it ends the current write transaction and registers the changes in the database. If an error occurs after the Commit, those changes won’t be rolled back, potentially leading to a partial commit issue.

Here’s an example:

Consider the table 99000786 “𝗥𝗼𝘂𝘁𝗶𝗻𝗴 𝗩𝗲𝗿𝘀𝗶𝗼𝗻” and its “𝗦𝘁𝗮𝘁𝘂𝘀” field validation.

In this code, a 𝗖𝗼𝗺𝗺𝗶𝘁 is triggered when the 𝗦𝘁𝗮𝘁𝘂𝘀 field is validated.

We need to be aware of this.

Why?

✅ 𝗔𝘃𝗼𝗶𝗱 𝗽𝗮𝗿𝘁𝗶𝗮𝗹 𝗰𝗼𝗺𝗺𝗶𝘁. If an error occurs after a Commit, it is impossible to roll back everything completely.

Even though the commit statement isn’t used frequently, it’s important to check for it when working with any objects in BC so you can handle it accordingly.