Microsoft MB-820 Exam With Confidence Using Practice Dumps

For the requirements provided, the appropriate page types should be selected as follows:

Display relevant insights in the Housekeeping Role Center: HeadlinePart

Display the additional information for the Room table: FactBox

Configure the first installation: StandardDialog

Comprehensive Detailed Explanation

In the context of Microsoft Dynamics 365 Business Central, page types are crucial for determining how information is presented to the user.

HeadlinePart: This page type is designed to display key data and insights in a concise and visually appealing manner, often used in Role Centers to highlight important information. It is suitable for the Housekeeping Role Center to display relevant insights.

FactBox: This page type is used to display supplementary information related to a selected record in the main part of the page. It's often used to show additional details about a record in a list, card, or document page. In this scenario, it is suitable for showing additional information about a specific Room when viewing the Room table.

StandardDialog: This is a page type that provides a modal dialog for user interaction, commonly used for setup wizards, confirmations, and input forms that require user action before proceeding. This is appropriate for configuring the first installation, where a step-by-step guided interaction is necessary.

API Publishing for Extensions:

In Business Central, when creating custom APIs like RoomsAPI, it is important to ensure that they are automatically published during the installation or upgrade of the extension.

To achieve this, you can include a codeunit of type Install in the extension that explicitly publishes the custom API (RoomsAPI) as a web service. This ensures that it is available for use immediately after the extension is deployed without requiring manual intervention.

Codeunit Type:

A codeunit of type Install runs when the extension is installed or upgraded. This type of codeunit can be used to perform setup tasks such as publishing web services or APIs like RoomsAPI.

Why Not Other Options?

Option A (default API configuration): This would not automatically publish the RoomsAPI. Default APIs do not cover custom APIs.

Option B (enable APIs for the environment): Enabling APIs in Business Central allows the standard APIs to be used, but custom APIs still need to be manually published.

Option C (publish via Web Services page): This would work but requires manual intervention to publish RoomsAPI, which does not fulfill the requirement of automatic publishing during installation.

Reference Documentation:

Publishing APIs in Extensions

Codeunit Types in Business Central

 Add Clear(PurchaseLine); as a line before line 01 of the code: No

 Add PurchaseLine.SetFilter("Line No."; '>0') as a line after line 06: Yes

 Change the filter on line 06 from a "No." field to a "Document No." field: No

 Remove "not" in line 07: No

 Add Clear(PurchaseLine); as a line before line 01 of the code.

No

You do not need to clear the PurchaseLine record before running the query, because the SetRange filters will take care of setting the correct context.

 Add PurchaseLine.SetFilter("Line No."; '>0') as a line after line 06.

Yes

Adding a SetFilter on the "Line No." field ensures that you're checking for actual purchase lines greater than 0, which are valid lines. This would fix the issue where the check might return false even when lines exist.

 Change the filter on line 06 from a "No." field to a "Document No." field.

No

The filter on the No. field is correct, as it's filtering based on the purchase order number. Changing this to Document No. is unnecessary.

 Remove "not" in line 07.

No

The not in line 07 is necessary because IsEmpty() returns true when no lines are found. To correctly return a boolean indicating whether the purchase order has lines, you need to negate the result of IsEmpty().