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 loging informations

0001 = Errors output

0000 = Standard output

Let’s make an example :

1) 4GL Silent import call

Raz [M:IMP2]

[M:IMP2]MODIMP = YAOENAME # Import Template Name

[M:IMP2]NOMIMP = YTMPFILE # File Location and Name

[M:IMP2]TYPEXP = 2 # Server

Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ

Call ERR_IMPORT([M:IMP2]STAT, YMESSAGE) From GIMPOBJ

If [M:IMP2]STAT or GOK < 1 : YRESTA += 1 # Import Error

Else : YRESTA = 0 : Endif # Import Successful

If !GSERVEUR : Call FERME_TRACE From LECFIC : Endif

2) Log reading

Openi filpath("TRA",GTRACE,"tra",0) Using [YTRA]

Local Char XLINE(100)

Repeat

Rdseq XLINE Using [YTRA]

If left$(XLINE,5)="<0001" # This is an error

Append YMESSAGE(YRESTA), right$(XLINE,6) : YRESTA += 1

Break

Elsif find(left$(XLINE,11), "Création de") # This is OK

[L]Y2_TSKNUM = right$(XLINE,13)

Append YMESSAGE(YRESTA), [L]Y2_TSKNUM : YRESTA += 1

Endif

Until fstat <> 0

Openi Using [YTRA]

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