How to skip entry transaction pop-up and select a default entry transaction?

Fuente original:

https://www.greytrix.com/blogs/sagex3/2018/07/22/how-to-popup-file-selection-window-in-sage-x3/

By Greytrix | May 8, 2018

You might have come across a situation where you might have to open a window via code. Here, if there are multiple entry transactions for the window, then the Entry Transaction Dialog will pop-up and would require the user to manually select the Entry transaction before the opening of the desired window. This can be avoided by setting the value of GFLAG after the standard action of “DEFTRANS”.

Syntax:

In the Specific Processing file for the Window, call the Standard action first and set the GFLAG variable with the desired transaction. In the below case the default transaction is set as “ALL”.

Fig: Code Snippet

Hope this blog helps!

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