You create a Business Central report. You need to insert values on the Request page to be saved for the next time the report is run. What should you…

In Business Central AL development, the SaveValues property of a report object is specifically designed to control the persistence of user-entered data on the request page. When this property is set to true, any filters or parameter values entered by the user on the request page are saved. The next time the same user runs the report, these saved values are automatically loaded, streamlining the process for recurring report generation. This is the direct and intended method for meeting the requirement.

A. Set the TransactionType property to Update.

This property controls the database transaction behavior during report execution, such as data locking. It has no effect on saving user input from the request page.

B. Declare a SaveValues variable and assign it to true on the OnOpenPage() trigger.

This describes an incorrect implementation. SaveValues is a declarative property of the report object itself, not a variable to be assigned a value within a trigger.

C. Set the UseRequestPage property to true.

This property determines whether the request page is displayed to the user. While necessary to have a page to save values from, it does not enable the saving functionality itself.

1. Microsoft Learn. (2023). SaveValues Property. In Business Central development documentation. "Sets a value that indicates whether to save the values that the user enters on the request page... If you set this property to true, the values are saved."

2. Microsoft Learn. (2023). UseRequestPage Property. In Business Central development documentation. "Sets a value that indicates whether to show a request page for the report... The default value is true."

3. Microsoft Learn. (2023). TransactionType Property. In Business Central development documentation. "Sets the transaction type for the report. The following are the possible values: Browse, Snapshot, UpdateNoLocks, Update."