npm - @celigo/api-specs - Versions diffs - 0.2.112 → 0.2.113 - Mend

@celigo/api-specs 0.2.112 → 0.2.113

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (4) hide show

package/dist/import.yml CHANGED Viewed

@@ -3802,23 +3802,25 @@ components:
             - |-
               Two ways to specify the lookup, picked per import:
+              - **Expression form** — the default choice: set `expression` to a
+                NetSuite search-expression literal (the canonical patterns are on
+                the `expression` field — `["internalid","is","{{{id}}}"]` for a
+                record that carries the internal id, `externalid` and `cust*_*`
+                variants, `anyof` for multi-match, AND/OR compounds).  When
+                `expression` is set, `searchField` / `operator` / `extract` are
+                ignored.
               - **Simple form** — set `searchField` + `operator` (+ optional
-                `extract`).  Use for single-criterion lookups against a built-in
-                NetSuite field.  The platform builds the equivalent search
-                expression for you at runtime.
-              - **Expression form** — set `expression` to a NetSuite search-
-                expression literal.  Use for compound (AND/OR) lookups, custom-
-                record-field lookups (`custbody_*` / `custrecord_*` /
-                `custentity_*`), and the `anyof` operator that the simple form
-                doesn't cover.  When `expression` is set, `searchField` /
-                `operator` / `extract` are ignored.  The expression form is the
-                common pattern in practice.
+                `extract`) for a single-criterion lookup against a built-in
+                NetSuite field; the platform builds the equivalent search
+                expression at runtime.  For the internal id itself the expression
+                form above is the preferred path, and `anyof` is available only
+                through `expression`.
             - |-
               The lookup result is what identifies the target record; on `update` a source
               field mapped to `internalid` is overridden by it. When the incoming record
-              already carries the NetSuite internal ID, point the lookup at that field
-              (simple form with `extract`, or an expression on the id field) rather than
-              removing the lookup.
+              already carries the NetSuite internal ID, point the lookup at that field with
+              the expression form — `["internalid","is","{{{id}}}"]` — rather than removing
+              the lookup.
           properties:
             extract:
               type: string
@@ -3827,7 +3829,7 @@ components:
                 - |-
                   Path on the incoming source record (NOT the post-mapped record) whose value drives the lookup.
                   Used with the simple form (`searchField` + `operator`).
-                  Common values: `"internalId"`, `"externalId"`, `"id"`.
+                  Common values: `"externalId"`, `"id"`.
                   Ignored when `expression` is set.
               examples:
                 - externalId
@@ -3837,8 +3839,9 @@ components:
               x-celigo-ai-guidance:
                 - |-
                   NetSuite field the simple-form lookup queries against.
-                  Common values: `"externalId"`, `"internalId"`, `"email"`, `"tranId"`,
-                  `"name"`.
+                  Common values: `"externalId"`, `"email"`, `"tranId"`, `"name"`.
+                  Matching on the record's internal id is the expression form —
+                  `["internalid","is","{{{id}}}"]` — not a `searchField`.
                   Ignored when `expression` is set.
               examples:
                 - externalId
@@ -3848,9 +3851,9 @@ components:
               x-celigo-ai-guidance:
                 - |-
                   Comparison operator for the simple-form lookup.
-                  Common values: `"is"` (exact match),
-                  `"anyof"` (matches any of the given internal-id values), `"contains"`,
-                  `"startswith"`, `"equalto"`.
+                  Common values: `"is"` (exact match), `"contains"`, `"startswith"`,
+                  `"equalto"`.  Multi-match (`anyof`) is available only through
+                  `expression` (`["internalid","anyof","{{{id}}}"]`).
                   Ignored when `expression` is set.
             expression:
               type: string

package/dist/tool.yml CHANGED Viewed

@@ -15381,23 +15381,25 @@ components:
             - |-
               Two ways to specify the lookup, picked per import:
+              - **Expression form** — the default choice: set `expression` to a
+                NetSuite search-expression literal (the canonical patterns are on
+                the `expression` field — `["internalid","is","{{{id}}}"]` for a
+                record that carries the internal id, `externalid` and `cust*_*`
+                variants, `anyof` for multi-match, AND/OR compounds).  When
+                `expression` is set, `searchField` / `operator` / `extract` are
+                ignored.
               - **Simple form** — set `searchField` + `operator` (+ optional
-                `extract`).  Use for single-criterion lookups against a built-in
-                NetSuite field.  The platform builds the equivalent search
-                expression for you at runtime.
-              - **Expression form** — set `expression` to a NetSuite search-
-                expression literal.  Use for compound (AND/OR) lookups, custom-
-                record-field lookups (`custbody_*` / `custrecord_*` /
-                `custentity_*`), and the `anyof` operator that the simple form
-                doesn't cover.  When `expression` is set, `searchField` /
-                `operator` / `extract` are ignored.  The expression form is the
-                common pattern in practice.
+                `extract`) for a single-criterion lookup against a built-in
+                NetSuite field; the platform builds the equivalent search
+                expression at runtime.  For the internal id itself the expression
+                form above is the preferred path, and `anyof` is available only
+                through `expression`.
             - |-
               The lookup result is what identifies the target record; on `update` a source
               field mapped to `internalid` is overridden by it. When the incoming record
-              already carries the NetSuite internal ID, point the lookup at that field
-              (simple form with `extract`, or an expression on the id field) rather than
-              removing the lookup.
+              already carries the NetSuite internal ID, point the lookup at that field with
+              the expression form — `["internalid","is","{{{id}}}"]` — rather than removing
+              the lookup.
           properties:
             extract:
               type: string
@@ -15406,7 +15408,7 @@ components:
                 - |-
                   Path on the incoming source record (NOT the post-mapped record) whose value drives the lookup.
                   Used with the simple form (`searchField` + `operator`).
-                  Common values: `"internalId"`, `"externalId"`, `"id"`.
+                  Common values: `"externalId"`, `"id"`.
                   Ignored when `expression` is set.
               examples:
                 - externalId
@@ -15416,8 +15418,9 @@ components:
               x-celigo-ai-guidance:
                 - |-
                   NetSuite field the simple-form lookup queries against.
-                  Common values: `"externalId"`, `"internalId"`, `"email"`, `"tranId"`,
-                  `"name"`.
+                  Common values: `"externalId"`, `"email"`, `"tranId"`, `"name"`.
+                  Matching on the record's internal id is the expression form —
+                  `["internalid","is","{{{id}}}"]` — not a `searchField`.
                   Ignored when `expression` is set.
               examples:
                 - externalId
@@ -15427,9 +15430,9 @@ components:
               x-celigo-ai-guidance:
                 - |-
                   Comparison operator for the simple-form lookup.
-                  Common values: `"is"` (exact match),
-                  `"anyof"` (matches any of the given internal-id values), `"contains"`,
-                  `"startswith"`, `"equalto"`.
+                  Common values: `"is"` (exact match), `"contains"`, `"startswith"`,
+                  `"equalto"`.  Multi-match (`anyof`) is available only through
+                  `expression` (`["internalid","anyof","{{{id}}}"]`).
                   Ignored when `expression` is set.
             expression:
               type: string

package/package.json CHANGED Viewed

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

package/schemas.json CHANGED Viewed

@@ -1,7 +1,7 @@
 {
 	"provenance": {
 		"repo": "celigo/integrator-api-specs",
-		"iasCommit": "290f7bc1",
+		"iasCommit": "af39c6bc",
 		"generatedAt": "2026-10-15"
 	},
 	"roots": {