Upgrading from NAV2009 to NAV2016 - new fields in 2016 that are not in 2015

rsaritzky

Hi all,

I'm migrating a database from NAV2009 to NAV2016. As has been discussed in this forum many times, the steps are:

1. Technical Upgrade from NAV2009 to NAV2013
2. Data Upgrade from NAV2009 to NAV2015 using the upgrade objects provided (Upgrade601800.US.fob)
3. Upgrade from NAV2015 to NAV2016

During the Data Upgrade in Step 2 (going from 2009 to 2015), you are supposed to replace all the objects with 2015 objects. For the tables, I merged our custom fields into a 2015 database and brought the 2015 objects in and continued the Data upgrade, which completed successfully.

Now, I'm in step 3, which requires pretty much the same thing - replacing all the objects with 2016 objects. Again, for the tables, I merged our custom fields into a template 2016 database. So here's the issue (this is just one example - we have many standard nav tables that are customized.) One of them is the G/L Account Table.

BUT the G/L Account Table in NAV2016 has a new field - field 1700 "Default Deferral Template Code". So I have to merge our custom changes AND add this new standard field.

In my own database, which has 2015 objects, I cannot import object Text files with this field, because it does not exist (yet) - the error message you get (obvious) is "Your program license does not allow you to create the Default Deferral Template Code field in the G/L Account table."

So, my question is what to do about this? Since I cannot import a text file for this object Do I have to merge my custom changes to 2016 in a template database and compile them before I can move them to our converted database? So far, this is the only way I've been able to get the new 2016 customized object into our database.

Or am I missing something?

Thanks

Ron

rsaritzky

Hi Kamil,

I don't think your solution will work, because we also have some addons. Our addon license doesn't allow us to create fields in a table in the addon licensed range, so we can't import object text files. We've asked our partner to try and even with their addon license, it won't work.

Ron

ayhan06

Hi,

for you have to prepare a fob file to import without your customization. In the Import journal screen, you need to select merge existing<=new option, not replace option, then select later option for the sync. after you import this fob, you will be able to import txt file.

for example, in the Item table, there is field numbered 50.000.001 for addon 1. also you have another field numbered 50.000.0002 for addon 2. last you have 50.000 field in customer range.

first you have to create a new 2009 db , export item table from old db as fob, import it into fresh db. then clean Item table by deleting all code and special properties on fields. (to accomplish this, export Item table to txt file, clean all the codes, autoformatexpr, tablerelation properties ) Import it to the system back. then convert that db to nav 2013/2015 and 2016 one by one by opening with development environments. then export Item table as fob and import it your real database with merge existing<= new selection. now your db has all fields from all addons and custom developments. then you can import merged/upgraded txt file into your database.

I was able to accomplish this process successfully in the old versions (like 4,0, 5.0 etc). I think it will work in the new versions as well.

thanks.

note: to be able to Insert Microsoft fields, you have start with nav 2016 w1 ( or country version) and import your special fob file with my suggestion and then import your merged/upgraded txt file.

postsaurav

Hi,

I am not sure what is your approach for a merge but what i feel based on my experience is-

Merge 1 -
Three Object Only Database --
a) 2009 Base (Microsoft Objects 2009)
b) 2009 Custom (Microsoft Objects 2009 + Customer specific customization)
c) 2015 Base (Microsoft Objects 2015)

You compare A & B Using any tool and merge gaps to C.

Merge 2 (2009 TO 2016) -
Three Object Only Database --
a) 2009 Base (Microsoft Objects 2009)
b) 2009 Custom (Microsoft Objects 2009 + Customer specific customization)
c) 2016 Base (Microsoft Objects 2016)

You compare A & B Using any tool and merge gaps to C.

Then You will not have above issue.

** One more thing as 2015 is a intermediate steps, you can only merge Tables Fields (standard Tables) and New Table.

** Reason being - We just need to place data in 2015 so we only need three things -
> Changed property of standard fields.
> New Fields in standard Tables.
> New tables.
Other objects you can use as of Microsoft NAV 2015 base.

Let me know if any doubts or my understanding is wrong.

mohana_cse06

