Close this search box.

Dynamics NAV Dimension Errors – Part 1 of 2

This post is part of the Understanding Dimensions blog series.

One of the most common issues our clients run into is this error (or a variation of it) while posting transactions.

Dynamics NAV Dimension Error
Dynamics NAV Dimension Error

This error (with numerous variations) means that the transaction you are doing does not comply with the Dimension rules setup in your instance of NAV. There can be a few different causes and therefore different solutions, but there is a common way to interpret the message and find the correct fix.

What are Dimensions?

Firstly it is important to understand the usage of Dimensions. These are user defined reporting categories that drive NAV reporting. A common example may be for a NAV user to create a Dimension called “Product Group” to allow for reporting based on how the Items they sell are classified. The user then defines Dimension Values for the Dimension. In the Product Group example these may be Chairs, Desks, Cupboards etc. It is important to note that in NAV you may define as many Dimensions as you need, and each one can have as many Dimension Values as required.

Dimension Controls

Once Dimensions and their Values are defined, you need to ensure that they are used correctly on transactions so that all your reports are accurate & reconcilable to the total figures. NAV has three kinds of Dimension Controls

  • Code Mandatory: This means a Dimension Value for the given Dimension must be present, and it doesn’t matter which one.
  • Same Code: A specific Dimension Vale for the given Dimension must be used
  • No Code: You are not allowed to specify a Dimension Value for the given Dimension.

There are also various places Dimension controls may be set. The most common areas that may be have controls are

  • G/L Account: You may set up that you cannot post to one or more accounts without a particular dimension. A common example here may be that you make a “Product Group” dimension mandatory on your Sales account to ensure you can always report Sales by Product Group
  • Customer: If you have a dimension that is customer based (e.g. Customer Group) you may set that a particular Customer must always have a particular value (e.g. Supermarket). Therefore any transaction you post for that Customer must have Customer Group of Supermarket.
  • Item: In the Product Group example you may specify that a given Item must always use a particular Dimension & Value (e.g. an Item must always be tagged with Product Group of Chair)

Stay tuned for my next blog where we continue the discussion on the Dimensions.