How to Copy Detail Lines in Sage X3

Origen: https://www.greytrix.com/blogs/sagex3/2011/10/27/how-to-copy-detail-lines-in-sage-erp-x3/

By Greytrix | October 27, 2011

Consider a scenario where you have created a utility in Sage X3 and you need to create a GL Journal entry, based on the field inputs within the X3 custom screen. Now to achieve this, the option is to map all the custom screen fields with the Sage X3 Journal fields so that all the custom screen fields populate the detail lines in Journal.

We can populate the Journal fields by assigning the Custom screen field with the Journal fields using the assignment statement for each field individually as listed below:

[M:TARGETSCREEN]FIELD1 = [M:SOURCESCREEN]FIELD1
[M:TARGETSCREEN]FIELD2 = [M:SOURCESCREEN]FIELD2
[M:TARGETSCREEN]FIELD3 = [M:SOURCESCREEN]FIELD3

And so on……

However, this surely becomes cumbersome if there are many fields within the table. While checking for another quick solution which can map the fields without going for individual assignment of each field, we found the snippet code which can help you out in the direct assignment of a group of fields.

The Code discovered by Greytrix team of experienced techno-functional consultants, uses the Assign command to pass the value from source table to destination table.

Refer the code snippet below:

Code Snippet:
Assign(“[M:TARGETSCREEN]”+[F:AMZ]CODZON+”(“+num$(<destination line (Copy To) >)+”)”) With evalue(“[M:SOURCESCREEN]”+[F:AMZ]CODZON+”(“+num$($(<original line (Copy from) >)+”)”)

This code sample will copy all the custom fields directly within the Journal detail without checking out every field individually.

In this way you can copy Detail Lines in Sage X3.

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 , ...

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....

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 ...