Ir al contenido principal

How to tab directly to a non-neighbour field in a grid

Origen: http://sageerpx3dev.blogspot.com/2014/11/how-to-tab-directly-to-non-neighbour.html

Tabbing through default values can get boring if you have to do it a lot. The good news is, with Sage X3 you don't have to do it at all!

Suppose, for example, that you enter Sales orders in the following screen (GESSOH function)


On each row, you enter the product code and then you tab through to the Ordered qty field, accepting the default values for Description, Ship site and Sales unit. This is three tabs too many. Wouldn't it be great if you could just hit Tab once in the Product field and get directly to the Ordered qty field, with the default values appearing as they normally should in the three fields in-between?

Well, here's how to do just that.

You need to create an After change action on the Product field. For the Sales orders, this is the [M:SOH4]ITMREF field. You must open the SOH4 screen in the GESAMK function and create the appropriate action like this:


In your specific processing file SPESOH, in the After change action handler (AM_ITMREF) you must assign a value to the zonsui variable, which contains the next field to be entered. To go to the Ordered qty field on the current line, this value must be QTY(nolign-1). So the AM_ITMREF handler should look like this:

Subprog AM_ITMREF(VALEUR)
Variable Char VALEUR()
zonsui="QTY(" + num$(nolign-1) + ")"
End

After you validate your screen and your entry transactions, you will have the desired effect of tabbing directly from Product to Ordered qty field when you enter Sales orders. And you can use this technique in any other screen you want.

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