Issue in Importing the Object in NAV 2013 - Upgrade Issue

SmitaDubai

Dear Everyone,

I need one urgent help for the following issue.

Currently I am doing one Data Upgradation for one customer.

I am following the steps as per the quick Guide which comes with the Product CD.

While importing the NAV 2013 Merging Objects after converting the Database, I am facing the following error for few tables.

"The XXXXX table contains a Microsoft Dynamics NAV Development Environment field data type that is not compatible with the SQL Server data type:

Field: Record ID
Type: RecordID448
SQL type: VARBINARY(224)"

I am using SQL Management Studio 2014. Compatibility, I have set to 120.

Please help me to import the object.


Regards,
Smita.

SmitaDubai

Another thing I noticed , For few tables , 'Text' & 'Code' Data types for fields have been changed as 'OemText' & 'OemCode' after Database Conversion in NAV 2013.

The above mentioned error message I am getting for these objects only where the data type has been changed. (While Importing/Replacing NAV 2013 objects ).

tinoruijs

Are you using the latest build for NAV 2013 or NAV 2013 R2?
I think it is best to start over again.

SmitaDubai

I am using NAV 2013 not NAV 2013 R2.

Anyone having any solution to this ?? ](*,)

Please help.

Everything till now is fine & i have already put so much of time. So starting all again is the last option.

tinoruijs

And you're on the latest build?
I understand starting over is the last solution. I know how it goes and how much time a conversion can cost.
Hope for you anyone else has got a better solution.

SmitaDubai

I am using the build - Build -33781 (NAV 2013).

Someone Please help.

postsaurav

Hey Smita,

Let me re-phrase what i understand -

1. You are upgrading the Database to NAV 2013.

Cause of Issue -

SQL Server Support Unicode way back but NAV before NAV 2013 does not support Unicode.

Before NAV 2013 navision used to use a datatype on SQL Server i.e VarChar. In NAV 2013 for Unicode Support it have been changed to nVarchar Datatype. When importing a FOB file in NAV 2013 during Upgrade process the Text and Code fields are converted to OemCode and OemText.

NAV 2013 converts Code and Text Datatypes to nVarchar in SQL but till NAV 2009 values coverts these datatypes to OemCode and OemText.

Resolution -
Export Objects to Text Format and Find and Replace OemCode and OemText with Code and Text.

For Details Refer the Nice Post here From Mark -
http://dynamicsuser.net/blogs/mark_brummel/archive/2012/11/14/nav-2013-unicode-oemcode-amp-oemtext.aspx

Let me know if you have any doubts.

postsaurav

Hey Smita,

If above steps resolve issue, please mark issue as resolved.

SmitaDubai

Thanks a lot Saurav for the detailed explanation & solution provided.

I tried doing changes in the text file & importing again, but the same error message again came up.

Surprisingly I am getting this issue only in 8 tables not for all the tables in the DB. Among which 7 are not having any Data. So what I did , i deleted some 7 tables, imported the merging objects of 2013.

And for the one which is having data, I transferred the data in SQL to to another customized table which is replica of the standard one. Then I deleted the data from the standard table & changed the data type from OemText to Text.

Thanks you so much. Your post helped me to understand why this Oemtext/Oemcode is coming .Earlier I didn't have any clue :roll:

postsaurav

Hey Smita,

Great to hear that issue is resolved. :thumbsup: =D>

Please mark the issue as resolved on the forum. You can do same from the right bottom of the page.