MB-820 Online Practice Questions and Answers

Correct Answer:

Codeunit "Discount Mgmt." compiles successfully. = NO VariantLine in line 17 must be changed to Line and the DiscountAmount removed for the codeunit to compile. = NO

The DiscountIsValid method must be defined in the interface for the code to compile. = YES

The codeunit "Discount Mgmt." will not compile successfully as is because the DiscountIsValid method is not defined in the "IDiscount Calculation" interface, yet it is being declared in the codeunit which implements this interface. AL requires

that all procedures in the codeunit that implements an interface must be defined in the interface itself.

The VariantLine in line 17 does not need to be changed to Line, nor does the DiscountAmount need to be removed for the codeunit to compile. These are valid declarations in AL and they are correctly implemented in the codeunit. The Variant

data type in AL is used to handle various data types and DiscountAmount is a valid return type for a procedure.

For the code to compile successfully, the DiscountIsValid method must be included in the interface because AL enforces that any codeunit implementing an interface must implement all the methods defined in that interface.

Correct Answer:

Based on the PowerShell script snippet you've provided and the scenario described, you need to configure Docker sandbox environments for a company with specific requirements for Test Toolkit installations.

For SandboxA, since it is configured without the Test Toolkit installed, you would typically use the PowerShell cmdlet Install-TestToolkitToBcContainer to install the Test Toolkit into the Business Central Docker container.

For SandboxB, which must be configured from scratch with the Test Toolkit installed during configuration, you would include the Test Toolkit as part of the New-BcContainer script block that creates the container.

The relevant cmdlets and parameters for SandboxB would include:

-includeTestToolkit: This parameter ensures that the Test Toolkit is included during the creation of the new container.

Given the limited context from the image, here's how you should complete the cmdlets for SandboxB:

Add -includeTestToolkit in the New-BcContainer script to ensure the Test Toolkit is installed when creating SandboxB.

Since you are setting up SandboxB from scratch, you don't need to run Install- TestToolkitToBcContainer separately as the toolkit will be included at the time of container creation with the -includeTestToolkit parameter. For the New-

BcContainer cmdlet, you would fill in the placeholders with the appropriate values for artifactUrl, imageName, and licenseFile if they are required for your specific setup.

Correct Answer:

Correct Answer:

Box 1: 'Authorization'

Business Central and the AL language have made web service code much easier with the HttpClient and Json types available. Handling the HTTP Authorization header is easier too with the TempBlob table, which can now encode the basic

authentication string using base64.

See below for an example of how to add a basic authorisation header to the AL HttpClient:

procedure AddHttpBasicAuthHeader(UserName: Text[50]; Password: Text[50], var HttpClient : HttpClient);

var

AuthString: Text;

TypeHelper: "Type Helper";

begin

