Ir al contenido principal

Sage X3 procedure to launch a report


Here how-to run an X3 report  programmatically.
  1. $TEST_11_B
  3. #Variable for report parameters
  4. Local Char TBPAR_BP(15)(1..50),TBVAL_BP(30)(1..50)
  6. If clalev([F:SDH]) = 0 Then Local File SDELIVERY [F:SDH] : Endif
  7. Read [F:SDH]SDH0 = "S0112BDF00138"
  9. #Set parameters value
  10. TBPAR_BP(1) = "Livraisondeb" : TBVAL_BP(1) = [F:SDH]SDHNUM
  11. TBPAR_BP(2) = "Livraisonfin" : TBVAL_BP(2) = [F:SDH]SDHNUM
  12. TBPAR_BP(3) = "numedt" : TBVAL_BP(3) = "0" #num$(ARM_REQ_BP)
  13. TBPAR_BP(4) = "sitedeb" : TBVAL_BP(4) = [F:SDH]STOFCY
  14. TBPAR_BP(5) = "sitefin" : TBVAL_BP(5) = [F:SDH]STOFCY
  15. TBPAR_BP(6) = "clientdeb" : TBVAL_BP(6) = [F:SDH]BPCORD
  16. TBPAR_BP(7) = "clientfin" : TBVAL_BP(7) = [F:SDH]BPCORD
  17. TBPAR_BP(8) = "codimp" : TBVAL_BP(8) = "2"
  19. #Call at the standard X3 Subprog to execute the report
  20. #The Subprog ETAT needs these parameters:
  21. #1 - "BONLIV" Name of the report (is not the name of the rpt Crystal file)
  22. #2 - "ANTEPRIMA" Name of the destination
  23. #3 - "FRA" Language, leave this blanc to use the default language
  24. #4 - 0 or 1 it shows or not the info message 'print executed'
  25. #5 - TBPAR_BP
  26. #6 - TBVAL_BP
  28. # Run the report with the info message 'print executed'
  29. #Call ETAT("BONLIV","VTPRTCED01","",1,"",TBPAR_BP,TBVAL_BP) From AIMP3
  31. # Run the report without the info message
  32. Call ETAT("BONLIV","ANTEPRIMA","",0,"",TBPAR_BP,TBVAL_BP) From AIMP3
  34. Return

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

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

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