Skip to main content

Difference Between Global Dimension, Shortcut Dimension, and Dimension

People often get confused with this three different terminologies.
First of all keep aside different dimension terminology, just remember concept of Dimension.
So you know how to create dimension what is purpose of dimension & that all. So before shortcut dimension or global dimension, first it is normal dimension that we are defining on dimension page.
So all characteristics & usage of "Dimension" will be applicable for Global Dimension & Shortcut Dimension both.
We are defining Dimension as Global Dimension or Shortcut Dimension in General Ledger Setup.
Now lets see what is difference between them.

For more clarity see below screen captures.

Point 1:
I have defined two Global Dimensions "Department Code" & "Unit Code". Below Screen Shot is of Item ledger entry showing Global Dimension as a part of table fields.












Point 2:
Below Screen Shot is of Purchase Order showing Global Dimension & Shortcut Dimension in Purchase Line for data entry.













Point 3:
Below Screen Shot is of General Ledger Setup from which you can see defined Global Dimensions & Shortcut Dimension.
Also check that Global Dimensions are assigned as Shortcut Dimension 1 & 2 by default.










That's the funda of Dimension, Global Dimension, and Shortcut Dimension. Hope I am able to clear the idea a little bit, If you want to discuss it further, simply fire a mail to me with your questions (kapilpunvar@gmail.com).

Comments

Post a Comment

Popular posts from this blog

Subcontracting in BC 2026 Wave 1 — A Manufacturer's Guide to the New Native Framework

  Introduction Subcontracting has been one of the most common pain points I encounter in Business Central manufacturing implementations. The question I've heard dozens of times is some version of this: "We send components to a vendor for painting / galvanizing / heat treatment — how do we handle that in BC without building a workaround?" Until now, the honest answer was: with some creative configuration, a fair bit of discipline, and an acceptance that BC's native subcontracting capabilities only handled the cost side of the equation, not the physical movement of goods. It is worth noting that subcontracting logistics functionality has existed in BC but only within specific localizations, namely India and Italy. Manufacturers running those localizations have had access to logistics flows for subcontractor transfers as a regional capability. With 2026 Wave 1, Microsoft is promoting this to a W1 — worldwide — solution, meaning any BC customer on any localization c...

Manufacturing Costing — What Changed in recent versions (BC26 & 27) and Why It Matters

  Introduction Manufacturing costing has always been one of the most technically demanding areas of a Business Central implementation. Get it right and you have a reliable, real-time view of what it actually costs to make your products. Get it wrong and your P&L tells a story that doesn't match your shop floor. In 2025, Microsoft has made meaningful improvements to manufacturing costing across both Wave 1 and Wave 2 — which targeted fixes to gaps that practitioners like me have been navigating in our implementations. This post walks through what changed, what it means in practice, and what you should do about it. Quick reference — what's available and when All four features covered in this post are already generally available. Here's the version map so you know exactly what you need to be running: Feature Wave GA Date BC Version Non-inventory items in production cost Wave 1 20...

Phantom BOM in Business Central: Solving the "Kit Problem" for many Industries

  If you have ever sat in a discovery workshop with an industries like industrial pump manufacturer, you already know the moment I am talking about. The production head opens his BOM file in Excel. You scroll down. And down. And down some more. For example, a single end-suction centrifugal pump has 150+ components — bolts, nuts, washers, gaskets, O-rings, dowel pins, retaining rings, shims, nameplates, grease nipples, foundation hardware — and roughly half of those line items repeat across every pump variant the company builds. Then the planner says the line we have all heard a hundred times: "Sir, we always use these hardware items together. Why should I plan them one by one every time?" This is the classic kit problem in many industry. And in Microsoft Dynamics 365 Business Central, the cleanest way to solve it is a feature that is criminally under-used — the Phantom BOM . Why a Kit (Phantom) Structure Is Required Here Before jumping into BC setup, let me...