Can localised fields cause problems?

afarr

A client has some fields and tables from a local version of NAV 2009.
Our dev licence does not have that localization; we can renumber the tables to the 50000 range, but cannot renumber the fields, since we cannot delete the localized fields.

If we renumber the tables (not the fields), the client can use the database with a W1 client licence; they can also read and modify data in the localized fields.

On the other hand, we can modify the localized fields (rename, shorten, lengthen) with our dev licence, delete a table that contains a localized field, and import the table into NAV 2013. The only limitation that I can see is that we cannot delete the field from the table.

Could that cause problems, for example, during an upgrade?

postsaurav

Hey,

First thing First - You Should not Do It.
The Right way to do is to Procure the Correct License from Microsoft.

To Answer your Question-

A) Yes it may cause an issue, if the Logic behind that field changes in New Version, then Upgrade Toolkit will not take care of the data in your customized Table / Field.

What if the Microsoft Comes up with a New Localization Hotfix and the Field Logic have been changed?

afarr

Hi Saurav,

It's certainly best to use the appropriate licence, and we certainly tried, but unfortunately the Turkish localisation was discontinued in Nav 2013.

This is why the client started with Nav 2009 R2 instead, and is now moving the Turkish tables to the 50000 range.

Alastair

postsaurav

Hey Alastair,

Ok, If that is the case then as per my knowledge there should not be any issues during data migration.

Question 1 -

afarr wrote:

Our dev licence does not have that localization; we can renumber the tables to the 50000 range, but cannot renumber the fields, since we cannot delete the localized fields.

For Localization Fields in Standard Tables Created Fields in 50000 ID and change the name of standard fields. (like Local Field to Local Field 1)
Transfer Data From Standard Field to Customized fields for all companies.
Clear Data in Standard Fields from all companies.

Question2 -

afarr wrote:

On the other hand, we can modify the localized fields (rename, shorten, lengthen) with our dev licence, delete a table that contains a localized field, and import the table into NAV 2013. The only limitation that I can see is that we cannot delete the field from the table.

When you upgrade the database to NAV 2013 W1, it will not have Turkish Localization Fields and During Merging you cannot create Them. You can only create Customized Fields which you created.
They will be automatically deleted during Upgrade.

Question 3 -

afarr wrote:

Could that cause problems, for example, during an upgrade?

As Localization Fields will be Blank During Data Upgrade (Data Transferred From Localized Fields to Customized Fields in Question 1) it will not cause any issues.

---

Hope it clears your doubts. If you have any queries do ask me otherwise mark the issue as Solved / Closed.