Extension from NAV2016 to NAV2017

AitorEG

Hello everyone
We have some modifications in NAV2016, that are quite interesting to pack them in extension for future applications.
My first question I think is quite obvious, but, can I create the extension in NAV2016, and publish it on NAV2017? Probably no I think...
If I need to create the extension on NAV2017, I have to import the objets from NAV2016 to NAV2017. Should I import all the application objects, or it's enough with the objects involved in the extension? Before importing, should I merge the versions?
I just need the objets, so I think I don't need to upgrade the database.
Thanks in advance

mohana_cse06

No, we can install extensions on base version where we developed.
yes, you need to merge NAV2016 modified objects to NAV2017.

mohana_cse06

yes. if you have developed on NAV2016 then you can install on NAV2016 etc.

daborg

Yes you actually can do this, and I have done this. What it really depends on is what your extension hooks into. the less base application you hook into the better the chance that you do not have to change your extension at all from 2016 to 2017. Even if you have touched some base objects as part of your extension, if those pieces remain the same in 2017, your extension will still work.

As a workshop, I had some developers create various extensions using NAV 2016, and I later re-used those same extensions (unchanged) in a NAV 2017 demo that I gave. The NAV 2017 database wasn't even an unmodified database!

As the extensions are built off of deltas, as long as the delta in question still applies to the base objects you changed, then the extension will still work on the newer platform.

This is the same premise that lets you install cumulative updates without necessarily having to change your extension.

mohana_cse06

No, we can install extensions on base version where we developed.
yes, you need to merge NAV2016 modified objects to NAV2017.

AitorEG

mohana_cse06 wrote: »

No, we can install extensions on base version where we developed.

With this you mean that I can just install the extension where they have been develpod, am I right?
Thanks

mohana_cse06

yes. if you have developed on NAV2016 then you can install on NAV2016 etc.

daborg

Yes you actually can do this, and I have done this. What it really depends on is what your extension hooks into. the less base application you hook into the better the chance that you do not have to change your extension at all from 2016 to 2017. Even if you have touched some base objects as part of your extension, if those pieces remain the same in 2017, your extension will still work.

As a workshop, I had some developers create various extensions using NAV 2016, and I later re-used those same extensions (unchanged) in a NAV 2017 demo that I gave. The NAV 2017 database wasn't even an unmodified database!

As the extensions are built off of deltas, as long as the delta in question still applies to the base objects you changed, then the extension will still work on the newer platform.

This is the same premise that lets you install cumulative updates without necessarily having to change your extension.

AitorEG

Thank you both for your help. So, definitely, I should upgrade the modified objects to NAV2017, and then, develop the extension in NAV2017.
Thank you very much!