Ir al contenido principal

How to perform text translation to add a different text language translation to a field.

Origen: https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=67803&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=19899&cmd=displayKC&dialogID=819187&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true
Products
Sage X3

Description
On-line text translation.
How to perform text translation to add a different text language translation to a field.


Resolution
Only the tables listed in the table selection on the Text translation screen are available for on-line translation. There are two ways to update text translation. One is on the fly, the other is across an entire table. 
On any description field that has and action button option of On line translation you can update a translation on the fly.
  1. Navigate to a field that you want to translate (such as Common data, Products, Products, description field).
  2. Click the action button and select On Line Translations.
  3. In a new row select the language you want to translate to.
  4. Enter the the translated text you want to see.
  5. Click Ok.
  6. Now when you click On Line Translation for that field and item you will see your translation.
You can update multiple table items at once from text translation.
  1. Navigate to Setup, Setup, Text Translation.
  2. Enter your source language.
  3. Enter the translation language
  4. Select the table you want to translate
  5. Click in the grid to populate it.
  6. Type in your translations in the translation column.
  7. Click Save when done.
  8. This will now show up for on line translation selections for those tables and items.




Entradas populares de este blog

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...
Leer más

How to create an additional line text (ACLOB) on purchase orders for internal notes

Sin conexión Kyle Klinger hace 1 día Origen:  https://www.sagecity.com/support_communities/sage_erp_x3/f/sage-x3-general-discussion-forum/143870/how-to-create-an-additional-line-text-aclob-on-purchase-orders-for-internal-notes I was trying to add internal notes to the purchase orders at a line level and was thought I would share a how to.  If you have a better way, please share.     Add column to PORDERQ; YLINTEX2, Type TXC   Save and validate table This is where the ID of the text will be stored at the record level, i.e. POQ~00000007, this is similar to field LINTEX  On screen POH2 Add column YLINTEX2, to Block 1. Most likely you will want this field to be hidden. On column NBLIG add a button action ACLOB2, description "Text internal" This button action will require an action parameter "CODE2", it will not be available until after save. Set the parameter "CODE2" to [M:POH2]YLINTEX2(nolign-2), the field that was just added....
Leer más

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  ...
Leer más