The table definition is invalid and cannot be validated - NAV 2015

poppins
poppins Member Posts: 647
in NAV Three Tier
I am receiving this message after importing a fob and compiling.
I used to solve this in 2013 R2 via the property prevent data loss.
How to do it for NAV 2015?

Answers

  • Adun
    Adun Member Posts: 19
    Have you tried selecting "Force" sync method? Please note that by doing so you can have your data erased (for example if a field was deleted in the fob)
  • poppins
    poppins Member Posts: 647
    Adun wrote: »
    Have you tried selecting "Force" sync method? Please note that by doing so you can have your data erased (for example if a field was deleted in the fob)

    yes but it did not work ...
  • Adun
    Adun Member Posts: 19
    From what I remember this error can occur if the object contain characters which cannot be recognized by the server (e.c. locale is different), or simply corrupted characters. Can this be the case?
  • poppins
    poppins Member Posts: 647
    Adun wrote: »
    From what I remember this error can occur if the object contain characters which cannot be recognized by the server (e.c. locale is different), or simply corrupted characters. Can this be the case?

    Yes, I think the localization is different.
    What to do in this case?
  • Adun
    Adun Member Posts: 19
    Well the only solution I know is to change system locale in Windows Region and Language setup (see a screenshot attached). I deal with Russian localization, so I have to change this into Russian locale. However, if you have multiple "specific" regions within NAV I don't think you can use this piecefully, because something else can break (just an assumption).
    1.png 50.5K
  • Kowa
    Kowa Member Posts: 926
    edited 2016-03-18
    If you have conflicting codepages within one installation:
    https://msdn.microsoft.com/en-us/library/dn479852(v=nav.90).aspx

    Apart from that, try to use PowerShell for the sync first to see if the error comes up there too.
    https://msdn.microsoft.com/en-us/library/dn466418(v=nav.90).aspx
    Sync-NavTenant <serverinstance> –Mode ForceSync.
    Kai Kowalewski
  • CristinaC
    CristinaC Member Posts: 1
    I had this issue with a Romanian database. For me force sync didn't help at all. The solution was to correct the incorrect letters from captions and messages and then I was able to compile just with validation.

Categories