PDF MB-800 Study Guide

The requirement is: “You need to configure retail store customer cards to track revenue by market.”

In Business Central, to track revenue by customer market (Retail, Veterinarian, Breeder), you configure default dimensions on the Customer Card.

Assign the dimension code → Market

The business wants to analyze revenue by Market (Retail, Veterinarian, Breeder).

Therefore, the dimension code must be Market.

Assign the dimension value code → Retail

For this specific setup, the customer is a retail store, so the dimension value must be Retail.

Select a value posting → Same code

To ensure that every posting for this customer always carries the same dimension value, use Same Code.

Other options:

Blank = no default dimension.

No code = optional dimension.

Code mandatory = requires entry but allows flexibility in values.

Since we want strict tracking by a fixed market (Retail), Same code is correct.

This ensures that every transaction posted for the customer will always have Market = Retail, enabling accurate revenue tracking.

Microsoft Learn references:

Work with Dimensions

Set Up Default Dimensions

Dimension Value Posting Options

In Dynamics 365 Business Central, default dimensions ensure that a required dimension is automatically suggested or enforced when creating transactions for entities such as Customers, Vendors, G/L Accounts, etc.

Step-by-step process to make a dimension mandatory for Customers:

Select Account Type Default Dim.

Navigate to Search → Default Dimensions.

Here you define which account type (Customer, Vendor, Item, etc.) will be linked to dimensions.

Select the relevant table ID.

Choose the entity (Customer table ID = 18) for which the default dimension setup will apply.

On the Dimensions page, select the required dimension.

For example, " DEPARTMENT " or " REGION. "

This ensures the dimension is linked to the Customer entity.

Leave the dimension value blank, and in the Value Posting column, select Code Mandatory.

This ensures that a transaction cannot be posted without a dimension value being entered.

Leaving the dimension value blank enforces flexibility (any value allowed), while Code Mandatory ensures it is always required.

Other options not correct for this requirement:

Define the dimension value and set it in Value Posting → would automatically assign a fixed dimension value, but the requirement is just to make it mandatory, not fixed.

Disable the dimension value from posting → prevents posting, not useful here.

Microsoft Learn References

Set Up Default Dimensions for Customers, Vendors, and Other Accounts

Enforce Dimension Rules with Default Dimensions

Business Central Functional Consultant at end of each question below

The requirement is:

Purchasing agents must create and post purchase documents (which requires permissions to vendors, purchase headers/lines, posting routines).

They must be restricted from viewing General Ledger (G/L) balances and amounts.

They must still be able to select G/L accounts when coding purchase lines.

In Business Central, this scenario is solved by using Permission Sets with Security Filters:

Assign a Permission Set to the User

The purchasing agent must first be assigned a permission set (e.g., PURCHASER, or a custom one cloned from SUPER with reduced rights).

This ensures they have access to vendors, purchases, and posting processes.

Select the Permission Set to Modify

You then open the permission set (or copy/create a new one for Purchasing Agents).

Modify it to apply restrictions specifically for the G/L Account table.

Apply Security Filters on the G/L Account Table

Locate the G/L Account table within the permission set.

In the Security Filter column, choose the field Income/Balance.

Set the Filter Value to Income only (or exclude Balance).

Alternatively, set the filter on Direct Posting = Yes, ensuring they can pick accounts but not see balances.

This filter prevents access to balance-related fields, effectively hiding financial values from the user while allowing them to still select G/L codes for posting.

Thus, the correct sequence to meet the requirements is:

Assign a permission set to a user

Select the permissions set you want to modify

In the row for G/L account table, select the Security Filter column

In the Field Filter column, set the value to hide balances

Microsoft Learn References

Security Filters (how to restrict data visibility by table fields):

Assign Permission Sets to Users:

Create and Modify Permission Sets: