Ir al contenido principal

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.
Sage ERP X3 Help Screen
In this example, the Temp directory is used. Below is a snapshot of the directory where the .exe was copied.
Sage ERP X3 Temp File Directory
NOTE: The .exe must reside in the X3 client installation directory, so if a local client is used, the .exe must be copied to each workstation accessing the .exe.

CREATE THE PROCESS

Go to the Process editor (Development > Processes > Processes > Process editor), and create a process to call the external program.
Copy the code below to the process editor. The .exe file name will need to be modified to match the name of the .exe being called. Compile the code.
##########################################################

# Processing Name - ZSLSUPD

# Description     - Used to call salesperson utility

# Created By      - D. Hartman, RKL

# Date Created    - 10/28/2014

##########################################################


$ACTION

Case ACTION

 When "TRT_DIV" : Gosub TRT_DIV

 When default

Endcase

Return



$TRT_DIV



Local Char RETOUR : RETOUR = ""



Callui RETOUR="" With "UIAction="+chr$(1)+"OpenFile",

& "UILocalDir="+chr$(1) + "Temp",

& "UILocalFile="+ chr$(1) +"SalespersonUtility.exe"



Return

CREATE AN ACTION

The next step is to create an action in Sage ERP X3 that will call the process code referenced above (Development > Processes > Actions > Actions).
Calling an External Program from Sage ERP X3 Action

CREATE A FUNCTION

The next step is to create a Function to call the action created above (Development > Processes > Functions).
The Parent menu value should match the name of the menu where the function call should appear.
Calling an External Program from Sage ERP X3 Function
Calling an External Program from Sage ERP X3 Parameters

VALIDATE THE MENU

If the function is added to a menu, the menu profile(s) will have to be validated (Development > Utilities > Dictionary > Validation > Menus) for the item to appear.

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...
Leer más

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 ,  ...
Leer más

How To Add a Custom Selector for the Screen Field

Fuente original del artículo:   https://www.rklesolutions.com/blog/how-to-add-a-custom-selector-for-the-screen-field January 5, 2022 By RKL Team Leave a Comment There may be times when you want to add a pop-up window to select a field for a screen. Sometimes this can be handled automatically if the field is a standard X3 object field (i.e. when selecting a product with a type of ITM from the ITMMASTER table). There may be other times where a standard look-up is not available, and some custom code is required to do the selection window. We'll show you how to add a custom selector of your choosing to the screen field. ADD SELECT ON SCREEN FIELD The first step is to add the appropriate code to the field on the screen in Sage X3: Go to  Development > Script Dictionary > Screens Select Your Screen Select the field to have the lookup for  by moving your cursor to it on the screen. The field should show with a blue background. Select a type of "Selection" , and an  ac...
Leer más