Skip to main content

Adding Default / Mandatory Dimensions in Dynamics NAV / Business Central

Introduction:
In this blog I aim to provide how to set Mandatory Dimensions on Items,Customers, Vendors and G/L Accounts and how to optimize this process using Configuration package.


Pre-requisites:
Microsoft Dynamics NAV.
Microsoft Dynamics Business Central.
Understanding of Dimensions in NAV / BC

Theory:
Automatic Dimensions can be added for the G/L Accounts, Customers, Vendor and Items.
The Value Posting can be selected as per the below Table.

Value PostingExplanation
BlankNo posting restriction.Transactions can be posted with any dimension value or without a dimension value.
Code MandatoryAny dimension value for the given dimension can be added. If dimension value is blank then NAV / BC will throw an error
Same CodeOnly a single dimension value defined in Default Dimension can be used while posting.
No Code
Dimensions must not be specified on the transactions.
This also implies that you can add the Default Dimension, No Dimension, Mandatory Dimension and Manual Dimension only when needed using the Default Dimension functionality.

Solution:
1. Apply Mandatory Dimension on Items:
Goto Items > Select the Item and Open Card Page > Click on Dimensions Action.

In the Default Dimension Table, Table No. for Items Table is 27 which is automatically selected.
The value posting is also selected in the table based upon what option is selected.


2. Apply Mandatory Dimension on Customers:
Goto Customers > Select Customer and Open Card Page > Click on Dimensions Action


In the Default Dimension Table, Table No. for Customer Table is 18 which is automatically selected. The value posting is also selected in the table based upon what option is selected.


3. Apply Mandatory Dimension on Vendors:
Goto Vendors > Select Vendor and Open Card Page > Click on Dimensions Action

In the Default Dimension Table, Table No. for Vendor Table is 23 which is automatically selected. The value posting is also selected in the table based upon what option is selected.


4. Apply Mandatory Dimension on G/L Accounts:
Goto Chart of Accounts > Select the G/L Account and Open the Card Page > Click on  Dimensions Action.

In the Default Dimension Table, Table No. for Chart of Accounts Table is 15 which is automatically selected. The value posting is also selected in the table based upon what option is selected.


NOTE: You can give multiple Mandatory Dimensions as well

5. Using Configuration Package:
In Configuration Package, add the Table 352 Default Dimension and Export the Excel.
You can add the dimensions referring to the points 1-4 and insert you data in the Excel.

Import the Excel Package and Apply Data.

Conclusion:
Applying manually for each Master Record can be tedious and time consuming. In this blog I tried to add few sample records so that we can take help of this samples to create our conditions and insert data into Excel and apply it on all the Master Records.

Comments

Popular posts from this blog

TIP: Working with changing Field DataTypes and Deleting fields in Business Central

Introduction:
Imagine a scenario where as per the requirements provided by your clients, you have set up the Database structure in NAV/Business Central.
Then comes a requirement in Phase 2 which completely redefines the database structure which was provided by you and you need to delete a few fields in a table and move it to another table.

Pre-requisites:
Microsoft Dynamics NAV
Microsoft Dynamics Business Central

Books & References:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-obsoletestate-property

Solution:
1. In Microsoft Dynamics NAV, there was a flexibility to delete fields, tables, and keys and using  Force-Sync, you can directly delete the field, table, and keys from SQL Database.


2. Whereas in Microsoft Dynamics Business Central, you cannot delete the fields, keys, and tables.
In order to deploy this deleted change, you need to mention this field, table, and keys with Obsolete State Removed.


After you mention the field as…

How to actually use Profile Objects in Business Central

To 'Whomsoever This May Concern',
When I was working on a Production Deployment for one of my clients, I noticed that I could not create a Profile in Business Central Production Tenant. I was able to create new Profile in Sandbox.


Then I tried using configuration Package and modify the contents of 2000000178 Profile Table and as always configuration package blocked it.



There was no way of dealing with this other thancontacting Microsoft Support and this is the answer I get from a Support Engineer

I was on the verge to give my clients a link pointing to a specific page i.e https://businesscentral.dynamics.com/?page=50150

After being a little creative, I figured out that developing profile objects might help.

And this resolved this issue for me.




Permission Issues on Posting after deploying Extension in Business Central Production Tenant

Introduction:
Issues when you deploy your app in Business Central Production VS Business Central Sandbox. Let us what are the implications of the statement.
In my last blog () I have already pointed out the difference in Profile as to how can create new Profile in Business Central Sandbox but the same is not possible in Business Central Production.
Pre-requisite:
Microsoft Dynamics Business Central (SaaS)
Demonstration: 1. I was working with General Journals after deploying the App in Production Environment. Suddenly during posting I go this error.


2. To Verify this issue is not of Permission Set, I gave the User SUPER Permission and tried again.

I got the same error despite giving SUPER Permission. Again the same the error, so I checked the Effective Permissions.

I noticed that Table G/L Entry has an Indirect Permission. I replicated the same Production in Sandbox. But I didn’t find any issue like this.

3. Moreover, I noticed that when I uninstall the App, the Production works perfectly and …