If you are just starting out with dimensions, or have created a new dimension, you may need to assign this to multiple Customer, Vendors, Items or GL Codes very quickly. To do this you can use the “Dimensions – Multiple” function.
In this example I have a dimension called “Department” that I want to assign as “Mandatory” to all my expense GL codes.
To do this I’ll go to “Chart of Accounts”, select all the GL expense codes, and then click “Related > Account > Dimensions > Dimensions – Multiple”
Then I’ll select that I want “Department” to be mandatory for these GL codes and click OK
Finally, I’ll check a GL code to confirm this has worked as expected:
Perfect, everything has worked as expected!
You can do this to customers, vendors and items via the relevant list page.
I came across an interesting situation today that I thought was worth documenting to see if there’s any known reason for this behaviour or if I’ve misunderstood something.
I’m unsure if this is a software issue, or by design, however I noticed that even though I’d set the dimension value posting to “No Code” on a GL code, a value was still posting for the dimension in a certain scenario.
The scenario is outlined below but in short the G/L entries affected were exchange gain and loss postings that were automatically created after applying a foreign currency invoice to a foreign currency payment.
The G/L account in question is the exchange gains\losses account. As you see I’ve specified this shouldn’t have any analysis to the “CUSTOMERGROUP” dimension code.
I then posted an Invoice and Payment at different exchange rates and analysed both to the Dimension Code “CUSTOMERGROUP”. (I used different value codes for each transaction as part of the test)
Then I applied the payment to the invoice to force an exchange gain\loss postings as per below.
When posting the application I expected an error however to my surprise this worked, and when I check the G/L entries the GL code 31900 has dimension code analysis posted to “CUSTOMERGROUP”. (its taken from the Payment as I used the dimension value code “MEDIUM” on the payment)
To confirm I’d set this up correctly I tried posting a standard journal to the GL code and I correctly received the error below:
While I appreciate its unlikely the system would ever be setup like this its interesting that the rule of “No Code” appears to have been bypassed in this particular scenario.
It would be interesting to know if there’s any reason for this?
I encountered this issue while investigating a dimension error a user received when applying an Invoice to a Credit note in Dynamics 365 Business Central.
In this case the user had just started assigning dimensions to customers however some customers had posted documents without any dimension analysis. They found when they attempted to apply documents with no dimension analysis they now received the error “Select Dimension Value Code for Dimension Code”.
To illustrate the issue below are some customer ledger entries for customer C00070 that have no dimension analysis (as this wasn’t required when the documents were posted)
We will now configure a requirement for analysis to the dimension “DEPARTMENT” on the customer:
Now when you attempt to post the application of the invoice to the credit note you are presented with the error below:
The only solution I could find other than reversing both the invoice and the credit was to temporarily remove the “Code Mandatory” for the dimension on the customer.
I guess as the system may have to post GL entries as a result of the application it therefore checks for the existence of dimensions on the source documents.
Something to watch out for when adding new dimensions onto existing customers and suppliers.