MB-820 Online Practice Questions and Answers

Correct Answer:

Correct Answer:

Scenario: When a purchase order with incorrect quantity or quality issues is received, the entity must create a non-conformity document in the system. The following information must be included in the document:

*

Comments: can include comments with rich text and pictures to illustrate quality problems

*

etc.

Box 1: MultiLine = true;

Rich Text and content controls

The Rich Text feature in Business Central is designed to handle multimedia content, such as social media posts, email bodies, quick annotations, file contents, or any field that requires a mix of text, tables, links, and images.

Both ExtendedDataType and Multiline are required to render a Rich Text Editor ExtendedDataType = RichContent; MultiLine = true;

Box 2: ExtendedDataType

Box 3: RichContent

Reference: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-richtext-content-controls

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:

Step 1: Create an Azure Application Insights instance by using the Azure Portal in the Partner's subscription.

Scenario: External business partner

The external business partner must add custom telemetry to an application created for Contoso, Ltd. to monitor a business process.

Custom telemetry signals for the application must be visible only on the partner's telemetry.

Step 2: Select the environment in the Admin Center and place the connection string in the Application Insights Connection String field.

Connection strings

Connection strings define where to send telemetry data.

Find your connection string

Your connection string appears in the Overview section of your Application Insights resource.

Note: When you create a custom telemetry trace signal, you can specify the scope of the event. The telemetry scope determines if the event is only sent to the Azure Application Insights resource specified in the extension's app.json or if the

event is also sent to the Azure Application Insights resource of the environment where the extension is installed.

Step 3: Select the Application Insights instance, select Logs and then inspect the Traces table.

Custom events in Log Analytics

The telemetry is available in the customEvents table on the Application Insights Logs tab or usage experience.

Create a custom telemetry event

To create a custom telemetry event, use the LogMessage method in AL code where you want to trigger the signal. The LogMessage method defines the information that is sent to Azure Application Insights for a specific operation or activity.

There are two variations of the LogMessage method. The difference is that one method uses a dictionary object to define custom dimensions for the trace signal. The other method includes two overloads so you don't have to construct a

dictionary. You can use these methods in any object, trigger, or method.

Incorrect:

* Select the Sessions menu and then select Restart Environment.

Reference: https://learn.microsoft.com/en-us/azure/azure-monitor/app/api-custom-events-metrics https://learn.microsoft.com/en-us/azure/azure-monitor/app/sdk-connection-string

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 assign the indirect permissions for the Boxes table to the codeunit, use the following code blocks in sequence: TableData "Boxes" = Permissions RIM Assigning permissions:In Business Central, to assign permissions within a codeunit, you need to specify the table that the permissions apply to, followed by the type of permission. The sequence starts by indicating that we are defining table data permissions (TableData ). Then, we specify the table in question ("Boxes" =). After that, we state that we are setting permissions (Permissions). Finally, we assign the RIM permissions, which stands for Read, Insert, and Modify permissions. The Indirect permission allows the codeunit to read, insert, and modify records in the Boxes table indirectly, meaning these operations can be performed by the codeunit when it is called by a user who has direct permissions for these operations.

Correct Answer:

To make the permission set visible on the Permission Sets page, perform the following actions in sequence:

Change the Assignable property value to true.

Add the ObsoleteState = No property.

Publish the app with the permission set to an environment. Process for making permission sets visible:In Business Central, the Assignable property determines whether a permission set is shown in the user interface for assigning to users. By

default, if Assignable is set to false, the permission set is hidden. Therefore, it should be set to true to make the permission set visible. The ObsoleteState property indicates whether an object is outdated (Obsolete) or not (No ). If an object is

marked as obsolete, it is typically hidden from the user interface. Therefore, setting ObsoleteState = No ensures that the permission set is not treated as outdated and remains visible.

Finally, publishing the app with the permission set to an environment updates the environment with the new or modified objects, including permission sets, making them available for assignment to users.

Correct Answer:

Developed by using any coding language: Connect app Developed by using AL language in Visual Studio Code: Add-on app

In Microsoft Dynamics 365 Business Central, there are distinct types of applications that can be developed: Connect apps and Add-on apps. Each has its own development language requirements:

Connect apps:

Add-on apps:

The language and environment used for developing these apps are key differentiators between Connect apps and Add-on apps.

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: A

For a task that is performed infrequently and requires users to follow a sequence of steps, a wizard-like interface is ideal. In Microsoft Dynamics 365 Business Central, the NavigatePage page type (A) is best suited for this purpose. NavigatePage is designed to guide users through a series of steps or pages, allowing them to complete a task by making choices or entering data in a structured manner. This page type is often used for setup wizards, data migration tasks, or any other process that benefits from a step-by-step approach. Unlike the other page types like Card (B), RoleCenter (C), or List (D), NavigatePage specifically supports the navigation and decision-making flow required for wizard creation, making it the optimal choice for this requirement.