Ir al contenido principal

How to upload a file from the client?


You may have a need to upload a file to the server, and in the past you may have used COPSRV routine from ORDSYS.
On V6 the limit that this routine had was that, you did not know the file name of the file that is getting transferred to the server, and you had to define the file name for the destination. 
But things have changed on newer version.
Before we get to the example review online help title "How to manage files in the storage area" 

As you noted in the online help, in the new version COPSRV will copy the file to server TMP directory. So in below example I am going to use another routine MOVE from ORDSYS to move the file to my desired location.
In this example, I am adding a button to Sales order, for transferring the file.
  1. Open Development, Script dictionary, Windows.
  2. Select OSOH window.
  3. Add a new button. 

  4. Save and Validate.
  5. Open Setup, Sales, Entry transactions, Orders.
  6. Validate the entry transaction.
  7. Now open Development, Script dictionary, Script Editor.
  8. Select SPESOH and add below code. 



    $ACTION
    Case ACTION
    When "EXEBOUT" : Gosub BOUTON
    Endcase
    Return
    　
    ##############
    　
    $BOUTON
    If BOUT="8" ###### this is the code of our button in Window dictionary

    Local Char FICSRV(250),FICCLI(250),MYPATH(250)
    Local Integer ASTATUS
    Local Integer stat
    　
    FICCLI = ""
    FICSRV = filpath("tmp","","")  ######## here I am building path to tmp folder
    MYPATH= filpath("ATT\SALES","","") ########## here I am building the path to my destination folder
    　
    Call COPSRV(FICCLI,FICSRV,ASTATUS) From ORDSYS
    FICSRV=FICSRV+"\"+FICCLI
    If ASTATUS = 0
        Call MOVE(FICSRV,MYPATH,stat) from ORDSYS  ### this will move the file for me
    　
    Endif
    If stat =0
    Infbox("UPLOAD WAS GOOD THANKS")
    Else
    Infbox("Somethign went wrong")
    Endif
    　
    Endif
    Return

  9. Save and Compile.
  10. Now when open Sales , Orders, Orders.
  11. Click on the button on right. 


  12. After click on the button, you will get the following. 

  13. Use the button to select the file or drag the file here, then click Ok.
  14. Now you will get the information box that it was ok. 

Conclusion: You can use COPSRV to copy files to the server.

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