yes, you need to use a standard NAV2016 database and import the merged objects in that database and compile.
export All FOB and use that FOB file to import

kine

Do not forget that today it is much easier to solve this issue. Just import the standard object through FOB file, use Replace All, and set the Schema synchronization to "Later". After that import the txt file, and now you can sync the schema. in this way, it will not do anything with the structure after the FOB import and you are safe with the data... ;-)

rsaritzky

Hi Kamil,

I don't think your solution will work, because we also have some addons. Our addon license doesn't allow us to create fields in a table in the addon licensed range, so we can't import object text files. We've asked our partner to try and even with their addon license, it won't work.

Ron

mdPartnerNL

kine wrote: »

Do not forget that today it is much easier to solve this issue. Just import the standard object through FOB file, use Replace All, and set the Schema synchronization to "Later". After that import the txt file, and now you can sync the schema. in this way, it will not do anything with the structure after the FOB import and you are safe with the data... ;-)

Interesting but still difficult for me to see this in action. How would his steps then be with the 2016 new field "Default Deferral Template Code"?

jglathe

Hi there,

mdPartnerNL wrote: »

Interesting but still difficult for me to see this in action. How would his steps then be with the 2016 new field "Default Deferral Template Code"?

There are some possibilities here. As long as your developer license has all the ISV insert rights you need, you can:

- import the standard .fob for the table, with "Replace", "Sync Later"
- import the "final" merged object as .txt.
- do the schema synchronization.

That's more or less the "I am Microsoft" case, you normally don't have ISV insert rights for AddOns you sell to (or find at) a customer. If you're not Microsoft, it won't work, you can't create the ISV AddOn fields again. What you would need is a "clean" .fob of the table of the target version with merged AddOn(s) of the target version. Or not so clean (no code), but the fields should be all there. There are scenarios, though, where you don't have all AddOns on the target NAV version. In this case you can only disable the old fields. They're still there, but can't contain data.

with best regards

Jens

mdPartnerNL

thx for the info

rsaritzky

Jens - you mentioned exactly what my problem is when you say "As long as your developer license has all the ISV insert rights you need, you can..."

Our license doesn't allow the ISV insert. That's the problem all along.

I know that Microsoft has this issue "under discussion". Hope they come up with something better.

Thx

Ron

kine

Than you need to contact the ISV and request the FOB file with their objects on the actual build you need. If they are not able to update the solution to newer versions, than it is not good vendor for you.

jglathe

Hi Kine,

true, but what about combinations of AddOns? In this case it's not quite as easy, you probably need to revert to washed objects. But you will probably be able to generate a clean custom object with all the desired fields and none of the old ones. Still some work, though

with best regards

Jens

ayhan06

Hi,

for you have to prepare a fob file to import without your customization. In the Import journal screen, you need to select merge existing<=new option, not replace option, then select later option for the sync. after you import this fob, you will be able to import txt file.

for example, in the Item table, there is field numbered 50.000.001 for addon 1. also you have another field numbered 50.000.0002 for addon 2. last you have 50.000 field in customer range.

first you have to create a new 2009 db , export item table from old db as fob, import it into fresh db. then clean Item table by deleting all code and special properties on fields. (to accomplish this, export Item table to txt file, clean all the codes, autoformatexpr, tablerelation properties ) Import it to the system back. then convert that db to nav 2013/2015 and 2016 one by one by opening with development environments. then export Item table as fob and import it your real database with merge existing<= new selection. now your db has all fields from all addons and custom developments. then you can import merged/upgraded txt file into your database.

I was able to accomplish this process successfully in the old versions (like 4,0, 5.0 etc). I think it will work in the new versions as well.

thanks.

note: to be able to Insert Microsoft fields, you have start with nav 2016 w1 ( or country version) and import your special fob file with my suggestion and then import your merged/upgraded txt file.

rsaritzky

Thanks again for keeping this thread discussion alive. I believe the latest version of Developer licenses (perhaps only for partners) will allow you to add fields in the 1-50000 range. This will help solve my original problem.

Ron

kine

Yes, with latest dev license you can create fields in Microsoft range. Thanks Microsoft, this save me hours of my live!