What dimension issues have people dealt with when upgrading?

daborg · 2014-07-04

I am curious as to what various dimension issues people have encountered when upgrading from 2009 to 2013 (or R2...doesn't matter). We have a particularly difficult upgrade right now that has millions of dimension entries and it's hitting a wall now as the dimension portion of the upgrade seems to be endless. The first attempt at the upgrade was running for 5 days before we stopped it. We've identified some bad data but I'm curious what else may be out there that might be toying with the upgrade.

Thanks.

geordie · 2014-07-05

The common dimension issues I experienced and read about are related to value inconsistency between document/ledger tables and Posted Document Dimension/Ledger Entry Dimension that require to be fixed to avoid errors.

For performance improvement in upgrade (or migrate?

) Gunnar wrote two useful posts with some suggestions: first part and second part.

Some additional considerations:
- Running the upgrade process on the server directly increase the speed.
- Since the dimension upgrade use SQL statement, you can use monitor it to see if it's stuck on certain query.

thegunzo · 2014-07-07

I have also seen problems where the dimension value used has been deleted from the dimension value table.

I suggest that you also take a look at http://www.dynamics.is/?p=1751 where you should find methods to test the dimension before the upgrade.

postsaurav · 2014-07-07

Hey,

Here is what i guess can be useful.

The Problem =
http://saurav-nav.blogspot.in/2014/05/nav-2013-nav-2013-r2-conman-issue.html

and The Resolution =
http://saurav-nav.blogspot.in/2014/05/nav-2013-nav-2013-r2-comman-issue.html

Let me know if any issues.

What dimension issues have people dealt with when upgrading?

Comments

Categories