Due to table extensions & page extension in business central, now we can have 0 foot print in base application/ code, but is same achievable in NAV 2018 also?
Lets take a simple example, you have an add-on which has added few fields in base table (lets say currency table) and this field is added in currency page also in NAV 2017. You are upgrading to NAV 2018, I think you can create a new table for these new fields and when adding these fields on the page you will have to make some changes in the base currency page. Is there a way to do this without making any customization/ modification in base page?
I am talking about upgrading an add-on on NAV2017 to Business Central and thinking about taking the route:
NAV2017 >> NAV 2018 >> Business Central
A lot is being discussed in forums about 'Zero Footprint in base application' which is doable in Business Central, but can same be achieved in NAV2018 also?
Thanks in advance.
For a NAV 2018 you can develop an extension, the same way you would do for 365BC.
Then youcan publish it with PS.
As Alexander says then you can create an extension with NAV 2018, just as you can with Business Central.
In fact depending on what changes we talk about, then that is also possible in NAV 2017. You can create extensions in NAV 2017 too, just not with AL/VSCode and not as much as you can in NAV 2018/BC.
You could upgrade from NAV 2017 via NAV 2018 before BC. But why would you not go directly from NAV 2017 to BC?
When you upgrade the first time from NAV 2017 to BC (or NAV 2018), then you would keep any added fields in C/Side. Your extension install function will then be able to copy the data from the old fields to the extension fields. These old C/Side fields would then have to be removed with force in your next update, after you have ensured they are migrated to your extension.