@celigo/api-specs 0.2.212 → 0.2.213

package/dist/import.yml

@@ -4177,8 +4177,26 @@ components:
                     type: string
                     description: |
                       The NetSuite field ID to write the value to (e.g., "companyname", "email", "subsidiary").
+                      Besides field ids it includes Celigo's control rows, which change how the record is
+                      written instead of setting a field — `celigo_recordmode_dynamic` (NetSuite record
+                      mode), `celigo_nlobjTransformId` with `celigo_nlobjTransformType` (create by
+                      transforming the source transaction, "Created From"), `celigo_replaceAllLines_<sublist id>`
+                      (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).
                     examples:
                       - companyname
+                    x-celigo-ai-guidance:
+                      - |-
+                        `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,
+                        where NetSuite documents that body fields and sublist lines are sourced, calculated
+                        and validated as each value is set, in UI order — one field can source or overwrite
+                        another, so mapping-row order matters, and a field no mapping row sets can arrive
+                        populated by NetSuite's own sourcing. Without the row the record is written in
+                        NetSuite's default standard mode, where sourcing of empty dependent fields at save
+                        depends on the SuiteScript save option `enableSourcing` (default false); whether
+                        the SuiteApp passes it is not documented.
                   hardCodedValue:
                     type: string
                     description: |

package/dist/tool.yml

@@ -16423,8 +16423,26 @@ components:
                     type: string
                     description: |
                       The NetSuite field ID to write the value to (e.g., "companyname", "email", "subsidiary").
+                      Besides field ids it includes Celigo's control rows, which change how the record is
+                      written instead of setting a field — `celigo_recordmode_dynamic` (NetSuite record
+                      mode), `celigo_nlobjTransformId` with `celigo_nlobjTransformType` (create by
+                      transforming the source transaction, "Created From"), `celigo_replaceAllLines_<sublist id>`
+                      (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).
                     examples:
                       - companyname
+                    x-celigo-ai-guidance:
+                      - |-
+                        `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,
+                        where NetSuite documents that body fields and sublist lines are sourced, calculated
+                        and validated as each value is set, in UI order — one field can source or overwrite
+                        another, so mapping-row order matters, and a field no mapping row sets can arrive
+                        populated by NetSuite's own sourcing. Without the row the record is written in
+                        NetSuite's default standard mode, where sourcing of empty dependent fields at save
+                        depends on the SuiteScript save option `enableSourcing` (default false); whether
+                        the SuiteApp passes it is not documented.
                   hardCodedValue:
                     type: string
                     description: |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.212",
+  "version": "0.2.213",
   "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": "dcc0e0ac",
+		"iasCommit": "2d17b954",
 		"generatedAt": "2026-10-30"
 	},
 	"roots": {