When an ERROR procedure is invoked, the execution of the current process terminates, the message is immediately displayed, and the database returns to the status it had following the last (implicit or explicit) COMMIT procedure as though the process that was calling the ERROR procedure had not run at all.
We can use the ERROR procedure in combination with the MESSAGE procedure to assist in repetitive testing. MESSAGE procedures can be placed in code to show what is happening with an ERROR procedure that's been placed just prior to where the process would normally complete. Because the ERROR procedure rolls back all database changes, this technique allows us to run through multiple tests against the same data without any time-consuming backup and restoration of our test data. The enhanced testing procedurality that's built into Business Central can accomplish the same things in a much more sophisticated fashion, but sometimes there's room for a temporary...
