x Want to participate? Join the group to interact
  • State Verified Answer
  • Replies 1 reply
  • Subscribers 137 subscribers
  • Views 1576 views
  • Users 0 members are here
Browse Forums
Announcements
236
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
210
topics
416
replies
Sage Intelligence Reporting
121
topics
322
replies
Ricardo Castaneda Gonzalez

Import Products Transalation

SOLVED
Posted By

Hello,

I am pretty new into X3. I am wondering how can I import translations.

After reading several articles, I have no doubts that ATEXTRA table holds the translations. However when I get into the table, I cannot see any translation. I read about the importance about several flags in this table, but I have not seen any information they hold.

Also, I have been able to identify how easy is to introduce new translation in the function ATXTTRAD (Texts to translate). The client I have has thousands of products in different languages, I should not register item to item the translations. I tried to create an import template to make translations possible. I could not make it, but I am sure it should be a way to import translation.

Anyone can help me, please.

Thanks!

  • +1
    verified answer

    Hi Ricardo,

    ATEXTRA is the table to use to import product description in different languages. This table is used to store many translations for many fields. So the fields IDENT1 and IDENT2 are the key to identify the record linked to the translation. In the case of a product, you just need IDENT1 because the key is a unique field (ITMREF).
    The CODFIC identifies the table that hold the translated record: ITMMASTER in your case
    The LANGUE field is used to indicated in which language the text is translated.
    And ZONE is the field that stores the translation: DES1AXX for 1 description, DES2AXX for the 2nd description, etc.

    Here is an example of the import to build:

    Please be sure to test properly the import before using it on a Live environment.

    Note: You might need to create a new language code in the function GESTLA just for translation purpose. For instance a customer of mine needed to have the latin name of the plant he was using. So we created the Latin language before importing the latin translation.

*Community Hub is the new name for Sage City