@celigo/api-specs 0.2.126 → 0.2.127

package/dist/import.yml

@@ -3841,7 +3841,11 @@ components:
               field mapped to `internalid` is overridden by it. When the incoming record
               already carries the NetSuite internal ID, point the lookup at that field with
               the expression form — `["internalid","is","{{{id}}}"]` — rather than removing
-              the lookup.
+              the lookup. Only when every record carries it: on `restletVersion:
+              suiteapp2.0` a record whose field is empty does not fall through to
+              "create" on `addupdate` — the empty value is searched as `isempty` and
+              can match an existing record (see `expression`; SuiteBundle and SuiteApp
+              1.0 create in that case).
           properties:
             extract:
               type: string
@@ -3967,6 +3971,21 @@ components:
                   - DO NOT use `jsonSerialize` here — search expressions take
                     scalar literals, not serialized JSON.  Use `{{{id}}}` or
                     `{{{[Field Name]}}}` directly.
+                - |-
+                  ## A substitution that renders empty is not "no match"
+
+                  When the source field is absent or empty, `["internalid","is","{{{id}}}"]`
+                  renders `["internalid","is",""]`, and the SuiteApp rewrites an empty
+                  `is` / `equalto` / `internalid anyof` value to `isempty` before the
+                  search. On `restletVersion: suiteapp2.0` that search is not treated as
+                  "no match": it can return existing records, and `addupdate` then
+                  updates one of them — an unrelated record receives the mapping (seen
+                  in production as `cant_modify_sub` on a customer the record never
+                  named). SuiteBundle and SuiteApp 1.0 discard a blank `internalid`
+                  match and create. Design so the operational lookup never renders
+                  empty: key it on a value every record carries (the source id stored
+                  as `externalid`), or route records without a destination id to a
+                  separate `add` import.
                 - |-
                   ## Body-level only
 

package/dist/tool.yml

@@ -15422,7 +15422,11 @@ components:
               field mapped to `internalid` is overridden by it. When the incoming record
               already carries the NetSuite internal ID, point the lookup at that field with
               the expression form — `["internalid","is","{{{id}}}"]` — rather than removing
-              the lookup.
+              the lookup. Only when every record carries it: on `restletVersion:
+              suiteapp2.0` a record whose field is empty does not fall through to
+              "create" on `addupdate` — the empty value is searched as `isempty` and
+              can match an existing record (see `expression`; SuiteBundle and SuiteApp
+              1.0 create in that case).
           properties:
             extract:
               type: string
@@ -15548,6 +15552,21 @@ components:
                   - DO NOT use `jsonSerialize` here — search expressions take
                     scalar literals, not serialized JSON.  Use `{{{id}}}` or
                     `{{{[Field Name]}}}` directly.
+                - |-
+                  ## A substitution that renders empty is not "no match"
+
+                  When the source field is absent or empty, `["internalid","is","{{{id}}}"]`
+                  renders `["internalid","is",""]`, and the SuiteApp rewrites an empty
+                  `is` / `equalto` / `internalid anyof` value to `isempty` before the
+                  search. On `restletVersion: suiteapp2.0` that search is not treated as
+                  "no match": it can return existing records, and `addupdate` then
+                  updates one of them — an unrelated record receives the mapping (seen
+                  in production as `cant_modify_sub` on a customer the record never
+                  named). SuiteBundle and SuiteApp 1.0 discard a blank `internalid`
+                  match and create. Design so the operational lookup never renders
+                  empty: key it on a value every record carries (the source id stored
+                  as `externalid`), or route records without a destination id to a
+                  separate `add` import.
                 - |-
                   ## Body-level only
 

package/package.json

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

package/schemas.json

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "0d0dde72",
+		"iasCommit": "2882b3ab",
 		"generatedAt": "2026-10-20"
 	},
 	"roots": {