Ir al contenido principal

Calling Subprogram Sage X3 Web Services


CREATE THE CALL CONTEXT


CALL THE WEB SERVICE

The example below is based on calling a Sage ERP X3 Web Service that was generated from a custom sub-program. Refer to the post Day 2 – Creating X3 Web Services for instructions on creating a custom sub-program and exposing it as a web service. The code sample below displays the .net code used to call the web service.
    1. The first step will be to construct the XML parameter list to make the web service call. This will vary based on the parameters defined in the custom web service. The example below is based on web service ZWSCUSTLIS. As shown below, the parameters passed into the web service are UPDDAYS and CUSTID. The results will include an array of up to 2000 customers.
      WebServices14
    2. The XML Parameter string will be constructed as shown below, to match the required parameters for the subprogram call.
<PARAM>
    <FLD NAME="UPDDAYS" >30</FLD>
    <FLD NAME="CUSTID" > </FLD>
</PARAM>
  1. Call the Web Service
Below is a snippet of the .net code required to call the web service. The web service will return an xml string containing the call results. This string can be parsed to extract the details of the call.

public
List<X3_Account_List> GetAccounts(int iUpdateDays, string sAcctId){  List<X3_Account_List> lsAccts = new
List<X3_Account_List>(); 
 // Initialize Connection Values
 X3DataAccessConn.CallContextClass oCallContext = _connDetails.GetCallContext();
// Complete call context 
oCallContext.CallContext.requestConfig ="adxwss.trace.on=off&adxwss.trace.size=16384&adonix.trace.on=off&adonix.trace.level=3&adonix.trace.size=8";
 // Build Input XML with Parameters
  StringBuilder xmlInput = new
StringBuilder("");  xmlInput.Append("<PARAM>");xmlInput.AppendFormat("<FLD NAME="{0}">{1}</FLD>", "UPDDAYS", iUpdateDays.ToString());xmlInput.AppendFormat("<FLD NAME="{0}">{1}</FLD>", "CUSTID", sAcctId);xmlInput.Append("</PARAM>");
// Call web service
oCallContext.ResultXML = oCallContext.WebService.run(oCallContext.CallContext, "ZWSCUSTLIS", xmlInput.ToString());  string result = "";  foreach (X3WebService.CAdxMessage msg in oCallContext.ResultXML.messages){result += msg.message.ToString() + "^";}
// Success
 if (result.Length == 0){ string xml = oCallContext.ResultXML.resultXml.ToString();   lsAccts = ExtractAccts(xml);}
return lsAccts;}  public
CallContextClass GetCallContext(){  // Initialize connection values
  CAdxCallContext callContext = new
CAdxCallContext();  CAdxWebServiceXmlCCService webService = new
  CAdxWebServiceXmlCCService();  CAdxParamKeyValue[] paramKey = new
  CAdxParamKeyValue[1];  CAdxResultXml resultXML = new
  CAdxResultXml();callContext.codeLang = _x3Language; // Connection language
callContext.codeUser = _x3User; // X3 user
callContext.password = _x3Pwd; // X3 password
callContext.poolAlias = _x3WSPool; // Connection pool name

CallContextClass context = new
CallContextClass(callContext, webService, paramKey, resultXML);return context;}

Entradas populares de este blog

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

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

How To Add a Custom Selector for the Screen Field

Fuente original del artículo:   https://www.rklesolutions.com/blog/how-to-add-a-custom-selector-for-the-screen-field January 5, 2022 By RKL Team Leave a Comment There may be times when you want to add a pop-up window to select a field for a screen. Sometimes this can be handled automatically if the field is a standard X3 object field (i.e. when selecting a product with a type of ITM from the ITMMASTER table). There may be other times where a standard look-up is not available, and some custom code is required to do the selection window. We'll show you how to add a custom selector of your choosing to the screen field. ADD SELECT ON SCREEN FIELD The first step is to add the appropriate code to the field on the screen in Sage X3: Go to  Development > Script Dictionary > Screens Select Your Screen Select the field to have the lookup for  by moving your cursor to it on the screen. The field should show with a blue background. Select a type of "Selection" , and an  ac...
Leer más