Microsoft Updated MB-820 Exam Questions and Answers by pia

A: In Business Central, wizard pages are created using the NavigatePage type because it allows step-by-step navigation, which is perfect for wizard-like user experiences.

B: The group control organizes the content for each step in the guide, and it’s essential to add these controls to the layout's Content area for each step of the wizard.

C: Worksheet is used for pages designed to handle larger datasets, not for wizard or step-by-step flows.

D: Repeater controls are used for displaying multiple records, not for guiding users through steps, so it’s incorrect for this scenario.

For more information, you can refer to Assisted Setup in Business Central.

When updating the base application table using a table extension in Microsoft Dynamics 365 Business Central, certain properties of table fields can be modified to meet new requirements, such as regulatory changes. The DecimalPlaces property (B) is one such property that can be adjusted in a table extension. This property determines the number of decimal places that are displayed and stored for decimal fields in the table. Adjusting the DecimalPlaces property can be particularly useful when dealing with financial data and tax calculations that require precision to meet new tax tiers set by a regulator. It's important to note that not all properties can be modified in a table extension; for example, the CalcFormula property (A) cannot be changed as it affects how the field's value is calculated, which could have significant implications on the base application's logic.

To hide the field "Unit Price" from the Resource Card page in Microsoft Dynamics 365 Business Central, you need to modify the visibility property of the field using the modify keyword, which allows you to change the properties of an existing field on a page.

modify("Unit Price") is the correct way to target an existing field on a page (like the Resource Card page).

The line Visible = false; makes the field invisible on the page.

Here's a breakdown of why each option is right or wrong:

Option A:

Uses addlast("Unit Price"), which is incorrect because you are not adding a new field; you're modifying an existing one. Also, Visible = false is correct for hiding a field, but the wrong method (addlast) is used.

Option B:

Uses modify("Unit Price") with Enabled = false;. This would disable the field (make it non-editable), not hide it. The field would still be visible, so this does not meet the requirement.

Option C:

Uses addlast("Unit Price"), which is incorrect, and Enabled = false;, which would disable the field, not hide it.

Option D:

modify("Unit Price") { Visible = false; } is the correct syntax for hiding the field on the page.

Correct Code Snippet:

modify("Unit Price")

{

Visible = false;

}

This hides the "Unit Price" field from the Resource Card page.

 Subtype: Install

 Trigger: OnInstallAppPerCompany

You are developing a codeunit that should only run during the installation of an extension package.

Options:

Subtype: The correct subtype is Install, as it indicates that the codeunit runs only when the extension is being installed.

Trigger: The correct trigger for running during installation is OnInstallAppPerCompany, which handles code execution when the app is installed for a specific company.