@celigo/api-specs 0.2.219 → 0.2.221

package/dist/import.yml

@@ -4184,9 +4184,29 @@ components:
                       (replace a sublist's lines on update), and the rows Celigo's field-definitions article
                       lists by label (Ignore Mandatory Fields, Initialize Values, Persist New Line Insertion
                       Order, Print Nlapi Debug Logs, Group Lines By, Use Address Subrecord, Void Transaction).
+                      For a NetSuite field it is always the field's script id: the mapping editor shows each
+                      destination by its label ("Customer (InternalId)", "Items : Location (InternalId)"),
+                      and a label saved here is not a field. The control rows above keep their own ids.
                     examples:
                       - companyname
                     x-celigo-ai-guidance:
+                      - |-
+                        `Items : Location (InternalId)` saved as a body row's `generate` — the editor's
+                        label for `item[*].location.internalid`, not a field id — was accepted by the save,
+                        rendered by the mapping preview, and ignored by NetSuite on a sales order import:
+                        the import succeeded with the field blank and no error anywhere. A label is never
+                        a script id. Resolve ids from the record metadata
+                        (`GET /v1/netsuite/metadata/suitescript/connections/{_id}/recordTypes/{recordType}`,
+                        `listNetSuiteRecordTypeFields`), whose rows carry each field's `id` and its editor
+                        label as `name`; that list is the editor's destination dropdown and is form- and
+                        role-dependent, so a standard field hidden on the form is absent from it yet still
+                        written by id.
+                      - |-
+                        A line field is never a body row. `item[*].<field>` is the record metadata's id
+                        for a sublist field (the editor shows its label, "Items : Location (InternalId)"),
+                        and the form typed as a destination to add a row the editor's picker lacks (see
+                        `lists`); the document stores it as the bare field id under `lists[]` with
+                        `generate: item`. A body row carrying that form is not a line mapping.
                       - |-
                         `celigo_recordmode_dynamic` with `hardCodedValue: "true"` is Celigo's documented
                         "Use Dynamic Mode" row: the record is created or loaded in NetSuite's dynamic mode,
@@ -4412,8 +4432,9 @@ components:
                   generate:
                     type: string
                     description: |
-                      The NetSuite sublist ID (e.g., "item" for sales order line items,
-                      "addressbook" for address sublists).
+                      The NetSuite sublist ID as the record metadata lists it (e.g., "item" for sales
+                      order line items, "addressbook" for address sublists); the mapping editor shows
+                      the sublist by its label ("Items"), which is never the id.
                   jsonPath:
                     type: string
                     description: LEGACY — do not set. Nominally the JSON path to the array of sublist records, but NetSuite DA ignores a top-level jsonPath here.
@@ -4485,7 +4506,30 @@ components:
                               `netsuite_da.lookups[].expression`.
                         generate:
                           type: string
-                          description: NetSuite sublist field ID to write to.
+                          description: |-
+                            NetSuite sublist field ID to write to, stored as the bare field id (`location`,
+                            `quantity`): the editor's `item[*].` prefix, the `.internalid` suffix (see
+                            `internalId`) and the editor's label ("Items : Location (InternalId)") are
+                            the editor's forms, not the stored value.
+                          x-celigo-ai-guidance:
+                            - |-
+                              Which line field exists depends on the NetSuite account: a sales order line's
+                              location is `location` unless the account's Intercompany Cross-Subsidiary
+                              Fulfillment feature is enabled, when NetSuite replaces it with
+                              `inventorylocation` — the record metadata then lists
+                              `item[*].inventorylocation.internalid` and no `item[*].location.internalid`;
+                              without the feature it lists `item[*].location.internalid` and
+                              `item[*].location` and no row whose id contains `inventorylocation`. Map the
+                              line location to whichever the account has, stored as `generate:
+                              inventorylocation` or `generate: location` with `internalId: true` — the
+                              metadata id's `.internalid` suffix is the `internalId` flag, not part of the
+                              stored id.
+                            - |-
+                              Put the `item` row before the line's `inventorylocation` row. Observed on a
+                              standard-mode sales order import (no `celigo_recordmode_dynamic` row):
+                              with `inventorylocation` (`internalId: true`) mapped above `item`, every
+                              line failed — the location was validated against a line that had no item
+                              yet; moved below the `item` row, the same mapping saved.
                         hardCodedValue:
                           type: string
                           description: Static value for this sublist field.
