IntellX for Sage X3 icon

IntellX for Sage X3

Read, create or modify a Sage X3 object via the XCHATX3OBJ sub-program (JSON in, JSON out)

Actions9

Create Sage X3 Object

AI-generated

Summary

Creates a Sage X3 object by sending the configured object code, optional transaction and identifier, and JSON data to the XCHATX3OBJ sub-program with the CREATE action. Returns the operation status and any parsed data, messages, session ID, or requested diagnostics.

Inputs

  • Action Code — Defaults to CREATE; can be changed to send a different action code.
  • Sage X3 Object Code (required) — Object to create, such as ITM, SOH, or BPC.
  • Transaction Code — X3 transaction code; leave empty to use the default.
  • Identifier — Primary key for the new object. Usually match this to the key field in Data unless Sage X3 generates the key.
  • Data (JSON) (required) — Fields to set, sent as XDATAJSON. X3 fields are dimensioned, so provide values as arrays, for example {"ITM0":{"TSICOD":["20"]}}; dates use YYYY-MM-DD.
  • Context (Optional) — Can set the X3 language or target user, include hidden fields, or restrict the response to selected field and screen codes. The user override is honored only for callers with GPROFIL=ADMIN.
  • Advanced Options — Can override SOAP code language, pool alias or pool ID, sub-program name, and request timeout. Also controls array compaction and trailing-empty trimming, and whether to include the raw SOAP response, request, or parsed result in output.

Output shape

A list of one result item per input item.

Each result includes success, status, action, object, and identifier; transaction is included when set. Parsed X3 data, messages, trace, sessionId, and technicalInfos are included when present. Single-value arrays are compacted and trailing empty array values are trimmed by default. Optional diagnostics add request, result, or raw response fields. If Continue On Fail is enabled, failures return an error item; otherwise the node raises an error.

Links

Discussion