Skip to main content

NAV 2013 R2 - The Object table contains a Microsoft Dynamics NAV Development Environment field data type that is not compatible with the SQL Server data type.

Hi all,

Let's discuss a issue resolution which most of us are facing after applying Rollup 5 for NAV 2013 R2 with Build  36281.

The Error Message that i faced is -

The Object table contains a Microsoft Dynamics NAV Development Environment field data type that is not compatible with the SQL Server data type.
Field : Version List
Type: Text 248
SQL type : VARCHAR(80)




Reason for Error Message (My Understanding) -

You tried to Open the Database created with a build earlier than 36281 in Build 32681 and didn't upgraded.

You clicked cancel when system asked to upgrade the database.

Here is what i Meant -

1. I have a database with old Build (say 35473) as shown below.



2. By Mistake i tried to open the database with Build 36281 and clicked cancel as shown below.



3. when i tired to open database again with old build (say 35473) it gives me error as shown below.


Resolution -

You need to upgrade the database to Build 36281 or Higher.

I hope you will be able to resolve the issue with the suggestion above.

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

Regards,
Saurav Dhyani
saurav-nav.blogspot.com

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.