npm - @celigo/api-specs - Versions diffs - 0.2.234 → 0.2.236 - Mend

@celigo/api-specs 0.2.234 → 0.2.236

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 (8) hide show

package/dist/ai-agent.yml CHANGED Viewed

@@ -5514,11 +5514,14 @@ components:
               - 'null'
             description: |
               Default value to use when the source value is not found in the lookup map.
-              The platform stores `null` here when no default is configured.
+              `""`, `null` and an absent key are three stored states — the mapper's
+              *Use empty string as default value*, *Use null as default value* and
+              *Do nothing* — kept apart on save and read back as written; on an allowed
+              miss of a static map they write `""`, write `null`, or leave the field out.
               This value is used as a fallback when:
               1. The source value doesn't match any key in the map
-              2. allowFailures is true or omitted
+              2. allowFailures is true, or omitted on a static map
               Setting an appropriate default helps prevent flow failures due to unexpected
               values and provides predictable behavior for edge cases.
@@ -5528,10 +5531,12 @@ components:
               - Original value indicators: "{Original Value}", "No mapping found"
               - Neutral values: "Other", "N/A", "Miscellaneous"
-              A save refuses a default together with an explicit `allowFailures: false`
-              (422 `Lookups with default set can not have allowFailures explicitly set to
-              false.`): a lookup either fails a miss (`allowFailures: false`, no default) or
-              falls back to its default.
+              A save refuses a non-empty default together with an explicit
+              `allowFailures: false` (422 `Lookups with default set can not have
+              allowFailures explicitly set to false.`). `allowFailures: false` fails the
+              miss even when `""` or `null` is stored (a static map: `lookup_error`,
+              nothing written); the default is used only on an allowed miss
+              (`allowFailures` true, or omitted on a static map).
             examples:
               - Unknown
               - Other
@@ -5539,8 +5544,8 @@ components:
               - Unmapped Value
               - '{Original Value}'
             x-celigo-ai-guidance:
-              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
-              - A default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
+              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a non-empty default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss of a static map writes `""`. On an update, carry a stored `""` or `null` through unchanged: it is the user''s choice, and on an allowed miss of a static map dropping it turns a written `""` / `null` into an omitted field.'
+              - On an allowed miss (`allowFailures` true, or omitted on a static map) a default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
           allowFailures:
             type:
               - boolean
@@ -5571,9 +5576,11 @@ components:
               - All possible source values are known and controlled
               - Missing mappings indicate serious data problems that should be addressed
-              A default raises no error: records that miss go out with the default value and
-              nothing reports them. Use true only when that fallback is acceptable at the
-              destination, and set false explicitly when a missing value must stop the record.
+              On an allowed miss (`allowFailures` true, or omitted on a static map) a default
+              raises no error: records that miss go out with the default value and nothing
+              reports them. Use true only when that fallback is acceptable at the destination,
+              and set false explicitly when a missing value must stop the record — on a static
+              map, false fails the miss even when `""` or `null` is stored as the default.
             examples:
               - true
               - false

package/dist/api.yml CHANGED Viewed

@@ -5006,11 +5006,14 @@ components:
               - 'null'
             description: |
               Default value to use when the source value is not found in the lookup map.
-              The platform stores `null` here when no default is configured.
+              `""`, `null` and an absent key are three stored states — the mapper's
+              *Use empty string as default value*, *Use null as default value* and
+              *Do nothing* — kept apart on save and read back as written; on an allowed
+              miss of a static map they write `""`, write `null`, or leave the field out.
               This value is used as a fallback when:
               1. The source value doesn't match any key in the map
-              2. allowFailures is true or omitted
+              2. allowFailures is true, or omitted on a static map
               Setting an appropriate default helps prevent flow failures due to unexpected
               values and provides predictable behavior for edge cases.
@@ -5020,10 +5023,12 @@ components:
               - Original value indicators: "{Original Value}", "No mapping found"
               - Neutral values: "Other", "N/A", "Miscellaneous"
