@celigo/api-specs 0.2.106 → 0.2.107

package/dist/export.yml

@@ -10775,6 +10775,12 @@ components:
                       - F
                       - - PurchOrd
                     x-celigo-ai-guidance:
+                      - |-
+                        The incoming record is the Handlebars root here: write `{{poNumber}}`, not
+                        `{{record.poNumber}}`. The Flow Builder's step preview rejects the
+                        `record.`-rooted form with `handlebars_template_parse_error` ("poNumber" not
+                        defined in undefined) while a flow run still renders it — write the bare path
+                        so the criterion can be step-previewed.
                       - |-
                         A Handlebars path the incoming record does not carry fails the render with
                         `handlebars_template_parse_error` ("Failed to generate criteria.N.searchValue

package/dist/import.yml

@@ -3787,6 +3787,12 @@ components:
           description: |
             Number of records to process per batch. Controls how many records are sent
             to NetSuite in a single API call. Typical values: 50-200.
+          x-celigo-ai-guidance:
+            - |-
+              Batching applies to the record writes. The `internalIdLookup` searches for a
+              page of records are issued ahead of the writes and independently of `batchSize`,
+              so `batchSize: 1` does not make the existing-record lookup run one record at a
+              time.
         internalIdLookup:
           type: object
           description: |-
@@ -3805,11 +3811,14 @@ components:
                 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.
-            - |-
-              Production usage:
-              `expression` is set on ~99.6% of active `internalIdLookup` blocks (55K imports),
-              so the expression form is the dominant pattern in the field.
+                `operator` / `extract` are ignored.  The expression form is the
+                common pattern in practice.
+            - |-
+              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.
           properties:
             extract:
               type: string

package/dist/tool.yml

@@ -15360,6 +15360,12 @@ components:
           description: |
             Number of records to process per batch. Controls how many records are sent
             to NetSuite in a single API call. Typical values: 50-200.
+          x-celigo-ai-guidance:
+            - |-
+              Batching applies to the record writes. The `internalIdLookup` searches for a
+              page of records are issued ahead of the writes and independently of `batchSize`,
+              so `batchSize: 1` does not make the existing-record lookup run one record at a
+              time.
         internalIdLookup:
           type: object
           description: |-
@@ -15378,11 +15384,14 @@ components:
                 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.
-            - |-
-              Production usage:
-              `expression` is set on ~99.6% of active `internalIdLookup` blocks (55K imports),
-              so the expression form is the dominant pattern in the field.
+                `operator` / `extract` are ignored.  The expression form is the
+                common pattern in practice.
+            - |-
+              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.
           properties:
             extract:
               type: string
@@ -34865,6 +34874,12 @@ components:
                       - F
                       - - PurchOrd
                     x-celigo-ai-guidance:
+                      - |-
+                        The incoming record is the Handlebars root here: write `{{poNumber}}`, not
+                        `{{record.poNumber}}`. The Flow Builder's step preview rejects the
+                        `record.`-rooted form with `handlebars_template_parse_error` ("poNumber" not
+                        defined in undefined) while a flow run still renders it — write the bare path
+                        so the criterion can be step-previewed.
                       - |-
                         A Handlebars path the incoming record does not carry fails the render with
                         `handlebars_template_parse_error` ("Failed to generate criteria.N.searchValue

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.106",
+  "version": "0.2.107",
   "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": "2ab2e845",
-		"generatedAt": "2026-10-13"
+		"iasCommit": "c1ef5efe",
+		"generatedAt": "2026-10-14"
 	},
 	"roots": {
 		"aiagent": 133,