@@ -4731,7 +4775,8 @@ components:
                   as a writable one. The mapper's "Items : Line ID" is `line` (the fulfillment's own line number,
                   equal to the order line only on a fresh full transform) and "Items : Line Number" is `linenum`;
                   `orderline` and `kitmemberof` are not in its picker — type `item[*].orderline` /
-                  `item[*].kitmemberof` as the destination.
+                  `item[*].kitmemberof` as the destination (the metadata id form of a sublist field; the
+                  document stores `orderline` / `kitmemberof` under `lists[]` with `generate: item`).
                 - |-
                   Kit components on a fulfillment: the item is the only default key that reaches a component
                   line, so a component two kit lines share fails with `MULTIPLE_LINES_WITH_SAME_KEYS`. Keying the
@@ -9051,7 +9096,7 @@ components:
             or, on a `blob: true` transfer, the existing file being moved; omit it for an
             unencrypted file. `pgp` requires `pgp.symmetricKeyAlgorithm` and a connection holding
             the recipient's public key (`pgp.publicKey`). Not observed in a run here; per the file
-            adaptor's code (IO-213945, the `blob: true` transfer path): with no `compressionFormat`,
+            adaptor's code (the `blob: true` transfer path): with no `compressionFormat`,
             a file over 200 MB fails the record before encryption with `pgp_file_size_exceeded`
             ("The file size exceeds the maximum limit of 200 MB supported for PGP encryption." —
             the adaptor's `errorStore.js` text); with `compressionFormat` set the adaptor skips that

package/dist/tool.yml

@@ -16470,9 +16470,29 @@ components:
                       (replace a sublist's lines on update), and the rows Celigo's field-definitions article
                       lists by label (Ignore Mandatory Fields, Initialize Values, Persist New Line Insertion
                       Order, Print Nlapi Debug Logs, Group Lines By, Use Address Subrecord, Void Transaction).
+                      For a NetSuite field it is always the field's script id: the mapping editor shows each
+                      destination by its label ("Customer (InternalId)", "Items : Location (InternalId)"),
+                      and a label saved here is not a field. The control rows above keep their own ids.
                     examples:
                       - companyname
                     x-celigo-ai-guidance:
+                      - |-
+                        `Items : Location (InternalId)` saved as a body row's `generate` — the editor's
+                        label for `item[*].location.internalid`, not a field id — was accepted by the save,
+                        rendered by the mapping preview, and ignored by NetSuite on a sales order import:
+                        the import succeeded with the field blank and no error anywhere. A label is never
+                        a script id. Resolve ids from the record metadata
+                        (`GET /v1/netsuite/metadata/suitescript/connections/{_id}/recordTypes/{recordType}`,
+                        `listNetSuiteRecordTypeFields`), whose rows carry each field's `id` and its editor
+                        label as `name`; that list is the editor's destination dropdown and is form- and
+                        role-dependent, so a standard field hidden on the form is absent from it yet still
+                        written by id.
+                      - |-
+                        A line field is never a body row. `item[*].<field>` is the record metadata's id
+                        for a sublist field (the editor shows its label, "Items : Location (InternalId)"),
+                        and the form typed as a destination to add a row the editor's picker lacks (see
+                        `lists`); the document stores it as the bare field id under `lists[]` with
+                        `generate: item`. A body row carrying that form is not a line mapping.
                       - |-
                         `celigo_recordmode_dynamic` with `hardCodedValue: "true"` is Celigo's documented
                         "Use Dynamic Mode" row: the record is created or loaded in NetSuite's dynamic mode,
@@ -16698,8 +16718,9 @@ components:
                   generate:
                     type: string
                     description: |
-                      The NetSuite sublist ID (e.g., "item" for sales order line items,
-                      "addressbook" for address sublists).
+                      The NetSuite sublist ID as the record metadata lists it (e.g., "item" for sales
+                      order line items, "addressbook" for address sublists); the mapping editor shows
+                      the sublist by its label ("Items"), which is never the id.
                   jsonPath:
                     type: string
                     description: LEGACY — do not set. Nominally the JSON path to the array of sublist records, but NetSuite DA ignores a top-level jsonPath here.
@@ -16771,7 +16792,30 @@ components:
                               `netsuite_da.lookups[].expression`.
                         generate:
                           type: string
-                          description: NetSuite sublist field ID to write to.
+                          description: |-
+                            NetSuite sublist field ID to write to, stored as the bare field id (`location`,
+                            `quantity`): the editor's `item[*].` prefix, the `.internalid` suffix (see
+                            `internalId`) and the editor's label ("Items : Location (InternalId)") are
+                            the editor's forms, not the stored value.
+                          x-celigo-ai-guidance:
+                            - |-
+                              Which line field exists depends on the NetSuite account: a sales order line's
+                              location is `location` unless the account's Intercompany Cross-Subsidiary
+                              Fulfillment feature is enabled, when NetSuite replaces it with
+                              `inventorylocation` — the record metadata then lists
+                              `item[*].inventorylocation.internalid` and no `item[*].location.internalid`;
+                              without the feature it lists `item[*].location.internalid` and
+                              `item[*].location` and no row whose id contains `inventorylocation`. Map the
+                              line location to whichever the account has, stored as `generate:
+                              inventorylocation` or `generate: location` with `internalId: true` — the
+                              metadata id's `.internalid` suffix is the `internalId` flag, not part of the
+                              stored id.
+                            - |-
+                              Put the `item` row before the line's `inventorylocation` row. Observed on a
+                              standard-mode sales order import (no `celigo_recordmode_dynamic` row):
+                              with `inventorylocation` (`internalId: true`) mapped above `item`, every
+                              line failed — the location was validated against a line that had no item
+                              yet; moved below the `item` row, the same mapping saved.
                         hardCodedValue:
                           type: string
                           description: Static value for this sublist field.
