Microsoft Updated MB-800 Exam Questions and Answers by orhan

Comprehensive Detailed Explanation

The requirement is to ensure that every transaction posted to a customer account includes the Customer Source dimension (e.g., Cash & Carry, Brokered). This is achieved by creating and enforcing a mandatory dimension rule in Business Central.

Step 1: Create a dimension code to identify the customer source

First, define a Dimension Code such as Customer Source.

This will hold values like Cash & Carry and Brokered.

Dimensions are the foundation for all reporting segmentation in Business Central.

Step 2: Create dimension values for the customer source dimension code

After creating the dimension, define the specific Dimension Values (e.g., Cash & Carry, Brokered).

These represent the business lines the company wants to track.

Step 3: Add the Customer table

To enforce the dimension on customers, link the dimension to the Customer table.

This ensures that every transaction involving a customer account requires this dimension.

Step 4: Set the Value Posting to Code Mandatory

On the Default Dimensions page, set Value Posting = Code Mandatory for the Customer Source dimension.

This forces users (or the system) to provide a dimension value on every transaction involving customers.

Without this, users might skip dimension assignment, leading to incomplete reporting.

Step 5: Select the Dimension Value Code that is used for the customer source

Finally, assign the correct Dimension Value (Cash & Carry or Brokered) to each customer record.

This ensures automatic defaulting during transaction entry, reducing user errors and maintaining consistency.

Why not the other actions?

Chart of Accounts: Not needed here, since the requirement applies to customers, not G/L accounts.

Account Type Default Dimension: Useful for G/L accounts, but here we are applying it at the Customer table level.

Search icon, Customers: While this helps you navigate, it’s not a required setup step in the sequence.

Microsoft References

Work with Dimensions in Business Central

Set Up Default Dimensions for Customers

Dimension Value Posting Options

Comprehensive Detailed Explanation

The requirement is to report profitability by business line (cash & carry vs. brokered). In Business Central, the way to achieve this is by creating a Global or Shortcut Dimension (for example, a dimension called Business Line) and ensuring that it is captured on every sales, purchase, and general ledger transaction.

Create a dimension → Value

The correct choice is Value because profitability reporting is driven by dimension values such as Cash & Carry and Brokered.

Combination, Default Priorities, and Account Type Default are used for control and automation of dimensions, not for the initial creation of reporting dimensions.

The requirement is to configure the new customer creation process in Dynamics 365 Business Central. The goal is to make sure that when users quickly add new customers (for example, at the Cash & Carry desk), all required fields and correct defaults are consistently applied.

1. Configuration Worksheet (B)

The Configuration Worksheet is used in RapidStart Services to plan and manage setup data across tables.

It lets you map out which tables (e.g., Customers, Vendors, Items) you want to configure and load master data into.

For customer creation, this ensures that the Customer table and related setup tables are properly configured before using templates.

This acts as the foundation of the process: deciding what must be included in the customer creation workflow.

2. Configuration Template (C)

Configuration Templates define default values for new master data records (e.g., customers, vendors, items).

For example, when creating a new customer, the template can pre-fill fields like:

Posting groups

Payment terms

Customer source dimension

Responsibility center (if required)

This ensures consistency and reduces errors when users add new customers.

In this scenario, since the company wants fast and accurate customer creation, templates are essential.

Why not A (Responsibility center)?

Responsibility centers are used to manage operations by location, department, or profit center.

They are useful for reporting and segregation of transactions, but not mandatory for customer creation setup.

Why not D (Permissions)?

Permissions define who can create or modify customers.

While important for security, this is not part of the configuration process for ensuring consistent field population and defaults in customer creation.

Microsoft References

Set Up Configuration Packages and Templates (RapidStart Services)

Configuration Templates for Customers, Vendors, and Items

Customer Table Setup and Creation

This sequence makes sense because you first create the series itself, then define the lines (the actual numbers within the series), and finally define the relationships to link the series to the specific data table (like the Accounts table) where it will be used.

Sequence 2: Using a Configuration Package to Manage Data

This sequence focuses on using a configuration package to manage and update data, which might include fixing issues with existing accounts or importing new ones.

Create a configuration package.

Configure the Vendor Table on the configuration package.

Create the Data template.

While this sequence is plausible, it has a significant flaw: the prompt mentions " Accounts, " but this sequence specifically mentions the Vendor Table. If we assume the " Vendor Table " is a placeholder for a generic data table like the Accounts table, the sequence makes sense. You create a package, configure it for a specific table, and then create a data template to import the data into that table.

Sequence 3: Resolving Issues by Defining the Number Series on the Configuration Template

This sequence focuses on resolving issues by directly modifying the configuration template within a configuration package.

Create a configuration package.

Create the Data template.

Define the No. Series on the configuration template.

This sequence is logical for a scenario where you ' re using a configuration package to manage both data and its associated number series. You first create the package, then create the data template (which is a core component of the package), and finally define the number series on that template to ensure the imported data uses the correct number sequencing.