Ir al contenido principal

How to call an external REST web services in classic functions

Origen: https://www.sagecity.com/support_communities/sage_erp_x3/b/sageerp_x3_product_support_blog/posts/how-to-call-an-external-rest-web-services-in-classic-functions

Autor: Ali Esfahani

In this blog, I like to show an example of how you can call an External/Outgoing REST web services in a classic function.

Before we get to the example , the API used for this is called ASYRRESTCLI and the function used is EXEC_REST _WS.

So if you search our online help for ASYRRESTCLI you will see below.




Please note that this is just a simple example(there might be other ways to accomplish this). The external API call is going to a free JSON API http://fixer.io/ ( you can read more about this API by visiting their website)

The requirement presented for this example is that we like to have a button in Purchase order entry that shows the current exchange rates.

  1. Open Administration, Administration, Web Services, Rest web services.
  2. Click on New REST web service to create a new REST web service connection.
  3. Enter the information like below ( for information on each field review online help)




  4. Open Development, Script Dictionary, Windows.
  5. Select OPOH windows.
  6. Click on Buttons/menus Tab.
  7. Enter a new line like below.





  8. Click Save and Validate.
  9. Open Setup, Purchasing, Entry transactions, Orders.
  10. Select your entry transaction and click Validate.
  11. Open Development, Script Dictionary, Scripts, Script editor.
  12. Enter SPEPOH for the file name.
  13. Enter below code.



    $ACTION
    Case ACTION
     When "EXEBOUT"    : Gosub BOUTON
    Endcase
    Return

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

    $BOUTON

    If BOUT="3"  ###### this is the code of our button in Window dictionary
      # Contains the result header and body
      Local Clbfile RESHEAD(0),RESBODY(0)
      Local Integer RETVAL
      # No additional parameter nor additional header value are given here (only the values given in ORDER definition are used)
      Local Char PCOD(100)(1..10),PVAL(100)(1..10),HCOD(100)(1..10),HVAL(100)(1..10)
       RETVAL=func ASYRRESTCLI.EXEC_REST_WS("ExchangeRate","GET","/latest",PCOD,PVAL,HCOD,HVAL,"{}", 0,"",RESHEAD, RESBODY)

      If RETVAL=200 : infbox(RESBODY) : Else infbox("somwthing Went wrong") : Endif

    Endif
    Return

  14. Click Save and Compile.
  15. Now open Purchasing, Orders, Orders.
  16. Select an existing Purchase order.
  17. Click on your newly created button.



  18. Clicking on the button will produce below.




Conclusion: You can use ASYRRESTCLI and function EXEC_REST_WS to execute an outgoing web service call

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