How Dimension Priority Works
Views (0)
In Microsoft Dynamics 365 Business Central, Dimension Priority is a subtle but powerful governance tool. It acts as the "tie-breaker" when the system receives conflicting information about how a transaction should be categorized.
Essentially, it tells Business Central: "If two different sources (like a Customer and an Item) both have a default value for the same dimension, use the value from the source with the higher priority."
By default, Business Central pulls dimensions from all entities involved in a transaction. However, if a Dimension Code (e.g., DEPARTMENT) is assigned to multiple accounts involved in a single entry, the system needs to know which one "wins."
The Logic Flow
- The Conflict: You create a Sales Order. The Customer is set to Department: SALES, but the Item is set to Department: PROD.
- The Priority: You define a ranking (1, 2, 3...) for different tables.
- The Result: The system automatically selects the value from the table with the lowest number (highest priority).
Use Case: Marketing vs. Product Sales
Imagine a company that runs specific Marketing Campaigns but also wants to track revenue by Product Line.
The Setup
- Dimension: AREA
- Customer (CUST001): Has a default AREA of NORTH.
- Salesperson (SP01): Has a default AREA of CAMPAIGN-X.
A salesperson (SP01) sells a product to Customer (CUST001).
- The Customer card wants to tag the revenue to their geographic region (NORTH).
- The Salesperson card wants to tag the revenue to their specific campaign (CAMPAIGN-X).
If the company decides that Salesperson performance is the most important metric for this period, they would set the Priority as follows:
- Salesperson Table: Priority 1
- Customer Table: Priority 2
The Result: When the invoice is posted, Business Central automatically assigns CAMPAIGN-X to the AREA dimension, overriding the Customer's geographic tag. This ensures clean data for the sales team's commission reports without manual adjustment.

Like
Report
*This post is locked for comments