Designing dimensions in Business Central

Dimensions are the analytical lens of Business Central. Designed well, they let you run any management report from the GL without ever multiplying the chart of accounts. Designed badly, they turn into an unenforced mess that everyone reports around. The design is one of the most consequential decisions in an implementation.

Global vs shortcut. Business Central has up to eight global dimensions — every transaction can carry a value for each of them, and they're filterable everywhere. Of those, two are shortcut dimensions that appear as columns on every transactional document (sales order line, purchase invoice line, journal line), making them easy to set. The other six global dimensions are still attached to every transaction but require an extra click to set; pick the two that are most operationally relevant as the shortcuts.

Choosing dimensions. Start from the management reports you want. Common dimensions: Department / Cost Centre (the unit owning the spend), Project (for project-billable businesses), Customer Group or Region (for sales analysis), Salesperson (for commissions), Brand or Product Line (for marketing roll-ups). Don't reach for dimensions that simply replicate data already on the transaction — date, customer number, item number all flow naturally; reporting them needs no dimension.

Default values. Master records — customers, vendors, items, GL accounts, employees, locations — can default dimension values onto the transactions they appear on. Configure defaults so that the right values get set automatically; manual setting should be the exception.

Default rules. Mandatory rules force a dimension value to be present before posting (typical for Department). Same Code rules force a dimension to match another dimension's value (rare; typical use is two related dimensions that should never disagree). No Code rules block a dimension on certain accounts (e.g. balance sheet accounts shouldn't carry a Project dimension).

Dimension combinations. A separate matrix defines which combinations of dimension values are valid (e.g. Project X is only valid with Department A). Combinations are powerful but get heavy to maintain — use sparingly.

Renaming and deleting. Dimension values can be merged or renamed; once they've been used on posted transactions, they cannot be deleted. So plan the initial coding scheme to leave space (e.g. number gaps) for future expansion.

Don't reach eight. Companies that use all eight global dimensions are usually under-using their chart of accounts. Aim for four to six clean dimensions and a tidy CoA.