Ir al contenido principal

Sage X3 Create a new CLOB Text


Here how to create a CLOB text
  1. Funprog F_CRELOB(YABRFIC,YTEXTE)
  2. Value Char YABRFIC
  3. Value Char YTEXTE
  5. Local Char XXRTFTXT(250)(3)
  6. XXRTFTXT(0) = "{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 MS Sans Serif;}}\viewkind4\uc1\pard\f0\fs17 "
  7. XXRTFTXT(1) = YTEXTE
  8. XXRTFTXT(2) = "\par}"
  10. Local Char X_RET
  11. Local Integer XXOK
  12. Local Char XCHAMPLIEN : XCHAMPLIEN = "YYYY"
  13. Global Char YYYY : YYYY = YABRFIC
  15. Local Clbfile WWCLOB
  16. Local Mask ACLOB [M:ACL]
  17. Setlob WWCLOB With XXRTFTXT
  18. [M:ACL]CLOB = WWCLOB
  19. Call CRE_CLOB_ACL(XCHAMPLIEN,XXOK) From TRTX3TEX
  20. Close Local Mask [M:ACL]
  21. X_RET = YYYY
  22. Kill YYYY
  24. End X_RET

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