Object Compatibility between different builds

gerdhuebner

Is there any information about the compatibility of the NAV objects (fob) between the different builds in NAV 2013 and/or NAV 2013 R2?
At the moment there are 3 main rollups available for NAV 2013 R2:
Rollup 1 - Build 35701
Rollup 2 - Build 35800
Rollup 3 - Build 36035
With RTC-Rollup 3 installed, it is not possible anymore to connect to a server, which runs on a build lower than 36035.
But what about object downward compatibility?
Is it possible, e. g., to import an object from a higher build (36035, e. g.) - database into a lower build (35701, e. g.) - database without problems?
Do we have to install a separate program version for each build in a development environment?
Some informations indicate that somewhere between build 35473 and 35800 a change in fob format has occured (http://www.mibuso.com/forum/viewtopic.php?f=32&t=60163). May be there are further changes...

mdPartnerNL

Like to know too.

This problem with objects not able to import is really annoying between major versions. With a little extra effort an update could be made... I think..

thegunzo

Hi

You should always be able to export an object to a text format and import with an older build.

mdPartnerNL

Correct, but sometimes the older database is missing some new fields created by ms. With the SEPA update I had this problem. And then you have a problem because NAV only created new fields with a fob.

davmac1

I was able to export objects from rollup 3 NAV 2013R2 to a system without rollups without a problem from the same copy of a customer database. (I had avised them to update to rollup 3 to fix an executable bug that rollup 3 fixed, but they have not done that yet.

gerdhuebner

I have imported the objects from Rollup 3 into a (technical) Build 35701 database environment (Rollup 1), recompiled the new objects and found only one error in Table Attachment, which was due to some new functions of the (new) outlook integration addin (Dotnet variable). So far no further problems occured.