@@ -17017,7 +17061,8 @@ components:
                   as a writable one. The mapper's "Items : Line ID" is `line` (the fulfillment's own line number,
                   equal to the order line only on a fresh full transform) and "Items : Line Number" is `linenum`;
                   `orderline` and `kitmemberof` are not in its picker — type `item[*].orderline` /
-                  `item[*].kitmemberof` as the destination.
+                  `item[*].kitmemberof` as the destination (the metadata id form of a sublist field; the
+                  document stores `orderline` / `kitmemberof` under `lists[]` with `generate: item`).
                 - |-
                   Kit components on a fulfillment: the item is the only default key that reaches a component
                   line, so a component two kit lines share fails with `MULTIPLE_LINES_WITH_SAME_KEYS`. Keying the
@@ -21058,7 +21103,7 @@ components:
             or, on a `blob: true` transfer, the existing file being moved; omit it for an
             unencrypted file. `pgp` requires `pgp.symmetricKeyAlgorithm` and a connection holding
             the recipient's public key (`pgp.publicKey`). Not observed in a run here; per the file
-            adaptor's code (IO-213945, the `blob: true` transfer path): with no `compressionFormat`,
+            adaptor's code (the `blob: true` transfer path): with no `compressionFormat`,
             a file over 200 MB fails the record before encryption with `pgp_file_size_exceeded`
             ("The file size exceeds the maximum limit of 200 MB supported for PGP encryption." —
             the adaptor's `errorStore.js` text); with `compressionFormat` set the adaptor skips that

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.219",
+  "version": "0.2.221",
   "private": false,
   "description": "Public OpenAPI bundles (dist/) and the celigo-cli lint schema pack (schemas.json).",
   "keywords": [

package/schemas.json

@@ -1,8 +1,8 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "adbfb1b8",
-		"generatedAt": "2026-11-02"
+		"iasCommit": "c51652db",
+		"generatedAt": "2026-11-03"
 	},
 	"roots": {
 		"aiagent": 128,