Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 262 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 385 SQL Performance
- 33 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
NAV2018 - The table definition is invalid and cannot be validated
t_cracco
Member Posts: 32
Hi,
I'm in the middle of an upgrade from NAV2016 to NAV2018, base localisation is BE.
The company has a Polish subsidiary and so we have merged the Polish localisation into the NAV2018BE with own changes.
Now when I'm trying to import the PL language with txt or flm, I get the following error:
There is a topic already existing Mibuso, but not for NAV2018 and the "workaround solution" isn't available.
Anybody knows a solution?
Many thanks,
Tom
I'm in the middle of an upgrade from NAV2016 to NAV2018, base localisation is BE.
The company has a Polish subsidiary and so we have merged the Polish localisation into the NAV2018BE with own changes.
Now when I'm trying to import the PL language with txt or flm, I get the following error:
There is a topic already existing Mibuso, but not for NAV2018 and the "workaround solution" isn't available.
Anybody knows a solution?
Many thanks,
Tom
0
Best Answer
-
Options
panosk
Member Posts: 6
Ah the famous, Sales has sold "We can do all countries in one database" story to the customer
The problem with the Polish language is that is not using the same code pages as for instance Dutch, German, French etc. And the C/SIDE is not really Unicode capable.
To import the Polish language into the database, you will have to switch your "Non Unicode" code page to Polish.
This will allow you to import the language (flm), after importing the language you can switch back your "Non Unicode" code page to what it was before.
You will notice if you switch back that the Polish characters will be displayed wrong.
If you now want to compile a table you could get the "table definition is invalid" message again. This can be solved by using "Force".
I would advise that the Polish users login into a different RDP as your Belgium users.
It still will be a PITA
5
Answers
The problem with the Polish language is that is not using the same code pages as for instance Dutch, German, French etc. And the C/SIDE is not really Unicode capable.
To import the Polish language into the database, you will have to switch your "Non Unicode" code page to Polish.
This will allow you to import the language (flm), after importing the language you can switch back your "Non Unicode" code page to what it was before.
You will notice if you switch back that the Polish characters will be displayed wrong.
If you now want to compile a table you could get the "table definition is invalid" message again. This can be solved by using "Force".
I would advise that the Polish users login into a different RDP as your Belgium users.
It still will be a PITA
Import is now working. Thanks for the quick update.
Is there a reason why the Polish users need to login into a different RDP?
I know C/Side is indeed non Unicode, but to my knowledge RTC is? And none of the Polish users will login onto C/Side.