How to Pass Parameter Values to Action through Function in Sage X3

MAY 5, 2017 PUBLISHED BY PANNI

https://www.pannimanagement.com/?blog=how-to-pass-parameter-values-to-action-through-function-in-sage-enterprise-management

Passing the parameter values is an important process in Sage X3 V9, especially when we use action parameters through function. The following are the steps to pass values to the action process through function in Sage X3.

Create one window for the testing purpose called “YTEST”. Go to

All Development Script Dictionary

$C:\Users\Administrator\Desktop\graphical requestor\param-1.png$

Script Dictionary Actions Action parameters

Click the action parameters as shown below.

$C:\Users\Administrator\Desktop\graphical requestor\param-1.2.png$

The following screen will appear as shown below

$C:\Users\Administrator\Desktop\graphical requestor\param-1.3.png$

Here you can create the new action, which is window entry type and map window, also add a specific process.

$C:\Users\Administrator\Desktop\graphical requestor\param-2.png$

Add the parameter, which we have created earlier in the action parameters function.

$C:\Users\Administrator\Desktop\graphical requestor\param-3.png$

Once an action has created successfully with parameters, the next step is to provide the action code to function. These parameters will come up in the parameter field automatically based on the action code given in the action code field. We will have to assign the parameter values as input, either they could be hardcoded values or screen field codes like “[M: XYZ] ABCDEF” as shown below.

$C:\Users\Administrator\Desktop\graphical requestor\param-4.png$

We need to write the code to display the parameter values through a specific process as shown. The PARAM is the standard variable, which is an array type.

When we provide the parameters in action, the parameter’s values will be automatically stored in the PARAM variable. The PARAM index will start from “1” by default.

$C:\Users\Administrator\Desktop\graphical requestor\param-5.png$

After the coding part has completed, execute the function and click on the Ok button in the message window, then the parameter’s values will be displayed as per the code written in the specific process.

AllSalesQuotes

$C:\Users\Administrator\Desktop\graphical requestor\param-6.png$

And also,

$C:\Users\Administrator\Desktop\graphical requestor\param-7.png$

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