Skip to main content

NAV 2013 & NAV 2013 R2 - Comman Issue Related to Dimension in Step 2.

Hi all,

This is one of the most Common error that most of us are facing while upgrading to NAV 2013 or NAV 2013 R2 From NAV 2009 / 2009 SP1 / 2009 R2.

What we had Completed?

A. We completed Step 1 Successfully.
B. Converted the Database to NAV 2013.
C. Converted the Database to NAV 2013 R2.
D. Imported the Merged Objects & Toolkit Step 2 Objects.

What we are Currently Doing?

A. Run the Upgrade Step 2.
B. Tested the Connection.
C. Clicked on Transfer Data.

What is the Error Message While Transferring Dimension?

Dimension Value ID must have a value in Dimension Set Entry: Dimension Set ID=0, Dimension Code=<Dimenion Code>. It cannot be zero or empty.



Why the Error Message?

After Trying to Find the Reason, i figured out that the error is due to a dimension Value that have been applied on a posted or UN-posted document, but due to certain Required Customization our Code had deleted the Dimension Value from Dimension Value Table.

Below is the Example to understand the issue -

1. I have a Posted Sales Invoice Which have Dimension Code is AREA and Dimension Value for AREA IS 30.


2. Our Code have deleted the Value 30 For Dimension AREA as Shown Below. (User cannot delete from here as there is a check which check usage of Dimension Value in Documents)



* As per Microsoft Standard we should not delete any dimension Value instead if don't want to use the same we can set the Blocked as True.

So Now we know what is the issue, in the Next post we will see how we resolve issue if -

A) We are about to begin the Upgrade.

B) We are in step 2 of Upgrade and Facing this issue.

Link To Next Post

Stay Tuned.

"These postings are provided "AS IS" with no warranties and confer no rights. You assume all risk for your use."

Regards,
Saurav Dhyani

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.