Conflicting Dimensions in Microsoft Dynamics NAV
In Microsoft Dynamics NAV you are able to specify or prevent a dimension on any master record. Examples of master records include the Item card, G/L Account, Customer Card, and Vendor Card. Occasionally the Dimensions specified on 2 different master records may conflict. Read on to learn how to resolve should you run into this issue.
Microsoft Dynamics NAV allows you to specify or prevent a dimension on any master record. Examples of master records include the Item Card, G/L Account, Customer Card, and Vendor Card.
Occasionally the Dimensions specified on 2 different master records may conflict.
The example below shows the Customer Card and the Bank Card. The ‘Area’ dimension is mandatory on the Customer Card and prevented on the Bank Account Card:
Figure 1 – Customer Card, Area Dimension
Figure 2 – Bank Card, Area Dimension
If you try to combine the above 2 master records on the same line on a journal (a cash receipts journal in this example) you will get a conflict error. See example below:
Figure 3 - Error Code on Dimension Code in Master Record
To get around this issue, two separate journal lines need to be created for the journal to post successfully.
Figure 4 - Creating Separate Journal Entries
Avoiding conflicting dimensions doesn’t have to be difficult, it just takes a little forethought. Always include separate journal lines for each entry and your journal will post correctly.
For more information on this or any other Dynamics NAV topic, please contact ArcherPoint.
For more step-by-step instructions on how to perform specific tasks in Microsoft Dynamics NAV, see our collection of How-To blogs.
- Login Error: Communication protocol mismatch between client and server
- Creating a Date Table in Power BI
- The Top Eight KPIs Retailers Should Be Tracking (with Formulas) for Your Retail KPI Dashboard
- Difference Between IaaS, PaaS, and SaaS And When You Need to Use Them
- The Microsoft Technology Stack – What It Is and Why You Should Care