The Microsoft Dynamics 365 Business Central Developer (MB-820)

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.

You are working on an on-premises Business Central instance and unable to download symbols for a new AL project. The current configuration in launch.json does not allow you to download symbols, and you need to make corrections.

Key Points in the Scenario:

Instance name is TEST .

Developer services port is 7149 .

Windows authentication is being used.

Correct Answers:

A. Change the server Instance parameter to TEST.

The serverInstance parameter must match the name of the Business Central instance, which is TEST in this scenario. You need to modify this to reflect the correct instance name.

B. Add the port: 7149 parameter.

Since the developer services are using port 7149 , you need to specify this in the launch.json file by adding the port parameter with the value 7149 .

Incorrect Options:

C. Change the name parameter to TEST : The name parameter is just a label and does not affect downloading symbols, so changing this won ' t help.

D. Change the authentication parameter to UserPassword : The authentication method is already set to Windows , which is valid for this scenario. Changing it to UserPassword is unnecessary unless specified by the system.

E. Check which server the instance is installed on and replace http://localhost with the correct IP address : Since the server is on the same machine as Visual Studio Code (as specified), localhost is correct.

Handler methods are used in tests to simulate user interactions, such as responding to dialogs, confirmation messages, or option selections. Since you need to simulate the user interaction of selecting a posting option (Ship, Invoice, Ship & Invoice), a Handler method would be the appropriate choice for capturing this kind of user input.

Normal attribute and Test attribute are used for marking methods for test execution, but they do not simulate user interaction, making Handler method the correct answer.

For more details, see the Microsoft Docs on Test Codeunits and Handler Methods .

In the context of Microsoft Dynamics 365 Business Central, an extension may not appear in the tenant for several reasons, particularly after an upgrade to a new major version.

Option A suggests that the extension was published as a DEV extension, which typically would not cause it to disappear after an upgrade because DEV extensions are intended for development and testing within sandbox environments.

Option B indicates that the extension was not compatible with the new version within 60 days of the first notification. This is a likely reason because Microsoft enforces compatibility rules, and extensions that are not made compatible within the specified timeframe might be removed or disabled.

Option C refers to the extension being published as a PTE (Per-Tenant Extension) and mentions the Platform parameter not being updated. This could cause issues, but not specifically the disappearance of the extension after an upgrade.

Option D expands on Option C by adding that both the Platform and Runtime parameters were not updated in the application file. This is a critical aspect because if these parameters are not correctly set to indicate compatibility with the new version of Business Central, the extension could be disabled or removed.

Option E is similar to Option B but mentions a 90-day period. This option does not align with standard Business Central practices for version compatibility requirements.

Therefore, the two possible reasons for the disappearance of the extension in the tenant after an upgrade are that the extension was not compatible with the new version within the required timeframe (Option B) and that the extension was published as a PTE without the Platform and Runtime parameters being updated (Option D).

In Microsoft Dynamics 365 Business Central, when configuring snapshot debugging, it is crucial that the parameters in the configuration file are correctly set. From the options provided, the issue with the debugger not starting correctly is most likely due to an incorrect " userId " parameter.

Option A is the cause of the problem. The " userId " parameter must be the GUID of the user, not the username. The snapshot debugger needs the exact GUID to attach to the right session for debugging.

Option B is incorrect because " breakOnNext " set to " WebClient " is a valid setting. This tells the debugger to break on the next client action in the web client, which is a typical scenario.

Option C is not the cause of the problem. The " userId " parameter is meant to specify which user session to debug, and this works in conjunction with the " breakOnNext " parameter.

Option D is incorrect as the " executionContext " parameter does not need to be set to " Debug " for snapshot debugging to work. " DebugAndProfile " is a valid value for the " executionContext " parameter, as it allows for debugging and collecting performance information.

Therefore, the reason why the debugger does not start correctly is due to Option A: The " userId " parameter must have the GUID of the user specified, not the username.