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
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