-              A save refuses a default together with an explicit `allowFailures: false`
-              (422 `Lookups with default set can not have allowFailures explicitly set to
-              false.`): a lookup either fails a miss (`allowFailures: false`, no default) or
-              falls back to its default.
+              A save refuses a non-empty default together with an explicit
+              `allowFailures: false` (422 `Lookups with default set can not have
+              allowFailures explicitly set to false.`). `allowFailures: false` fails the
+              miss even when `""` or `null` is stored (a static map: `lookup_error`,
+              nothing written); the default is used only on an allowed miss
+              (`allowFailures` true, or omitted on a static map).
             examples:
               - Unknown
               - Other
@@ -5031,8 +5036,8 @@ components:
               - Unmapped Value
               - '{Original Value}'
             x-celigo-ai-guidance:
-              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
-              - A default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
+              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a non-empty default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss of a static map writes `""`. On an update, carry a stored `""` or `null` through unchanged: it is the user''s choice, and on an allowed miss of a static map dropping it turns a written `""` / `null` into an omitted field.'
+              - On an allowed miss (`allowFailures` true, or omitted on a static map) a default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
           allowFailures:
             type:
               - boolean
@@ -5063,9 +5068,11 @@ components:
               - All possible source values are known and controlled
               - Missing mappings indicate serious data problems that should be addressed
-              A default raises no error: records that miss go out with the default value and
-              nothing reports them. Use true only when that fallback is acceptable at the
-              destination, and set false explicitly when a missing value must stop the record.
+              On an allowed miss (`allowFailures` true, or omitted on a static map) a default
+              raises no error: records that miss go out with the default value and nothing
+              reports them. Use true only when that fallback is acceptable at the destination,
+              and set false explicitly when a missing value must stop the record — on a static
+              map, false fails the miss even when `""` or `null` is stored as the default.
             examples:
               - true
               - false

package/dist/asynchelper.yml CHANGED Viewed

@@ -2901,11 +2901,14 @@ components:
               - 'null'
             description: |
               Default value to use when the source value is not found in the lookup map.
-              The platform stores `null` here when no default is configured.
+              `""`, `null` and an absent key are three stored states — the mapper's
+              *Use empty string as default value*, *Use null as default value* and
+              *Do nothing* — kept apart on save and read back as written; on an allowed
+              miss of a static map they write `""`, write `null`, or leave the field out.
               This value is used as a fallback when:
               1. The source value doesn't match any key in the map
-              2. allowFailures is true or omitted
+              2. allowFailures is true, or omitted on a static map
               Setting an appropriate default helps prevent flow failures due to unexpected
               values and provides predictable behavior for edge cases.
@@ -2915,10 +2918,12 @@ components:
               - Original value indicators: "{Original Value}", "No mapping found"
               - Neutral values: "Other", "N/A", "Miscellaneous"
-              A save refuses a default together with an explicit `allowFailures: false`
-              (422 `Lookups with default set can not have allowFailures explicitly set to
-              false.`): a lookup either fails a miss (`allowFailures: false`, no default) or
-              falls back to its default.
+              A save refuses a non-empty default together with an explicit
+              `allowFailures: false` (422 `Lookups with default set can not have
+              allowFailures explicitly set to false.`). `allowFailures: false` fails the
+              miss even when `""` or `null` is stored (a static map: `lookup_error`,
+              nothing written); the default is used only on an allowed miss
+              (`allowFailures` true, or omitted on a static map).
             examples:
               - Unknown
               - Other
@@ -2926,8 +2931,8 @@ components:
               - Unmapped Value
               - '{Original Value}'
             x-celigo-ai-guidance:
-              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
-              - A default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
+              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a non-empty default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss of a static map writes `""`. On an update, carry a stored `""` or `null` through unchanged: it is the user''s choice, and on an allowed miss of a static map dropping it turns a written `""` / `null` into an omitted field.'
+              - On an allowed miss (`allowFailures` true, or omitted on a static map) a default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
           allowFailures:
             type:
               - boolean
@@ -2958,9 +2963,11 @@ components:
               - All possible source values are known and controlled
               - Missing mappings indicate serious data problems that should be addressed
-              A default raises no error: records that miss go out with the default value and
-              nothing reports them. Use true only when that fallback is acceptable at the
-              destination, and set false explicitly when a missing value must stop the record.
+              On an allowed miss (`allowFailures` true, or omitted on a static map) a default
+              raises no error: records that miss go out with the default value and nothing
+              reports them. Use true only when that fallback is acceptable at the destination,
+              and set false explicitly when a missing value must stop the record — on a static
+              map, false fails the miss even when `""` or `null` is stored as the default.
             examples:
               - true
               - false