AuthString := STRSUBSTNO('%1:%2, UserName, Password);

AuthString := TypeHelper.ConvertValueToBase64(AuthString);

AuthString := STRSUBSTNO('Basic %1', AuthString);

HttpClient.DefaultRequestHeaders().Add('Authorization', AuthString);

end;

Box 2: Base64Convert.ToBase64(Username + ':' + Passsword)

How To Connect To External APIs From Business Central (HTTP Request)

Authentication

There are several methods of authentication, basic, OAuth, etc. In the next example, you can see a way to use basic authentication.

We introduce 2 new types, HttpRequestMessage and HttpHeaders. They become fundamental when creating more complex API calls.

The way to build the call is quite simple:

Set the information for the message

Set the authorization in the header of the message

Send the request

Read and handle the response

Example:

Box 3: httpContent.WriteFrom(Body)

Example

The following example illustrates how to use the HttpContent type to send a simple POST request containing JSON data.

// Add the payload to the content content.WriteFrom(payload);

// Replace the default content type header with a header associated with this request content.GetHeaders(contentHeaders); contentHeaders.Clear(); contentHeaders.Add('Content-Type', 'application/json');

// Assigning content to request.Content will actually create a copy of the content and assign it.

// After this line, modifying the content variable or its associated headers will not reflect in

// the content associated with the request message

request.Content := content;

request.SetRequestUri(uri);

request.Method := 'POST';

Box 4: httpClient.Post(Url,httpContent,ResponseMessage) POST as required, and include ResponseMessage.

Scenario: The API for sending subcontracting orders must be called by sending an authenticated POST request to the given endpoint.

Scenario, full:

An external business partner of Contoso, Ltd. exposed a REST API for receiving details about new subcontracting orders and for sending the planned release date of each subcontracting order received.

Integration with business partner for subcontracting

Contoso, Ltd. must connect Business Central to the external API provided by the business partner. This will be used for the partner to send the details of new subcontracting orders to fulfill the sales demand, and for receiving the planned

release date of each order sent. The integration requirements are as follows:

The business partner will provide a REST API secured with basic authentication. Credentials to access the API will be shared with Contoso, Ltd.

The API for sending subcontracting orders must be called by sending an authenticated POST request to the given endpoint.

The API for retrieving the order no. and planned release date of each subcontracting order responds with the following JSON:

Reference:

https://dankinsella.blog/http-basic-authentication-with-the-al-httpclient/ https://businesscentralgeek.com/how-to-connect-to-external-apis-from-business-central-http-request https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/httpcontent/httpcontent-data-type

Correct Answer:

Step 1: Set the Clone procedure as ObsoleteState = Pending and ObsoleteReason = 'Not in use' in version 2.0.0.0 ObsoleteState Property Marks whether the object will be deprecated.

Property Value

*

No

Not obsolete. This is the normal/default setting.

*

Pending

Will become obsolete in a future version.

Syntax

ObsoleteState = Pending;

Remarks

By coding against this property, you can use this property as a way to communicate through code to other developers which objects and elements will become obsolete over time and those which are already obsolete, enabling them to adjust

their application code accordingly.

Note

For all elements, except for Tables and Table fields, setting ObsoleteState = Removed will throw Compiler Error AL0169 because after an appropriate warning state of Pending, these elements can be deleted.

Note

When developing using Dynamics NAV Development Environment (C/SIDE), you do not get warnings or errors when you compile objects that reference table objects, fields, or keys that are marked as Pending or Removed. ObsoleteState

property is only detected by the AL compiler, which will return warnings for references to elements marked as Pending and errors for references to elements marked as Removed.

Step 2: Set the Description field as ObsoleteState = Removed in version 2.0.01

Step 3: Remove the Description field from the issue table in version 2.0.0.1

Note: ObsoleteReason Property

Specifies why the object has been marked as Pending in the ObsoleteState property.

Syntax

ObsoleteReason = 'Not Needed';

Remarks

Use this property to inform developers about an object or element that will become obsolete in time or is already obsolete. Use the ObsoleteTag Property to specify additional information which can be valuable to other developers.

Scenario:

The Issue Management process must be split into two extensions:

-

ISSUE BASE: main extension

-

ISSUE EXT: second extension with dependency from ISSUE BASE

In the version 1.0.0.0 of the ISSUE BASE extension, you plan to create an Issue table that contains a global Decimal variable named IssueTotal.

In the version 1.0.0.0 of the ISSUE BASE extension, you plan to define a table named Issue Category with a Description field defined as follows:

The Issue table defined in ISSUE BASE extension contains a Clone procedure defined as follows:

In the ISSUE EXT extension, you create a tableextension object of the Issue table.

The tableextension object of the Issue table must access the IssueTotal: Decimal variable.

After weeks of usage, you discover that you must remove the Description field and the Clone procedure because they are no longer required.

Reference:

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-obsoletestate-property

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-obsoletereason-property

Correct Answer:

Use the company hardware architecture to run the deployment: On-premises Use sandbox environments to develop extensions: Online Allow tenants to connect to Shopify with the standard connector: Online Use Microsoft Power Automate to

create a workflow that calls a business event:

Online

When deploying Microsoft Dynamics 365 Business Central, there are two main deployment types to consider: On-premises and Online.

On-premises Deployment:

Online Deployment:

Therefore, each requirement aligns with the deployment types as indicated above.

Correct Answer:

To meet the XMLport configuration requirements:

Link the child table to its parent: Use the OnAfterGetRecord trigger. Display a confirmation message after the XMLport runs: Use the OnPostXMLPort trigger.

In Business Central, when you are developing an XMLport for data export, triggers are used to perform actions at different stages of the XMLport's operation:

OnAfterGetRecord Trigger:This trigger fires after a record is retrieved from the database but before it is processed for output in the XMLport. It is the ideal place to link child table records to their parent because you have access to the current

record that can be used to set filters or modify data in the child table before it is written to the XML file.

OnPostXMLPort Trigger:This trigger fires after the XMLport has finished processing all records. It is the correct place to display a confirmation message because it ensures that the message will appear after the entire XMLport operation is

complete. Here, you can use application-specific functions to show the message, such as MESSAGE function in AL code.

By placing the appropriate triggers in these positions, you can ensure that the XMLport will link the child records to their parent records during the data export process and will notify the user with a confirmation message once the operation is

successfully completed.

Correct Answer: E

Use the POST action.

Use Microsoft.NAV in the URL.

End the URL with Copy, not copy.

Scenario: The IT department creates a custom API for exposing the custom Issue table. The API provides an action for copying an issue to a new table. The action is defined as follows:

Contoso, Ltd. must create an API in Business Central to expose item details to the mobile application.

The API must have the lowest possible impact on the production environment when used during working hours.

The API must only support Get operations.

Reference:

https://businesscentralgeek.com/what-are-bound-actions-in-business-central-apis

Correct Answer: A

Initialize a snapshot debugging session

You can start a snapshot by creating a snapshot configuration file in Visual Studio Code.

Choose whether to run the session on a cloud service or locally. The configuration file contains the following information.

*

userId The GUID of the user who initiated the process to start snapshot debugging. For on-premises, this can also be the user name in user password authentication scenarios. The user must be able to start, or have a session type opened that is specified in the breakOnNext parameter.

*

Etc.

Scenario: Debugging problems A user of the ISSUE BASE extension in Business Central reports a problem.

You discover that the debugging is not triggering.

Incorrect:

Not B: Example (attach to a web client session)

The following example illustrates a configuration for a local server, where you want to debug a web client session.

...

{

"name": "My attach to local server",

"type": "al",

"request": "attach",

"server": "https://localhost",

"serverInstance": "BC200",

"authentication": "Windows",

"breakOnError": true,

"breakOnRecordWrite": false,

"enableSqlInformationDebugger": true,

"enableLongRunningSqlStatements": true,

"longRunningSqlStatementsThreshold": 500,

"numberOfSqlStatements": 10,

"breakOnNext": "WebClient"

} ...

Reference: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-attach-debug-next https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-snapshot-debugging

Correct Answer: B

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.