Quantcast
Channel: Dynamics 365 Business Central/NAV User Group
Viewing all articles
Browse latest Browse all 11285

Forum Post: RE: Save changes even if error is raised.

$
0
0
Happy that it worked for you. The reason why COMMIT is dangerous is if you put it into the "wrong" place, then you get transactions committed, which should have "rolled back" on failure. In your case you do the COMMIT after you "transaction" (printing the report), so you're pretty safe. PS: Also notice another difference: FINDSET(TRUE,FALSE) as supposed to just FINDSET. Since you are modifying the customer, then you should say that in the command.

Viewing all articles
Browse latest Browse all 11285

Trending Articles