Check your knowledge

1.

What is the advantage of using collectible errors?

Normally, when an error occurs in a procedure, the procedure stops on the first error that it encounters. Using collectable errors will essentially postpone error handling to the end of the procedure call. AL code implementation won't stop on errors. Instead, it will continue until the end and will gather errors as they occur.

Normally, when an error occurs in a procedure, the procedure stops on the first error that it encounters. Using collectable errors will essentially postpone error handling to the beginning of the next procedure call. AL code implementation won't stop on errors. Instead, it will continue until the next procedure call and will gather errors as they occur.

Normally, when an error occurs in a procedure, the procedure stops on the first error that it encounters. Using collectable errors will essentially archive all errors. AL code implementation won't stop on errors. Instead, it will continue until the end and you can consult the error archive.

Normally, when an error occurs in a procedure, the procedure stops on the first error that it encounters. Using collectable errors will essentially cancel error handling. AL code implementation won't stop on errors. Instead, it will gather all errors and present them in one error message.

2.

Which method should you use to create pages that present options to the user?

Confirm

Message

StrMenu

Error

3.

What occurs if a try method contains a database write transaction?

The user needs to confirm a choice.

A runtime error occurs.

A warning message is generated.

The user needs to enter text to be written.

Answer the following questions to see what you've learned.

Feedback