{"id":27599,"date":"2023-10-27T12:48:03","date_gmt":"2023-10-27T12:48:03","guid":{"rendered":"https:\/\/www.greytrix.com\/blogs\/sagex3\/?p=27599"},"modified":"2023-10-27T12:48:06","modified_gmt":"2023-10-27T12:48:06","slug":"texts-to-translate-function-use-in-sage-x3","status":"publish","type":"post","link":"https:\/\/www.greytrix.com\/blogs\/sagex3\/2023\/10\/27\/texts-to-translate-function-use-in-sage-x3\/","title":{"rendered":"Texts to Translate function use in Sage X3"},"content":{"rendered":"\n

We frequently work with multilingual Sage X3<\/a> clients that prefer to utilize the program in their native languages. Many times during patching we often lose the translations for objects and to manually update them is a hassle.<\/p>\n\n\n\n

To know all the untranslated texts Sage X3 has a Translation module in the Navigation page that offers several tools among which today we\u2019ll show how to make use of the Texts to Translate function.<\/p>\n\n\n\n

To do the translation process, follow the steps below:<\/p>\n\n\n\n

Generation of cross reference: All > Translations > Software > Tools > Generation of cross-reference (AGENREFTXT)
Texts to Translate: All > Translations > Software > Functions > Texts to Translate (ATXTTRAD)<\/p>\n\n\n\n

New Stuff:<\/strong> Validation on Quantity field of the Purchase Invoice screen<\/a><\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 1: Generation of cross ref. & Texts to translate<\/center><\/font>\n\n\n\n

Refer the screenshots for reference:<\/p>\n\n\n\n

-First navigate to Generation of cross reference screen from the above path. This tool is used to generate a Temporary where-used table which has all the links of the text codes from ATEXTE table to the objects within Sage X3. Click on Yes button to begin the table generation as shown in Fig. 2.<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 2 – Prompt for generation<\/center><\/font>\n\n\n\n

-Once the table is generated a log page shows how many objects are added as shown in Fig. 3. Then head to Texts to translate screen and fill in the data as per your translated language and click Search as shown in Fig. 4.<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 3 – Log generation of Cross ref. table<\/center><\/font>\n\n\n\n
\"Fig.<\/a><\/center>\n
Fig. 4 – Texts to translate screen important components\n<\/center><\/font>\n\n\n\n

-Once the search is completed we\u2019ll see all our untranslated texts below in the table and for each record 2 lines will be present. The 1st line is for Reference language and 2nd for Translation language, for untranslated data the line will show \u201c?\u201d and we can edit out and click on save as shown in Fig. 5.<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 5 – Setting text for Translated language<\/center><\/font>\n\n\n\n

-When the changes are done on closing the screen a log will be generated showing all the changes made along with the validation as shown in Fig. 6. Log out the application and log in back with the translated language selected then we can see all our objects are updated with the texts.<\/p>\n\n\n\n

\"Fig.<\/a><\/center>\n
Fig. 6 – Successful validation log<\/center><\/font>\n\n\n\n

This way we can make use of the Texts to translation function in Sage X3 to update all our untranslated data without having to worry about validations.<\/p>\n","protected":false},"excerpt":{"rendered":"

We frequently work with multilingual Sage X3 clients that prefer to utilize the program in their native languages. Many times during patching we often lose the translations for objects and to manually update them is a hassle. To know all the untranslated texts Sage X3 has a Translation module in the Navigation page that offers\u2026 Read More »<\/a><\/span><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8,13],"tags":[3880,3265,3878,3881,2292,3879],"class_list":["post-27599","post","type-post","status-publish","format-standard","hentry","category-sage-erp-x3","category-integration","tag-language","tag-sagex3","tag-text","tag-text-to-translate","tag-translation","tag-untranslated"],"_links":{"self":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/27599","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/comments?post=27599"}],"version-history":[{"count":11,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/27599\/revisions"}],"predecessor-version":[{"id":27679,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/posts\/27599\/revisions\/27679"}],"wp:attachment":[{"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/media?parent=27599"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/categories?post=27599"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.greytrix.com\/blogs\/sagex3\/wp-json\/wp\/v2\/tags?post=27599"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}