Actions9
Modify Sage X3 Object
AI-generatedSummary
Updates an existing Sage X3 object by sending its object code, required identifier, optional transaction code, and JSON field data to the XCHATX3OBJ sub-program with the MODIFY action. Returns the operation status and any parsed response data or messages; configure context and advanced options to filter the response, reuse a session, or include debugging details.
Inputs
- Action Code — Defaults to MODIFY. Can be edited to send a different action; the value is trimmed and upper-cased.
- Sage X3 Object Code (required) — Object code to modify, such as ITM, SOH, or BPC.
- Transaction Code — XTRANSACTION value; an empty value uses the Sage X3 default.
- Identifier (required) — Primary identifier of the existing object (XIDENT).
- Data (JSON) (required) — Fields to set, sent as XDATAJSON. Sage X3 fields are dimensioned, so use arrays for values (for example, {"ITM0":{"TSICOD":["20"]}}); use indexed names such as "TSICOD(1)" to target a specific index. Dates are entered as YYYY-MM-DD.
- Context (Optional) — XCHATX3OBJ-level options: include hidden fields, override the language or target user, and restrict response fields or screens. The user override is honored only when the caller has GPROFIL=ADMIN.
- Advanced Options — Can override SOAP code language, pool alias or pool ID, public name, and request timeout. Pool ID can be set to a prior call's sessionId to reuse the Sage X3 session, which is needed to preserve a lock when chaining READ → MODIFY. Also controls compacting single-value arrays, trimming trailing empty array values, and including the raw SOAP response, request, or parsed result.
Output shape
A single output item containing one JSON object per input item.
The object includes success, status, action, object, and ident; transaction is included when non-empty. Parsed data, messages, trace, sessionId, technicalInfos, and optional result, raw, or request details are included when available or enabled. Single-value arrays are compacted and trailing empty array values are trimmed by default. With Continue On Fail enabled, a failed item instead contains error, code, and raw fields.