MB-820 Exam Dumps - Microsoft Dynamics 365 Business Central Developer

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

In Business Central, fields in tables are assigned specific data types that determine the kind of data they can store. For the Non-conformity table mentioned in the case study, the following data types should be used:

Date for the Non-Conformity Date field: This is because the Non-conformity Date field is required to store only the date when the non-conformity was recorded. The Date data type is appropriate for storing dates without times.

Code for the Non-Conformity Number field: The Non-conformity Number field is described to use alphanumeric values with a format that includes "NC" and the year, like "NC24-001". In Business Central, the Code data type is used for fields that store alphanumeric keys. It is a text field with a limited length, which makes it suitable for number series that contain letters and numbers.

Other options are not suitable:

A. Integer for the Non-conformity Number field: This would not be appropriate because the Non-conformity Number includes alphanumeric characters and not just integers.

B. DateTime for the Non-Conformity Date field: This is not correct because there is no requirement to store the time alongside the date.

C. Char for the Non-Conformity Number field: Char data type is not typically used in Business Central for number series or identifiers. The Code data type is preferred for this purpose.

ï‚· The Part Time Shop Supervisor profile will be applied only to users with "Register Time" = true on User Setup: No

ï‚· Variables, procedures, and triggers cannot be added on page customization objects: Yes

ï‚· Line 10 should use extends instead of customizes: No

ï‚· In line 18, "Unit Cost" will be moved after "Costing Method": Yes

ï‚· The Part Time Shop Supervisor profile will be applied only to users with "Register Time" = true on User Setup.

No

The code doesn't contain any reference to the User Setup table or the Register Time field, so this is not correct. Profiles are not applied conditionally based on fields like this.

ï‚· Variables, procedures, and triggers cannot be added on page customization objects.

Yes

Page customization objects are meant for UI modifications, such as moving or hiding fields. You cannot add variables, procedures, or triggers in a page customization object.

ï‚· Line 10 should use extends instead of customizes.

No

In AL, when customizing a page within a profile, you use customizes rather than extends. Extends is used when modifying base application objects, but customizes is used to customize pages within a profile.

ï‚· In line 18, "Unit Cost" will be moved after "Costing Method".

Yes

The code in line 18 is correct. The moveafter directive will move the "Unit Cost" field after the "Costing Method" field on the page layout.

Read Scale-Out:

Read scale-out is a feature in Business Central that allows you to improve performance by distributing read-only queries (such as the ones from the ticketAPI) across multiple read replicas in the cloud database. This reduces the load on the primary database and helps improve the response time for read-intensive operations, like analyzing POS data through the ticketAPI.

Data Access Intent - ReadOnly:

When enabling read scale-out, you can configure the DataAccessIntent property of APIs to be ReadOnly. This directs the system to use read replicas to handle read-only queries, which enhances performance by offloading such queries from the primary database.

Why Not Other Options?

Option A (ODataReadonlyGetEnabled): This parameter is unrelated to read scale-out and primarily affects OData services behavior, not API performance tuning.

Option B (AccessByPermission): Setting the permission to Read does not directly affect the performance. It only controls access based on user permissions.

Option D (DataAccessIntent ReadOnly): While setting this property to ReadOnly helps in read-only operations, enabling read scale-out (option C) ensures the underlying infrastructure is optimized to handle such read operations, which is the fundamental action required.

Reference Documentation:

Read Scale-Out in Business Central

Data Access Intent in AL

codeunit 52102 "POS API Management"

{

Access = Public;

Permissions = TableData "POS Information" = rwdx;

trigger OnRun()

begin

readAPI();

end;

procedure readAPI()

begin

// Your code here to read from the POS API

end;

}

Load the report for users in a specific location: OnInitReport

Validate data before processing: OnPreReport

Define filter based on Department field: OnPreDataItem

The requirements for the report are:

The report must be loaded for users in a specific location only.

Data entered in the request page must be validated before any further processing.

A filter must be defined for users based on the Department field defined in user setup.

Trigger Matching:

The report must be loaded for users in a specific location only.The correct trigger for loading the report is OnInitReport.

This trigger runs when the report is initialized, and you can use it to define user-specific loading conditions, like location-based filtering.

Data entered in the request page must be validated before any further processing.The correct trigger for validation before processing is OnPreReport.

This trigger occurs before the report is run and can be used for data validation before further processing begins.

A filter must be defined for users based on the Department field defined in user setup.The correct trigger to define filters is OnPreDataItem.

This trigger occurs before data item processing begins and is used to apply filters such as those based on the Department field in the user setup.

ï‚· Direction: Both

ï‚· Format: VariableText

You are configuring an XMLport for Business Central with the following requirements:

Specifies import or export on the Request page at runtime.

Formats the data in a non-fixed length CSV format.

XMLport Configuration:

Specifies import or export on the Request page at runtime.The Direction property must be set to Both.

This allows the XMLport to both import and export data depending on user selection during runtime.

Formats the data in a non-fixed length CSV format.The Format property must be set to VariableText.

VariableText is used for delimited text formats like CSV, which do not have a fixed length for fields.

You are retrieving data using a query data type. The following code snippet needs to be completed:

If QueryA...: The correct option here is Open. This opens the query and prepares it for data retrieval.

While QueryA...: The correct option here is Read. This reads through the query results one row at a time.

If QueryA...: Open

While QueryA...: Read