Study guide
4.2 Global Dimensions vs Shortcut Dimensions
Microsoft Dynamics 365 Business Central Functional Consultant MB-800
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Company Creation & Data Migration
1.1 Creating Companies & Assisted Setup Wizards 1.2 Configuration Packages & RapidStart Worksheets 1.3 Opening Balances & Data Migration Strategies
2 Chapter 2: Security, Profiles & Auditing
2.1 Users, User Setup & Role Center Profiles 2.2 Permission Sets & Security Group Management 2.3 Security Filters, Change Log & Security Auditing
3 Chapter 3: Core System Configuration, Number Series & Copilot
3.1 Company Information, Number Series & Job Queues 3.2 Report Layout Management & Copilot AI Capabilities
4 Chapter 4: Dimensions Architecture & Governance
4.1 Dimension Concepts & Dimension Values 4.2 Global Dimensions vs Shortcut Dimensions 4.3 Default Dimensions, Combinations & Priorities
5 Chapter 5: Workflows & Approvals
5.1 Native Workflow Templates & Approval Hierarchy 5.2 Workflow User Groups & Notification Configuration
6 Chapter 6: Financial Setup, Periods & Currencies
6.1 General Ledger Setup & Accounting Periods 6.2 Payment Terms, Payment Methods & Deferrals 6.3 Multi-Currency Setup & Exchange Rates
7 Chapter 7: Chart of Accounts, Categories & Allocations
7.1 Chart of Accounts Structure & G/L Account Cards 7.2 Account Categories, Subcategories & Financial Reporting 7.3 General Ledger Allocation Accounts & Sharing
8 Chapter 8: Posting Groups & Posting Setup
8.1 Specific Posting Groups: Customer, Vendor, Bank & Inventory 8.2 General Posting Groups & General Posting Setup Matrix 8.3 Inventory Posting Setup & Alternative Posting Groups
9 Chapter 9: General Journals & Recurring Methods
9.1 Bank Account Cards & Posting Setup 9.2 General Journal Templates, Batches & Number Series 9.3 Recurring General Journals & Allocation Methods
10 Chapter 10: Accounts Payable & Accounts Receivable Setup
10.1 Purchases & Payables Setup & Vendor Master 10.2 Sales & Receivables Setup & Customer Master 10.3 Payment Journals, Cash Receipts & Payment Registration Setup
11 Chapter 11: Fixed Assets Setup & Depreciation Books
11.1 Fixed Asset Setup, Classes & Depreciation Books 11.2 Fixed Asset Cards, Main/Component Assets & Depreciation Methods
12 Chapter 12: Inventory Setup, Costing & Locations
12.1 Inventory Setup, Item Types, Categories & Variants 12.2 Costing Methods (FIFO, LIFO, Average, Standard) & Ledger Architecture 12.3 Locations, Transfer Routes & Stockkeeping Units (SKUs)
13 Chapter 13: Logistics Master Data, Pricing & Discounts
13.1 Shipping Agents, Locations & Vendor Lead Times 13.2 Sales Prices, Purchase Prices & Price Lists 13.3 Line Discounts, Invoice Discounts & Thresholds
14 Chapter 14: User Interface, Views, Inspection & Excel
14.1 Personalization, Profile Customization & Designer 14.2 Searching, Advanced Filters, Saved Views & Page Inspection 14.3 Edit in Excel, OneDrive & Data Analysis Mode
15 Chapter 15: Purchase & Sales Order Execution
15.1 Purchase Orders, Receiving, Over-Receipt & Undo 15.2 Purchase Invoicing, Recurring Lines & Blanket Orders 15.3 Sales Quotes, Availability Checks & Order Conversion 15.4 Sales Shipping, Invoicing, Undo & Blanket Orders
16 Chapter 16: Invoices, Credit Memos & Document Corrections
16.1 Direct Invoices, Credit Memos & Document Reopening 16.2 Correct, Cancel & Corrective Credit Memo Procedures 16.3 Combined Shipments/Receipts & Prepayment Workflows
17 Chapter 17: Cash Management, Bank Reconciliation & Ledger Applications
17.1 Processing Payment Journals & Cash Receipt Registrations 17.2 Applying, Unapplying & Reversing Customer/Vendor Entries 17.3 Bank Account Reconciliation & Statement Matching Rules
18 Chapter 18: Operational Adjustments, Inventory & Asset Accounting
18.1 Exchange Rate Adjustments & Dimension Corrections 18.2 Inventory Adjustments, Transfers & Physical Counting 18.3 Fixed Asset Acquisitions, Depreciation Runs & Disposals
4.2 Global Dimensions vs Shortcut Dimensions
Key Takeaways Explain This Topic AI
Global Dimension 1 and Global Dimension 2 are stored directly as physical table columns on every document, journal, and ledger table (such as Table 17 G/L Entry), allowing instantaneous zero-join querying and FlowFilter calculation.
Shortcut Dimensions 3 through 8 are configured in General Ledger Setup and stored in Table 480 Dimension Set Entry behind an integer Dimension Set ID, and changing one is not free either: current Business Central rewrites every posted entry that carries the dimension, through the separate Change Dimensions action.
The Dimension Set architecture normalizes dimensional storage into an immutable relational tree, drastically reducing database bloat by ensuring identical combinations of dimensions share a single integer identifier.
Changing Global Dimensions runs from the Change Global Dimensions page in General Ledger Setup: Sequential mode (the default) uses Start directly, while Parallel mode requires Prepare, a sign-out and sign-in, and then Start.
Executing a Global Dimension change places extensive table locks across transactional and ledger tables, requiring execution during maintenance windows and monitoring via Change Global Dimensions Log entries.
Last updated: September 2026
4.2 Global Dimensions vs Shortcut Dimensions
Exam Focus: A critical distinction on the MB-800 exam is the difference between Global Dimensions and Shortcut Dimensions. Candidates must master where each is stored, how Global Dimensions 1 and 2 provide instant FlowFilter querying on the Chart of Accounts, how Shortcut Dimensions 3–8 leverage Table 480 Dimension Set Entries, and the exact steps, execution modes, and locking safeguards involved in changing global dimensions.
In Dynamics 365 Business Central, all dimensions are not stored or queried equally. To balance high-volume transaction throughput, instant financial reporting, and schema normalization, Business Central partitions dimensions into two technical tiers: Global Dimensions and Shortcut Dimensions .
1. Architectural Distinction: Global Dimensions vs. Shortcut Dimensions
The configuration hub for an organization's core dimensional framework resides in General Ledger Setup ( Page 118 ). UI Navigation Path:
- Tell Me (Alt+Q) -> General Ledger Setup -> Dimensions FastTab
- Global Dimensions (Global Dimension 1 & Global Dimension 2)
An enterprise selects two primary dimensions to serve as Global Dimension 1 and Global Dimension 2 (e.g., DEPARTMENT and PROJECT ). These two dimensions are fundamental to the ERP database schema:
Physical Table Columns: Business Central adds dedicated physical columns directly to almost every document, journal, and ledger table in the system:
Table 17 G/L Entry contains Global Dimension 1 Code and Global Dimension 2 Code .
Table 21 Cust. Ledger Entry and Table 25 Vendor Ledger Entry contain both fields.
Table 32 Item Ledger Entry , Table 169 Job Ledger Entry , and Table 271 Bank Account Ledger Entry contain both fields.
Table 36/37 Sales Header / Sales Line and Table 38/39 Purchase Header / Purchase Line contain both fields.
Instant Zero-Join Filtering: Because these codes reside directly as native columns on ledger tables, SQL queries filter by Global Dimension 1 and 2 without performing relational joins across secondary dimension tables. Direct database indexes exist on these columns, enabling microsecond query speeds.
Chart of Accounts FlowFilters: Global Dimensions 1 and 2 automatically become native FlowFilters on Table 15 G/L Account ( Global Dimension 1 Filter and Global Dimension 2 Filter ). Users can open the Chart of Accounts, set a FlowFilter for Global Dimension 1 = SALES , and see instantaneous, real-time recalculations of Net Change and Balance at Date across every account without running a report.
Shortcut Dimensions (Shortcut Dimensions 1 through 8)
In General Ledger Setup , administrators can configure up to eight Shortcut Dimensions :
Shortcut Dimensions 1 and 2: Permanently bound to Global Dimension 1 and Global Dimension 2 . Any change to Global Dimension 1 or 2 automatically updates Shortcut Dimension 1 or 2.
Shortcut Dimensions 3 through 8: Six additional dimensions selected to facilitate direct user data entry on operational pages (e.g., CUSTOMERGROUP , AREA , SALESCAMPAIGN , PRODUCTLINE ).
Unlike Global Dimensions 1 and 2, Shortcut Dimensions 3 through 8 are not stored as individual physical columns on Table 17 G/L Entry or other posted ledger tables. Instead, they are captured via the Dimension Set Architecture and referenced through a single foreign key: Dimension Set ID .
Architectural Comparison Matrix
Architectural Feature Global Dimensions (1 & 2) Shortcut Dimensions (3 through 8)
Configuration Location General Ledger Setup ( Global Dimension 1/2 Code ) General Ledger Setup ( Shortcut Dimension 3-8 Code )
Database Storage Mechanism Physical columns directly on all transactional & ledger tables Normalized in Table 480 Dimension Set Entry via Dimension Set ID
SQL Joins Required for Queries Zero joins (Direct indexed column lookup) Relational join to Table 480 or Analysis View tables
G/L Account Native FlowFilters Yes ( Global Dimension 1/2 Filter native fields) No (Requires an Analysis View or Financial Report)
Direct Line Entry in UI Visible and editable on document & journal lines Visible and editable on document & journal lines
Standard Out-of-the-Box Reports Pre-built filters and groupings on almost all reports Available where reports explicitly support dimension sets
Cost to Modify After Posting Very High (Rewrites physical columns on every posted table via Change Global Dimensions ) High (Still rewrites posted entries, but through the separate Change Dimensions action)
2. The Dimension Set Architecture & Table 480 Optimization
To understand why Business Central limits direct physical columns to two Global Dimensions, one must examine the underlying relational database architecture.
The Legacy Architecture Problem (Pre-NAV 2013)
In legacy versions of Dynamics NAV, every time a document line or journal posted, the system inserted a separate row into a Ledger Entry Dimension table for every single dimension assigned to that entry . If a company posted a general journal with 5,000 lines and 6 dimensions per line, the posting engine inserted: 5 , 000 G/L Entries + ( 5 , 000 × 6 ) = 30 , 000 Ledger Entry Dimension rows 5,000 \text{ G/L Entries} + (5,000 \times 6) = 30,000 \text{ Ledger Entry Dimension rows} 5 , 000 G/L Entries + ( 5 , 000 × 6 ) = 30 , 000 Ledger Entry Dimension rows
Over several years, ledger dimension tables grew into tens of millions of redundant rows, causing severe database bloat, buffer cache thrashing, and prolonged transaction locking during month-end closes.
The Modern Dimension Set Architecture
Starting with NAV 2013 and continuing in Dynamics 365 Business Central, Microsoft introduced the Dimension Set Engine centered around Table 480 Dimension Set Entry .
A Dimension Set is an immutable, unique combination of dimension values. Instead of storing separate dimension rows for every transaction, Business Central stores each unique combination exactly once in Table 480: Table 480: Dimension Set Entry
- +------------------+----------------+----------------------+-------------------+
- | Dimension Set ID | Dimension Code | Dimension Value Code | Dimension Value ID|
- +------------------+----------------+----------------------+-------------------+
- | 4120 | DEPARTMENT | SALES | 12 |
- | 4120 | PROJECT | ALPHA | 84 |
- | 4120 | AREA | NORTH | 31 |
- +------------------+----------------+----------------------+-------------------+
- | 4121 | DEPARTMENT | SALES | 12 |
- | 4121 | PROJECT | BETA | 85 |
- | 4121 | AREA | NORTH | 31 |
- +------------------+----------------+----------------------+-------------------+
- The Dimension Set Tree (Codeunit 408)
When a user enters dimensions on a document line or journal:
Codeunit 408 DimensionManagement evaluates the combination of dimension values in an in-memory binary search tree ( Dimension Set Tree ).
If the exact combination has ever been used before in the company, Business Central retrieves the pre-existing Dimension Set ID (a 4-byte integer, such as 4120 ).
If the combination is brand new, Business Central generates the next sequential Dimension Set ID , commits the normalized rows to Table 480, and registers the node in the tree.
When the document posts, Table 17 G/L Entry only writes the 4-byte integer Dimension Set ID = 4120 .
Result: If 100,000 sales order lines share the identical combination of Department, Project, and Area, Table 480 contains only 3 rows, and every ledger entry stores only a single 4-byte integer. Storage footprint is reduced by over 80%, and posting concurrency increases dramatically.
3. Changing Global Dimensions: Procedure & Scheduling Modes
Organizations frequently restructure their business operations. A company that initially established AREA as Global Dimension 2 may determine two years later that PROJECT must become Global Dimension 2 to enable instant balance sheet project filtering.
Because Global Dimensions are physical columns across every transaction and ledger table, changing them requires rewriting database fields across potentially millions of historical rows. To manage this safely, Business Central provides the Change Global Dimensions administrative utility ( Page 483 ). (Shortcut Dimensions 3 through 8 are also rewritten when changed, but through the separate Change Dimensions action rather than this page.) UI Navigation Path:
- Tell Me (Alt+Q) -> General Ledger Setup -> Actions -> Change Global Dimensions
- Step-by-Step Administrative Procedure
Open the Change Global Dimensions page.
At the top of the page, choose the run mode first — the mode decides which action you use at the end:
Sequential (this is the default ): the change runs as a single transaction in the current session. Microsoft recommends it when the company has relatively few posted entries, because it finishes in the shortest time. It locks multiple tables and blocks other users until it completes, and on a large database it may never complete at all.
Parallel: turn on the Parallel Processing toggle. The change is split across multiple background sessions and multiple transactions. Microsoft recommends it for large databases or companies with numerous posted entries. In this mode the update will not start if more than one database session is active , so every other user must be signed out.
In the Global Dimension 1 Code and/or Global Dimension 2 Code fields, enter the new replacement dimension codes. The current codes appear greyed out behind the fields.
Run the action that belongs to the chosen mode. This is the step candidates most often reverse:
Sequential mode → choose Start directly. There is no Prepare step in sequential mode.
Parallel mode → choose Prepare first. Prepare fills the Log Entries tab with the tables and record counts to be changed. Then sign out of Business Central, sign back in, and choose Start to begin the parallel processing. Change Global Dimensions Execution Flow:
- Change Global Dimensions Page
- │
├── 1. Choose the run mode FIRST:
- │ ├── Sequential (DEFAULT) ── one transaction, current session,
- │ │ locks tables, few posted entries only
- │ └── Parallel ───────────── Parallel Processing toggle ON,
- │ multiple background sessions,
- │ refuses to start with >1 active session
- │
- ├── 2. Enter the new Global Dimension 1 / Global Dimension 2 codes
- │
├── 3. Run the action for that mode:
- │ ├── Sequential ──► Start (NO Prepare step exists)
- │ └── Parallel ────► Prepare ──► sign out / sign in ──► Start
- │
└── 4. Change Global Dimensions Log Monitor:
- ├── Table 17 G/L Entry ------------ [Completed]
- ├── Table 21 Cust. Ledger Entry --- [In Progress]
- ├── Table 32 Item Ledger Entry ---- [Scheduled]
- └── Action: Rerun Incomplete (Resumes if deadlock occurs)
- 4. Table Locking, Integrity Safeguards & Monitoring Logs
Executing a Global Dimension change is one of the most resource-intensive operations in Dynamics 365 Business Central. Functional consultants must observe strict operational protocols:
Table Locking & User Concurrency Rules
Mandatory Maintenance Window: The process applies exclusive schema and table update locks on Table 17 G/L Entry , Table 32 Item Ledger Entry , Table 37 Sales Line , and related tables. All business users must log out of the company.
Any user attempting to post an invoice or edit a sales order while the routine is executing will trigger SQL deadlock errors or cause the reclassification job to abort.
Monitoring the Change Global Dimensions Log
The Change Global Dimensions Log ( Page 484 ) provides real-time visibility into the reclassification progress:
- Table ID and Table Name
- Total Records to update
- Records Completed
- Status : Scheduled , In Progress , Completed , or Incomplete
- Duration
- Error Recovery & The "Rerun Incomplete" Action
If a background task is interrupted—due to an Azure SQL transient connection dropout, an exceeding of CPU thresholds, or a lingering lock—the affected table is marked as Incomplete or Error .
Business Central preserves all completed tables and committed rows.
Once the conflict is resolved, the administrator navigates back to the Change Global Dimensions page and chooses Rerun Incomplete .
The system restarts processing strictly for the unfinished tables from their last committed checkpoint without rolling back previously updated tables.
5. Common Implementation Pitfalls & Exam Traps
Pitfall 1: Expecting Shortcut Dimensions 3–8 as Chart of Accounts FlowFilters. Consultants often assign a dimension to Shortcut Dimension 3 and expect it to appear as a native FlowFilter on the G/L Account card. Only Global Dimensions 1 and 2 provide native G/L Account FlowFilters. To filter G/L balances by Shortcut Dimensions 3–8, consultants must build a Financial Report or an Analysis View .
Pitfall 2: Choosing the Mode by Habit Instead of by Data Volume. Sequential is the default , and Microsoft recommends it for companies with relatively few posted entries because it completes fastest. On a database with hundreds of thousands of ledger entries it may not complete at all, which is why large companies must switch to Parallel . The mistake works in both directions: reaching for Parallel on a small sandbox needlessly forces every other session off the environment.
Pitfall 3: Assuming Prepare Is Always Required. Prepare belongs to Parallel mode only. In Sequential mode — which is the default — you select the new dimension codes and choose Start ; there is no Prepare action to run first. In Parallel mode the opposite mistake bites: skipping Prepare (and the sign-out/sign-in that follows it) leaves Start with no prepared log entries to process.
Pitfall 4: Believing Shortcut Dimensions 3–8 Can Be Swapped for Free. This is stale advice carried over from older NAV/BC builds. Current Business Central documentation states that changing a global or shortcut dimension requires every entry posted with that dimension to be updated. The two changes simply use different actions: Global Dimensions 1 and 2 use Change Global Dimensions , while Shortcut Dimensions 3 through 8 use the separate Change Dimensions action. Neither is a free metadata flip, which is why Microsoft's guidance is to choose all ten dimensions carefully up front.