Ir al contenido principal

Sage X3 Job with dynamics parameters


In Sage X3 we can setting execution scheduling of a command using the SYSTEME Sage x3 job.
You can manage the Sage x3 jobs with Usage\Batch Server\Task management menu (GESABT function).
As parameter we pass it the system command to execute, for example “C:\temp\command.bat par1 par2″,  and that’s it.
If by chance we need to move this scheduling from a Sage X3 folder to another,
to pass the name Sage x3 folder as dynamic parameter can be useful,
so we do not have to modify the command to pass to the job SYSTEME every time.
To do this just create a job SYSTEME wrapper.
The SYSTEME job call the homonym SYSTEME action, which has as unique parameter the command string to execute;
to reach our target so we will create a YSYSTEME job and a YSYSTEME action.
But this EXESYS action what do it do precisely? It call a subprog of ORDSYS.
Here an example: the following code line executes the batch command Command.bat
that is present in the directory c:\DIR\SUB\
Call SYSTEME ("","C:\DIR\SUB\Command.bat","b",YSTAT) From ORDSYS
So, we duplicate the EXESYS action renaming it as YEXESYS.
We leave everything as it is, except for specific script box where we insert YEXESYS.
(at the place of YXEXESYS: this source file doesn’t exist, you can check the correspondant adx file is not present).
Remember to insert the Activity code.
Then duplicate the SYSTEME function SYSTEME giving it YSYSTEME name; we can remove value at “Parent menu” box
and as action we set YEXESYS.
Good, now we duplicate also the SYSTEME job setting the new job with name YSYSTEME and with function YSYSTEME.
At this point we just have to write the source code YEXESYS,
so that we can pass a parameter to evalue at runtime enclosed in two “%”:

###############################################################
$ACTION
Case ACTION
 When "CONTROLE" : Gosub CONTROLE
 When Default
Endcase
Return
###############################################################

###############################################################
#NB: [M:EXS]ORDSYS is the field that contains the command
###############################################################
$CONTROLE
Local Integer I1,I2
Local Char YPARAM(30)
Local Char YVALUE(30)
 I1=0
 I2=0
 I1=instr(1,[M:EXS]ORDSYS,"%")
 If I1
   I2=instr(I1+1,[M:EXS]ORDSYS,"%")
   If I2
   YPARAM = seg$([M:EXS]ORDSYS,I1+1,I2-1)
   YVALUE = evalue (YPARAM)
   [M:EXS]ORDSYS = func YSAGEDEV.REPLACE([M:EXS]ORDSYS, "%"+YPARAM+"%", YVALUE)
   Endif
 Endif
End
###############################################################
Very good, now in scheduling we could pass as parameter, for instance,
c:\Sage\folders\%nomap(0)%\YIMPORT\filename.txt %nomap(0)%
that will be transformed into (in the case that Sage X3 folder name is TEST)
c:\Sage\folders\TEST\YIMPORT\filename.txt TEST
In this way we can pass as dynamic parameters anything can be interpreted by evalue.
Note that with this code we can insert nomap(0) twice, but we can not insert nomap(0) and also nomap(1).
Attention, the program is not for production environment.
In the case of syntax error the command will be executed anyway, with unforeseeable consequences.
I help this help you,
and if you use it in a original way, write it in the comments!

If you wish a complete version of the program, with
  1. syntax control and errors management
  2. evalue function errors management
  3. multiple different parameters management
  4. a batch file that manages the FOLDER parameter without having to worry about the parameters already present
subscribe and you will receive it for free with all other additional contents!

Entradas populares de este blog

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

How to Call an External Program from Sage ERP X3

Origen fuente:   https://www.rklesolutions.com/blog/sage-x3-call-external-program November 20, 2014 By Denise Hartman Leave a Comment It is sometimes useful to be able to access external programs, such as .exe files, from the  Sage ERP X3   menu. Below are instructions for adding a menu item to Sage X3 that references a .Net .exe. COPY THE .EXE FILE TO THE SAGE X3 DIRECTORY The example used here uses the  Callui  function in the Sage X3 code to call OpenFile, and references the .exe program using the parameter UILocalDir. The program being executed must reside in a pre-defined list of directories available to this function. Depending on the parameter used for UILocalDir, the .exe should be copied to one of the 3 directories below. Temp Report RtsTemp Below is an excerpt from the X3 Help, which defines where each of these directories resides within the Sage ERP X3 client installation. In this example, the Temp directory is used. Bel...

How to Delete particular row and reset Grid

Origen: https://www.greytrix.com/blogs/sagex3/2014/06/30/how-to-delete-particular-row-and-reset-grid/ By  Greytrix   |   June 30, 2014 0 Comment We usually come across a scenario when we need to delete row from a grid through coding. Now we can even think of using SQL queries to delete the data, but these changes were reflected at the database level. The screen do not have the changes reflected and this may cause data inconsistency. So for deleting line from grid and then resetting the grid I used ‘DELA’ an existing function of X3. New Stuff :   How to send mail programmatically Dela  is used to delete elements from single-sized tables, from a given index. And also it resets the grid.   Syntax: Dela start [ , number [ , limit ] ] list_nom_var Example: Dela is used to delete elements (default 1) from a set of single-sized tables. In the instruction’s syntax, start establishes the index (shared by all the tables) where the deletion ...