Dimension Set Entry Not Update after Upgrade From NAV 2009 to NAV 2016

rachit

Hello Guys,

Please help me out to solve this situation.

I have upgraded NAV 2009 Database to NAV 2016 successfully without any major problems. I have followed all the steps given by microsoft from here :

https://blogs.msdn.microsoft.com/nav/2015/02/23/upgrading-from-microsoft-dynamics-nav-2009-r2-or-microsoft-dynamics-nav-2009-sp1-to-microsoft-dynamics-nav-2015/

Now after opening NAV 2016 Database I could not find any data related to Dimensions. In short during upgrade process Dimension Set entry is not created.

Can anybody help me here to troubleshoot this situation and suggest me a solution or workaround to create Dimension Set Entries in new version.

Any suggestions would highly helpful and appreciated.

Thanks
Rachit

davmac1

the upgrade runs the dimension updates using sql scripts. You should get an error if they fail. Do you have any customizations to the NAV 2015 upgrade programs?
Fixing this after the fact is dangerous - you should run the upgrade again and make sure you each step works before you continue with the next one.
The only shortcut I can think of is to run the dimension update by itself if you have not added any dimensions yet. But then you take the risk of having a bad dimension setup which will cause you continual problems.

davmac1

the upgrade runs the dimension updates using sql scripts. You should get an error if they fail. Do you have any customizations to the NAV 2015 upgrade programs?
Fixing this after the fact is dangerous - you should run the upgrade again and make sure you each step works before you continue with the next one.
The only shortcut I can think of is to run the dimension update by itself if you have not added any dimensions yet. But then you take the risk of having a bad dimension setup which will cause you continual problems.

rachit

Thanks @davmac1. You are correct that even if we follow workaround to create dimensions manually in the system, this might cause issues in future.

KWevick

We have the same problem, upgrading from NAV5.1 to NAV2016 using all the NAV tools. In testing, it was not discovered and now the Customer is live. This only impacted G/L Entries that were upgraded, as far as we can tell so far. All the other 'histories' appear to be correct, although we're still testing. We will have to do this by programming and "Forcing" the correct Dimension ID Set into each entry. Has anyone else tried this. Related records are correct.

malintus

@KWevick I have similar situation like you had. What did you do with this issue?