web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics NAV (Archived) / NAV2016 to NAV2018 (CU...
Microsoft Dynamics NAV (Archived)

NAV2016 to NAV2018 (CU3) data upgrade problems @ task 13

(0) ShareShare
ReportReport
Posted on by CanuckNav74

I'm currently upgrading the data for a client from NAV2016 CU3 to NAV2018 CU3 (C/AL customizations. not the modern development environment). The database is North America.

I'm using the guide here to upgrade the data (the client's objects have already merged and upgraded to NAV2018):

https://docs.microsoft.com/en-us/dynamics-nav/upgrading-the-data

I'm running into an error at step 13 (run the schema synchronization on the imported objects).

When I try to synchronize from finsql.exe, the Synchronize Schema Changes Window shows the following message:

State=OperationalWithSyncFailure

Detailed State:

Changes were found that may delete data from the relevant fields or tables. to get a list of errors, run the following windows powershell command: Sync-NavTenant [ServerInstance] -Mode CheckOnly

I run the command that NAV suggests, and I get this:

======================

Sync-NAVTenant : The schema synchronization may result in deleted data. The following destructive changes were detected:
Table: 4, Currency
Field: 10000, Symbol: Deleted
Table: 79, Company Information
Field: 10018, US Country/Region Code: Deleted
Field: 10019, Canada Country/Region Code: Deleted
Field: 10020, Mexico Country/Region Code: Deleted
Table: 81, Gen. Journal Line
Field: 10005, Check Exported: Deleted
Field: 10007, Check Transmitted: Deleted
Table: 311, Sales & Receivables Setup
Field: 10000, G/L Freight Account No.: Deleted
Examples of code to migrate data:
DataUpgradeMgt.SetTableSyncSetup(DATABASE::"Currency",[Upgrade Table Id],TableSynchSetup.Mode::[Mode]);
DataUpgradeMgt.SetTableSyncSetup(DATABASE::"Company Information",[Upgrade Table Id],TableSynchSetup.Mode::[Mode]);
DataUpgradeMgt.SetTableSyncSetup(DATABASE::"Gen. Journal Line",[Upgrade Table Id],TableSynchSetup.Mode::[Mode]);
DataUpgradeMgt.SetTableSyncSetup(DATABASE::"Sales & Receivables Setup",[Upgrade Table Id],TableSynchSetup.Mode::[Mode]);
At line:1 char:1
+ Sync-NAVTenant -ServerInstance RYCO_UPG -Mode CheckOnly
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (0:Int32) [Sync-NAVTenant], NavCommandException
    + FullyQualifiedErrorId : MicrosoftDynamicsNavServer$RYCO_UPG,Microsoft.Dynamics.Nav.Management.Cmdlets.SyncNavTenant

====================

If I perform a Sync-NAVTenant -Mode ForceSync, I can get past this step, but the next step, task 14, fails ("run the data upgrade process" - presumably because the force sync removes the old fields, thus breaking  the data upgrade process). The suggestions offered in the -Mode CheckOnly are cyptic and I don't understand what it wants me to do.

Has anyone encountered this before?

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    CanuckNav74 Profile Picture
    CanuckNav74 on at

    issue resolved.

    It's not covered in the published data upgrade guide, but in the case of the database I'm upgrading (country: Canada), there are localized upgrade toolkit .fobs on the install DVD in "Upgrade Toolkit >> Local Objects".

    Despite the file names in that folder e.g. Upgrade9001100.US.FOB, these are localized upgrade toolkit objects for North America.

    Why Microsoft named them .US is beyond me.

    Even more puzzling their complete absence in the official data upgrade documentation, despite their importance for North American upgrades to NAV2018!

    To resolve my issue, I needed to import the following .fobs in the following order (all with synchronize schema >> later):

    1) import the upgraded/merged .fob of ALL NAV2018 objects

    2) import Upgrade9001100.FOB

    3) import Upgrade9001100.US.FOB

    Once done, step 13 (schema synchronization with validation) ran without any issues and I was able to upgrade the database.

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Dear All,

    I am Working with Same Version i.e North America and Also getting same error which you mentioned above.

    I imported UpgardeToolkit of Local Objects  as (Upgrade7001100.US) fob

    I'm currently upgrading the data for a client from NAV2009R2  to NAV2018  (C/AL customizations. not the modern development environment). The database is North America. Now NAV NAV2009R2 to NAV2013 Upgraded successfully but when I am going to upgrade NAV2013 to NAV2018 then getting below error.

    I'm using the guide here to upgrade the data (the client's objects have already merged and upgraded to NAV2018):

    docs.microsoft.com/.../upgrading-the-data

    I'm running into an error at step 13 (run the schema synchronization on the imported objects).

    When I try to synchronize from finsql.exe, the Synchronize Schema Changes Window shows the following message:

    State=OperationalWithSyncFailure

    Detailed State:...

    Changes were found that may delete data from the relevant fields or tables. to get a list of errors, run the following windows powershell command: Sync-NavTenant [ServerInstance] -Mode CheckOnly

    I run the command that NAV suggests, and I get this:

    The schema synchronization may result in deleted data. The following destructive changes were detected:

    Table: 355, Ledger Entry Dimension

    Field: 1, Table ID: Data type changed

    Field: 2, Entry No.: Data type changed

    Field: 3, Dimension Code: Data type changed

    Field: 4, Dimension Value Code: Data type changed

    Table: 104055, Temp Post Code

    Field: 2, City: Data type changed

    Field: 1, Code: Removed from primary key - Data type changed

    Field: 10010, County: Deleted

    Table: 104073, Temp Cost Share Buffer

    Field: 1, Item Ledger Entry No.: Data type changed

    Field: 2, Capacity Ledger Entry No.: Deleted

    Field: 90, Order Type: Deleted

    Field: 91, Order No.: Deleted

    Field: 92, Order Line No.: Deleted

    Table: 104074, Temp Capacity Ledger Entry

    Field: 1, Entry No.: Data type changed

    Field: 90, Order Type: Deleted

    Field: 91, Order No.: Deleted

    Field: 92, Order Line No.: Deleted

    Table: 104080, Temp Invt. Adjmt. Entry (Ord)

    Field: 1, Order Type: Data type changed

    Field: 3, Order Line No.:

    ---------------------------

    OK  

    ---------------------------

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans