How to change the Enter key functionality

Origen fuente: http://sageerpx3dev.blogspot.com/2014/12/how-to-change-enter-key-functionality.html

In Sage X3 screens, the Enter key usually has some default functionality - for example, it might be triggering the OK button. Regardless of what the actual default functionality is, here is how you can block it or replace it with something else.

When the Enter key is pressed, X3 assigns the value GSTARET to the variable REPONSE. You can check for that condition in the 'After Choice' action. Depending on the template you are using, this action might be APRES_CHOI or AP_CHOIX. For the examples below, we will use APRES_CHOI.

First of all, you need to add the action to the list of actions in the $ACTION label of your specific processing file like this:

$ACTION
Case ACTION
# ... Other actions ...
When "APRES_CHOI" : Gosub APRES_CHOI
# ... Other actions ...
When Default
Endcase
Return

Then, in the action handler, if you just want to stop the standard Enter key functionality from executing, you can do:

$APRES_CHOI
If REPONSE=GSTARET : REPONSE=0 : Endif
Return

And if you want to replace it with new functionality:

$APRES_CHOI
If REPONSE=GSTARET
REPONSE=0
Infbox("Custom functionality goes here!")
Endif
Return

Once you make sure that the Infbox statement is getting executed when you press Enter in your screen, you can put in its place something actually useful, depending on your needs.

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

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...

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