MB-820 Online Practice Questions and Answers

Correct Answer:

For the data integrity requirements, the table field properties to use are:

To establish lookups into other records, use the TableRelation property. To validate if a record exists in a destination record, use the ValidateTableRelation property.

In Business Central, when creating tables to hold data, maintaining data integrity is crucial:

TableRelation Property:This property is used to create a relationship between the field in one table and a field in another table, which is typically used for lookups. When you set the TableRelation property on a field, it allows users to select

from a list of values that exist in the related table.

ValidateTableRelation Property:This property is used to ensure that the value entered in a field matches one of the values in a related table. If a user tries to enter a value that doesn't exist in the related table, an error will occur.

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:

Correct Answer:

To roll back changes to a test method after run time, you should:

Set the TransactionModel attribute to AutoRollback. To run an approve action on a test page named TestPageA, you should:

Configure TestPageA.Approve.Invoke().

In Business Central's testing framework, the TransactionModel attribute can be set to AutoRollback. This ensures that any changes made during the test are rolled back after the test is complete, leaving the database in its original state. For

running an action on a test page, you would use the 'Invoke' method on the action you wish to perform. In this case, to run an approve action on TestPageA, you would use TestPageA.Approve.Invoke() within your test codeunit. This simulates

the user action of approving something on the page.

These actions ensure that the testing environment is properly set up to test specific functionalities without persisting test data and to invoke actions as part of the test scenarios.

Correct Answer:

For the given requirements, you should configure the following actions:

For child data items not to be displayed on the request page for some master- detail reports, set the DataItemLinkReference property to the parent data item. To decrease the amount of time to select key filter fields, specify the

RequestFilterHeading property.

In Dynamics 365 Business Central, when customizing report request pages, certain properties can be set to control the behavior and display of the report options:

Hiding Child Data Items:The DataItemLinkReference property is used to link a child data item to a parent data item in the data model of a report. Setting this property correctly will ensure that the child data items are related to the correct

parent data item and will be displayed or hidden accordingly on the request page. If the goal is to prevent child data items from being displayed, you need to make sure they are correctly linked and configured to not appear. Optimizing Filter

Field Selection:The RequestFilterHeading property is used to group filter fields on the request page. By specifying this property, you can create a more organized and user-friendly interface, which can significantly speed up the process of

selecting filters. This property allows you to categorize filters into headings, making it quicker and easier for users to find and set the necessary filters for the report.

By adjusting these properties on the report request page as part of the per tenant extension customization, you will address the company's requirements to optimize the user experience when running reports.

Correct Answer:

Enclose line 08 into BEGIN .. END = NO Add TopCustomerOverview.Open(); before = YES TopCustomerOverview.SetFilter(Sales_LCY, '>10000'); in line 06. Add TopCustomerOverview.Open(); after TopCustomerOverview.SetFilter(Sales_LCY, '>10000'); in line 06. = YES Replace SetFilter in line 06 with SetRange. = NO

The code provided has a runtime error because the query TopCustomerOverview must be opened before it can be read from. Therefore, TopCustomerOverview.Open(); should be added before trying to read from the query, which is not present in the code. Enclosing line 08 into a BEGIN .. END block is unnecessary because it is a single statement, and AL does not require a BEGIN .. END block for single statements within trigger or procedure bodies. TopCustomerOverview.SetFilter(Sales_LCY, '>10000'); is a correct method to set a filter for the query, and using SetRange instead is not necessary unless the requirement is specifically to set a range of values, which is not indicated in the procedure's description. In summary, for the procedure to run correctly, the query must be opened after setting the filter and before attempting to read from it. The SetFilter method is correct for the intended operation, and there's no requirement to use SetRange or to enclose the Message call in a BEGIN .. END block.

Correct Answer:

procedure BlockNonSItems()

var

Item: Record Item;

begin

// Reset the Item record to clear any previous filters.

Item.Reset();

// Set the filter to exclude items that start with 'S'.

Item.SetFilter("No.", '<>%1*', 'S');

// Find each item that matches the filter.

if Item.FindSet() then

repeat

// Set the Blocked field to true to block the item.

Item.Blocked := true;

// Save the changes to the Item record.

Item.Modify();

until Item.Next() = 0; // Continue until no more items are found.

end;

Correct Answer:

Box 1: CreateOutStream Box 2: CreateInStream Box 3: Instream Reference:

https://community.dynamics.com/blogs/post/?postid=19ce850a-6ff7-4b99-8b3c-65aa6411771b

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:

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

To ensure the most recent Business Central artifact URL is selected for setting up a local Business Central Development Docker container, the command to use is Get-BcArtifactUrl -type sandbox -select Current (A). This PowerShell command retrieves the URL for the latest available Business Central artifact for a sandbox environment, ensuring that the Docker container is set up with the most up-to-date version for testing new project ideas. The -select Current parameter is crucial as it specifies that the current, or latest, version of the artifact is to be retrieved, as opposed to selecting a version based on other criteria such as Closest, NextMinor, or NextMajor.

Correct Answer: A

When creating a test codeunit in Microsoft Dynamics 365 Business Central to write unit test functions, the SubType property (A) of the codeunit should be set to Test. This property is crucial for defining the codeunit's purpose and behavior within the application. By setting the SubType property to Test, you are indicating that the codeunit contains test functions intended to validate the functionality of other parts of the application, such as customizations or new developments. This distinction ensures that the testing framework within Business Central recognizes the codeunit as a container for test functions, allowing it to execute these functions in a testing context, which can include setting up test data, running the tests, and cleaning up after the tests have completed.

Correct Answer: D

In the context of cleaning up sandbox environments for a company where data needs to be cleared each time an extension is published, the schemaUpdateMode property in the launch.json file should be set to Recreate (D). Setting this property to Recreate ensures that every time the extension is published, the existing tables and data are dropped, and then the tables are recreated based on the current extension's schema. This mode is particularly useful in development and testing environments where you need a clean slate for testing each version of the extension without the remnants of previous data affecting the outcomes. It's important to use this setting cautiously, as it results in the loss of all existing data in the tables defined by the extension, which is suitable for a sandbox environment but not for production environments.