package/dist/export.yml CHANGED Viewed

@@ -15218,11 +15218,14 @@ components:
               - 'null'
             description: |
               Default value to use when the source value is not found in the lookup map.
-              The platform stores `null` here when no default is configured.
+              `""`, `null` and an absent key are three stored states — the mapper's
+              *Use empty string as default value*, *Use null as default value* and
+              *Do nothing* — kept apart on save and read back as written; on an allowed
+              miss of a static map they write `""`, write `null`, or leave the field out.
               This value is used as a fallback when:
               1. The source value doesn't match any key in the map
-              2. allowFailures is true or omitted
+              2. allowFailures is true, or omitted on a static map
               Setting an appropriate default helps prevent flow failures due to unexpected
               values and provides predictable behavior for edge cases.
@@ -15232,10 +15235,12 @@ components:
               - Original value indicators: "{Original Value}", "No mapping found"
               - Neutral values: "Other", "N/A", "Miscellaneous"
-              A save refuses a default together with an explicit `allowFailures: false`
-              (422 `Lookups with default set can not have allowFailures explicitly set to
-              false.`): a lookup either fails a miss (`allowFailures: false`, no default) or
-              falls back to its default.
+              A save refuses a non-empty default together with an explicit
+              `allowFailures: false` (422 `Lookups with default set can not have
+              allowFailures explicitly set to false.`). `allowFailures: false` fails the
+              miss even when `""` or `null` is stored (a static map: `lookup_error`,
+              nothing written); the default is used only on an allowed miss
+              (`allowFailures` true, or omitted on a static map).
             examples:
               - Unknown
               - Other
@@ -15243,8 +15248,8 @@ components:
               - Unmapped Value
               - '{Original Value}'
             x-celigo-ai-guidance:
-              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
-              - A default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
+              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a non-empty default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss of a static map writes `""`. On an update, carry a stored `""` or `null` through unchanged: it is the user''s choice, and on an allowed miss of a static map dropping it turns a written `""` / `null` into an omitted field.'
+              - On an allowed miss (`allowFailures` true, or omitted on a static map) a default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
           allowFailures:
             type:
               - boolean
@@ -15275,9 +15280,11 @@ components:
               - All possible source values are known and controlled
               - Missing mappings indicate serious data problems that should be addressed
-              A default raises no error: records that miss go out with the default value and
-              nothing reports them. Use true only when that fallback is acceptable at the
-              destination, and set false explicitly when a missing value must stop the record.
+              On an allowed miss (`allowFailures` true, or omitted on a static map) a default
+              raises no error: records that miss go out with the default value and nothing
+              reports them. Use true only when that fallback is acceptable at the destination,
+              and set false explicitly when a missing value must stop the record — on a static
+              map, false fails the miss even when `""` or `null` is stored as the default.
             examples:
               - true
               - false
@@ -16884,10 +16891,18 @@ components:
             `webhook` object when `type` is `webhook`); an HTTP or SQL `delta` export saves without a
             `delta` object because its request carries `{{lastExportDateTime}}`, though
             `delta.startDate` sets its first window. It still needs `type: delta`: on an export
-            with no `type`, `{{lastExportDateTime}}` and `{{currentExportDateTime}}` render
-            empty on every run, so a request that carries them goes out with blank values each time
-            (live-verified 2026-10-22). Use `blob` only to transfer raw files without parsing their
-            contents.
+            with no `type` (or `all`, or `test`), `{{lastExportDateTime}}` and `{{currentExportDateTime}}` render
+            empty on every run, so a request that carries them bare goes out with blank values each
+            time, `dateFormat` on one renders the run's current time (the request asks for changes
+            since now), and `dateAdd` on one fails the whole render — on an HTTP export's body or
+            relative URI the run records `handlebars_template_parse_error`, "Failed to generate request
+            body (or url) from template … Details: Invalid time value" — before anything is sent
+            (live-verified 2026-10-22 and 2026-11-04). When incremental reads are intended, restoring
+            `type: delta` (with `delta.startDate` for the first window) makes the variables resolve;
+            when reading everything is intended, change the template — drop the variable or guard it
+            with `{{#if lastExportDateTime}}…{{else}}fallback{{/if}}`, whose else branch (a literal, in
+            practice a fixed start date) renders on an export with no `type`, `type: all` or
+            `type: test`. Use `blob` only to transfer raw files without parsing their contents.
           x-celigo-ai-guidance:
             - |-
               ## HOW TO PICK THE TYPE VALUE

