Testing Sage X3 SOAP Web Services in Update 9

In versions of Sage X3 prior to Update 9, a web services test console was available through a web browser. Beginning with PU9, this functionality is no longer available. Classic SOAP Web Service testing can now be done within the X3 website. The lack of the test console has caused some confusion for many who are upgrading to PU9. Below are the steps for testing Classic SOAP Web Services from within X3.

Publishing the Web Services

The classic SOAP web services are created and published in the same way as prior versions, by publishing the object or subprogram as a web service.

INITIAL SETUP

A few steps must be taken to enable the SOAP Web Services. These options can all be found within the Administration section of X3.

Hosts Web Service Setup

From the Administration section, go to the Servers \ Hosts.

Confirm that the Number of Web Service Child Processes has a value.

SET UP THE WEB SERVICE POOL

From the Administration section, go to Web Services \ Classic SOAP pools configuration.

Set up the Pool for the folder (endpoint) being used.

After the Web Service Pool is set up, click Start/Update.

Make sure the Start was successful.

Testing the Web Services

From the Administration section, go to Web Services \ Classic SOAP Web services.

Click the on CAdxWebServiceXmlCC.

Click the down arrow on the left.

A list of operations is displayed. These correspond to the operations from the web-based SOAP tester.

Web Service Description

The getDescription operation returns the web service description. Click the getDescription option, and enter the Language, Pool alias and Public name.

Click Invoke.

The web service description is displayed.

QUERY OPERATION

The query operation is the same as the list operation. Click the query option, and enter the Language code, Pool alias and Public name. Change the list size from 0 to the desired results size.

Click Invoke.

The results will appear in the Response tab.

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

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

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