package/dist/import.yml CHANGED Viewed

@@ -2898,15 +2898,20 @@ components:
                 description: |
                   Value written when the lookup finds no match and the miss is
                   allowed (``allowFailures`` true, or omitted on a static
-                  ``map``). A save refuses a ``default`` together with an
-                  explicit ``allowFailures: false`` (422 "Lookups with default
-                  set can not have allowFailures explicitly set to false."), so
-                  a lookup either fails a miss (``allowFailures: false``, no
-                  default) or falls back to its default. Stored as null when no
-                  fallback is configured.
+                  ``map``). A save refuses a non-empty ``default`` together with
+                  an explicit ``allowFailures: false`` (422 "Lookups with default
+                  set can not have allowFailures explicitly set to false.").
+                  ``allowFailures: false`` fails the miss even when ``""`` or
+                  ``null`` is stored (a static map: ``lookup_error``, nothing
+                  written); the default is used only on an allowed miss. ``""``,
+                  ``null`` and an absent key are three stored states — the
+                  mapper's *Use empty string as default value*, *Use null as
+                  default value* and *Do nothing* — kept apart on save and read
+                  back as written; on an allowed miss of a static map they write
+                  ``""``, write ``null``, or leave the field out.
                 x-celigo-ai-guidance:
-                  - 'Omit this field entirely when no fallback value is intended. An empty string is a value, not "no default": the save accepts `default: ""`, and a miss the lookup lets through writes `""`.'
-                  - 'A default raises no error: every unmatched value goes out as the default with a 200. Set one only when a single fallback is right for every value the lookup can''t match; when a miss must stop the record, set allowFailures: false and leave the default out. An ambiguous answer (two or more matches) doesn''t use the default either: see useDefaultOnMultipleMatches.'
+                  - 'Omit this field entirely when no fallback value is intended. An empty string is a value, not "no default": the save accepts `default: ""`, and an allowed miss of a static map writes `""`. On an update, carry a stored `""` or `null` through unchanged: it is the user''s choice, and on an allowed miss of a static map dropping it turns a written `""` / `null` into an omitted field.'
+                  - 'On an allowed miss (allowFailures true, or omitted on a static map) a default raises no error: every unmatched value goes out as the default with a 200. Set one only when a single fallback is right for every value the lookup can''t match; when a miss must stop the record, set allowFailures: false — a stored `""` or `null` may stay, a non-empty default cannot. An ambiguous answer (two or more matches) doesn''t use the default either: see useDefaultOnMultipleMatches.'
               allowFailures:
                 type:
                   - boolean
@@ -3616,7 +3621,11 @@ components:
                 type:
                   - string
                   - 'null'
-                description: Fallback value returned when the lookup finds no match. Used together with `allowFailures`. Stored as `null` when not configured.
+                description: |-
+                  Fallback value returned when the lookup finds no match. Used together with `allowFailures`.
+                  `""`, `null` and an absent key are three stored states — the mapper's *Use empty string
+                  as default value*, *Use null as default value* and *Do nothing* — saved and read back as
+                  written, in both `lookups` and `netsuite.lookups`.
               allowFailures:
                 type: boolean
                 description: When true, an unmatched lookup falls back to `default` and processing continues; when false, an unmatched lookup fails the record.
@@ -5016,9 +5025,14 @@ components:
                   - string
                   - 'null'
                 description: |-
-                  Value returned when the search matches no records. When
-                  omitted and `allowFailures` is false, an unmatched lookup
-                  halts the record. May be stored as null (no default).
+                  Value returned when the search matches no records and the
+                  miss is allowed. `""`, `null` and an absent key are three
+                  stored states — the mapper's *Use empty string as default
+                  value*, *Use null as default value* and *Do nothing* — saved
+                  and read back as written, in both `lookups` and
+                  `netsuite_da.lookups`; a save with no `default` key stores
+                  none. When `allowFailures` is false an unmatched lookup halts
+                  the record whatever is stored here.
           description: |-
             Lookup definitions that resolve reference values from NetSuite.
             Referenced by name from field mappings via `lookupName` and from
@@ -5346,11 +5360,14 @@ components:
               - 'null'
             description: |
               Default value to use when the source value is not found in the lookup map.
-              The platform stores `null` here when no default is configured.
+              `""`, `null` and an absent key are three stored states — the mapper's
+              *Use empty string as default value*, *Use null as default value* and
+              *Do nothing* — kept apart on save and read back as written; on an allowed
+              miss of a static map they write `""`, write `null`, or leave the field out.
               This value is used as a fallback when:
               1. The source value doesn't match any key in the map
-              2. allowFailures is true or omitted
+              2. allowFailures is true, or omitted on a static map
               Setting an appropriate default helps prevent flow failures due to unexpected
               values and provides predictable behavior for edge cases.
@@ -5360,10 +5377,12 @@ components:
               - Original value indicators: "{Original Value}", "No mapping found"
               - Neutral values: "Other", "N/A", "Miscellaneous"
-              A save refuses a default together with an explicit `allowFailures: false`
-              (422 `Lookups with default set can not have allowFailures explicitly set to
-              false.`): a lookup either fails a miss (`allowFailures: false`, no default) or
-              falls back to its default.
+              A save refuses a non-empty default together with an explicit
+              `allowFailures: false` (422 `Lookups with default set can not have
+              allowFailures explicitly set to false.`). `allowFailures: false` fails the
+              miss even when `""` or `null` is stored (a static map: `lookup_error`,
+              nothing written); the default is used only on an allowed miss
+              (`allowFailures` true, or omitted on a static map).
             examples:
               - Unknown
               - Other
@@ -5371,8 +5390,8 @@ components:
               - Unmapped Value
               - '{Original Value}'
             x-celigo-ai-guidance:
-              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
-              - A default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
+              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a non-empty default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss of a static map writes `""`. On an update, carry a stored `""` or `null` through unchanged: it is the user''s choice, and on an allowed miss of a static map dropping it turns a written `""` / `null` into an omitted field.'
+              - On an allowed miss (`allowFailures` true, or omitted on a static map) a default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
           allowFailures:
             type:
               - boolean
@@ -5403,9 +5422,11 @@ components:
               - All possible source values are known and controlled
               - Missing mappings indicate serious data problems that should be addressed
-              A default raises no error: records that miss go out with the default value and
-              nothing reports them. Use true only when that fallback is acceptable at the
-              destination, and set false explicitly when a missing value must stop the record.
+              On an allowed miss (`allowFailures` true, or omitted on a static map) a default
+              raises no error: records that miss go out with the default value and nothing
+              reports them. Use true only when that fallback is acceptable at the destination,
+              and set false explicitly when a missing value must stop the record — on a static
+              map, false fails the miss even when `""` or `null` is stored as the default.
             examples:
               - true
               - false
@@ -9377,7 +9398,7 @@ components:
                 type:
                   - string
                   - 'null'
-                description: Value substituted when a source value is not found in map; empty string when omitted. May be stored as null (no default).
+                description: Value substituted when a source value is not found in map and the miss is allowed.
               allowFailures:
                 type: boolean
                 description: When true, a value missing from map does not fail the record and the default (or original value) is used.

package/dist/tool.yml CHANGED Viewed

@@ -6019,11 +6019,14 @@ components:
               - 'null'
             description: |
               Default value to use when the source value is not found in the lookup map.
-              The platform stores `null` here when no default is configured.
+              `""`, `null` and an absent key are three stored states — the mapper's
+              *Use empty string as default value*, *Use null as default value* and
+              *Do nothing* — kept apart on save and read back as written; on an allowed
+              miss of a static map they write `""`, write `null`, or leave the field out.
               This value is used as a fallback when:
               1. The source value doesn't match any key in the map
-              2. allowFailures is true or omitted
+              2. allowFailures is true, or omitted on a static map
               Setting an appropriate default helps prevent flow failures due to unexpected
               values and provides predictable behavior for edge cases.
@@ -6033,10 +6036,12 @@ components:
               - Original value indicators: "{Original Value}", "No mapping found"
               - Neutral values: "Other", "N/A", "Miscellaneous"
-              A save refuses a default together with an explicit `allowFailures: false`
-              (422 `Lookups with default set can not have allowFailures explicitly set to
-              false.`): a lookup either fails a miss (`allowFailures: false`, no default) or
-              falls back to its default.
+              A save refuses a non-empty default together with an explicit
+              `allowFailures: false` (422 `Lookups with default set can not have
+              allowFailures explicitly set to false.`). `allowFailures: false` fails the
+              miss even when `""` or `null` is stored (a static map: `lookup_error`,
+              nothing written); the default is used only on an allowed miss
+              (`allowFailures` true, or omitted on a static map).
             examples:
               - Unknown
               - Other
@@ -6044,8 +6049,8 @@ components:
               - Unmapped Value
               - '{Original Value}'
             x-celigo-ai-guidance:
-              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss writes `""`.'
-              - A default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
+              - 'Omit this field entirely when no fallback value is intended: a miss the lookup lets through then leaves the mapped field out, and `allowFailures: false` (which a save refuses alongside a non-empty default) fails it. An empty string is a value, not "no default" — the save accepts `default: ""`, and an allowed miss of a static map writes `""`. On an update, carry a stored `""` or `null` through unchanged: it is the user''s choice, and on an allowed miss of a static map dropping it turns a written `""` / `null` into an omitted field.'
+              - On an allowed miss (`allowFailures` true, or omitted on a static map) a default sends every unmapped value with no error, so add the missing key to the map when the destination needs the real value; keys match the extracted value exactly (case, spacing and suffixes count), and a save replaces the whole map.
           allowFailures:
             type:
               - boolean
@@ -6076,9 +6081,11 @@ components:
               - All possible source values are known and controlled
               - Missing mappings indicate serious data problems that should be addressed
-              A default raises no error: records that miss go out with the default value and
-              nothing reports them. Use true only when that fallback is acceptable at the
-              destination, and set false explicitly when a missing value must stop the record.
+              On an allowed miss (`allowFailures` true, or omitted on a static map) a default
+              raises no error: records that miss go out with the default value and nothing
+              reports them. Use true only when that fallback is acceptable at the destination,
+              and set false explicitly when a missing value must stop the record — on a static
+              map, false fails the miss even when `""` or `null` is stored as the default.
             examples:
               - true
               - false
@@ -15251,15 +15258,20 @@ components:
                 description: |
                   Value written when the lookup finds no match and the miss is
                   allowed (``allowFailures`` true, or omitted on a static
-                  ``map``). A save refuses a ``default`` together with an
-                  explicit ``allowFailures: false`` (422 "Lookups with default
-                  set can not have allowFailures explicitly set to false."), so
-                  a lookup either fails a miss (``allowFailures: false``, no
-                  default) or falls back to its default. Stored as null when no
-                  fallback is configured.
+                  ``map``). A save refuses a non-empty ``default`` together with
+                  an explicit ``allowFailures: false`` (422 "Lookups with default
+                  set can not have allowFailures explicitly set to false.").
+                  ``allowFailures: false`` fails the miss even when ``""`` or
+                  ``null`` is stored (a static map: ``lookup_error``, nothing
+                  written); the default is used only on an allowed miss. ``""``,
+                  ``null`` and an absent key are three stored states — the
+                  mapper's *Use empty string as default value*, *Use null as
+                  default value* and *Do nothing* — kept apart on save and read
+                  back as written; on an allowed miss of a static map they write
+                  ``""``, write ``null``, or leave the field out.
                 x-celigo-ai-guidance:
-                  - 'Omit this field entirely when no fallback value is intended. An empty string is a value, not "no default": the save accepts `default: ""`, and a miss the lookup lets through writes `""`.'
-                  - 'A default raises no error: every unmatched value goes out as the default with a 200. Set one only when a single fallback is right for every value the lookup can''t match; when a miss must stop the record, set allowFailures: false and leave the default out. An ambiguous answer (two or more matches) doesn''t use the default either: see useDefaultOnMultipleMatches.'
+                  - 'Omit this field entirely when no fallback value is intended. An empty string is a value, not "no default": the save accepts `default: ""`, and an allowed miss of a static map writes `""`. On an update, carry a stored `""` or `null` through unchanged: it is the user''s choice, and on an allowed miss of a static map dropping it turns a written `""` / `null` into an omitted field.'
+                  - 'On an allowed miss (allowFailures true, or omitted on a static map) a default raises no error: every unmatched value goes out as the default with a 200. Set one only when a single fallback is right for every value the lookup can''t match; when a miss must stop the record, set allowFailures: false — a stored `""` or `null` may stay, a non-empty default cannot. An ambiguous answer (two or more matches) doesn''t use the default either: see useDefaultOnMultipleMatches.'
               allowFailures:
                 type:
                   - boolean
@@ -15969,7 +15981,11 @@ components:
                 type:
                   - string
                   - 'null'
-                description: Fallback value returned when the lookup finds no match. Used together with `allowFailures`. Stored as `null` when not configured.
+                description: |-
+                  Fallback value returned when the lookup finds no match. Used together with `allowFailures`.
+                  `""`, `null` and an absent key are three stored states — the mapper's *Use empty string
+                  as default value*, *Use null as default value* and *Do nothing* — saved and read back as
+                  written, in both `lookups` and `netsuite.lookups`.
               allowFailures:
                 type: boolean
                 description: When true, an unmatched lookup falls back to `default` and processing continues; when false, an unmatched lookup fails the record.
@@ -17369,9 +17385,14 @@ components:
                   - string
                   - 'null'
                 description: |-
-                  Value returned when the search matches no records. When
-                  omitted and `allowFailures` is false, an unmatched lookup
-                  halts the record. May be stored as null (no default).
+                  Value returned when the search matches no records and the
+                  miss is allowed. `""`, `null` and an absent key are three
+                  stored states — the mapper's *Use empty string as default
+                  value*, *Use null as default value* and *Do nothing* — saved
+                  and read back as written, in both `lookups` and
+                  `netsuite_da.lookups`; a save with no `default` key stores
+                  none. When `allowFailures` is false an unmatched lookup halts
+                  the record whatever is stored here.
           description: |-
             Lookup definitions that resolve reference values from NetSuite.
             Referenced by name from field mappings via `lookupName` and from
@@ -21451,7 +21472,7 @@ components:
                 type:
                   - string
                   - 'null'
-                description: Value substituted when a source value is not found in map; empty string when omitted. May be stored as null (no default).
+                description: Value substituted when a source value is not found in map and the miss is allowed.
               allowFailures:
                 type: boolean
                 description: When true, a value missing from map does not fail the record and the default (or original value) is used.
@@ -39194,10 +39215,18 @@ components:
             `webhook` object when `type` is `webhook`); an HTTP or SQL `delta` export saves without a
             `delta` object because its request carries `{{lastExportDateTime}}`, though
             `delta.startDate` sets its first window. It still needs `type: delta`: on an export
-            with no `type`, `{{lastExportDateTime}}` and `{{currentExportDateTime}}` render
-            empty on every run, so a request that carries them goes out with blank values each time
-            (live-verified 2026-10-22). Use `blob` only to transfer raw files without parsing their
-            contents.
+            with no `type` (or `all`, or `test`), `{{lastExportDateTime}}` and `{{currentExportDateTime}}` render
+            empty on every run, so a request that carries them bare goes out with blank values each
+            time, `dateFormat` on one renders the run's current time (the request asks for changes
+            since now), and `dateAdd` on one fails the whole render — on an HTTP export's body or
+            relative URI the run records `handlebars_template_parse_error`, "Failed to generate request
+            body (or url) from template … Details: Invalid time value" — before anything is sent
+            (live-verified 2026-10-22 and 2026-11-04). When incremental reads are intended, restoring
+            `type: delta` (with `delta.startDate` for the first window) makes the variables resolve;
+            when reading everything is intended, change the template — drop the variable or guard it
+            with `{{#if lastExportDateTime}}…{{else}}fallback{{/if}}`, whose else branch (a literal, in
+            practice a fixed start date) renders on an export with no `type`, `type: all` or
+            `type: test`. Use `blob` only to transfer raw files without parsing their contents.
           x-celigo-ai-guidance:
             - |-
               ## HOW TO PICK THE TYPE VALUE

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@celigo/api-specs",
-  "version": "0.2.234",
+  "version": "0.2.236",
   "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": "afd36585",
+		"iasCommit": "0e0f4656",
 		"generatedAt": "2026-11-04"
 	},
 	"roots": {