@celigo/api-specs 0.2.210 → 0.2.211
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.
- package/dist/import.yml +45 -15
- package/dist/tool.yml +45 -15
- package/package.json +1 -1
- package/schemas.json +2 -2
package/dist/import.yml
CHANGED
|
@@ -4286,13 +4286,13 @@ components:
|
|
|
4286
4286
|
jsonPath:
|
|
4287
4287
|
type: string
|
|
4288
4288
|
description: |
|
|
4289
|
-
JSONPath
|
|
4290
|
-
data feeding this subrecord. Semantics depend
|
|
4289
|
+
JSONPath from the source record root that selects
|
|
4290
|
+
the data feeding this subrecord. Semantics depend
|
|
4291
4291
|
on placement:
|
|
4292
4292
|
* Line-level (on `lists[].fields[].`
|
|
4293
|
-
`subRecordMapping`) —
|
|
4294
|
-
|
|
4295
|
-
|
|
4293
|
+
`subRecordMapping`) — the array of lines the
|
|
4294
|
+
sublist iterates (`lineItems`); `$` only when
|
|
4295
|
+
each record is itself one line.
|
|
4296
4296
|
* Body-level (on `fields[].subRecordMapping`)
|
|
4297
4297
|
— a path into the source record root.
|
|
4298
4298
|
Defaults to `$`.
|
|
@@ -4484,9 +4484,10 @@ components:
|
|
|
4484
4484
|
type: boolean
|
|
4485
4485
|
description: |-
|
|
4486
4486
|
When true, this field is a key for matching the record's existing sublist lines: a
|
|
4487
|
-
mapped line updates the one existing line whose key fields hold the same values
|
|
4488
|
-
|
|
4489
|
-
|
|
4487
|
+
mapped line updates the one existing line whose key fields hold the same values —
|
|
4488
|
+
every key field must match, so several keys narrow the match. `lists` says which
|
|
4489
|
+
records match lines, the keys used when no field sets `isKey`, and what a line that
|
|
4490
|
+
matches no line, or several, does.
|
|
4490
4491
|
immutable:
|
|
4491
4492
|
type: boolean
|
|
4492
4493
|
description: When true, this field is only set on record creation, not on updates.
|
|
@@ -4565,13 +4566,19 @@ components:
|
|
|
4565
4566
|
jsonPath:
|
|
4566
4567
|
type: string
|
|
4567
4568
|
description: |
|
|
4568
|
-
|
|
4569
|
-
|
|
4570
|
-
subrecord
|
|
4571
|
-
|
|
4572
|
-
|
|
4573
|
-
|
|
4574
|
-
Defaults to `$`.
|
|
4569
|
+
Path from the source record root to the
|
|
4570
|
+
array of lines whose elements feed this
|
|
4571
|
+
subrecord — the same array the sublist
|
|
4572
|
+
iterates (`lineItems`, `items`); the n-th
|
|
4573
|
+
element populates the n-th sublist line.
|
|
4574
|
+
`$` only when each source record is itself
|
|
4575
|
+
one line. Defaults to `$`.
|
|
4576
|
+
x-celigo-ai-guidance:
|
|
4577
|
+
- |-
|
|
4578
|
+
`$` on a record whose lines sit under a field renders no subrecord for any
|
|
4579
|
+
line, and NetSuite rejects the first numbered line with `Please configure the
|
|
4580
|
+
inventory detail in line N of the item list`; name the line array
|
|
4581
|
+
(`lineItems`), never the current-line context.
|
|
4575
4582
|
mapping:
|
|
4576
4583
|
type: object
|
|
4577
4584
|
description: |
|
|
@@ -4682,6 +4689,11 @@ components:
|
|
|
4682
4689
|
with `MULTIPLE_LINES_WITH_SAME_KEYS` ("Multiple lines found with keys item=<value> ..."). A
|
|
4683
4690
|
line that matches none is added as a new line, which an item fulfillment's `item` sublist
|
|
4684
4691
|
refuses with `SSS_INVALID_SUBLIST_OPERATION`: its lines are its order's.
|
|
4692
|
+
|
|
4693
|
+
On a fulfillment created from an order, a kit's lot-, serial- or bin-managed components are
|
|
4694
|
+
lines of their own under the kit's line, each with its own `line` and `orderline` (the
|
|
4695
|
+
component's own order line) and `kitmemberof` holding the kit line's id; the inventory detail
|
|
4696
|
+
belongs on those component lines, and a kit line refuses it.
|
|
4685
4697
|
x-celigo-ai-guidance:
|
|
4686
4698
|
- |-
|
|
4687
4699
|
To make an update replace a sublist's lines, also map the body field
|
|
@@ -4696,6 +4708,24 @@ components:
|
|
|
4696
4708
|
field, or, on a fulfillment, the order line's id mapped to `orderline`. Keying on the item fails
|
|
4697
4709
|
with `MULTIPLE_LINES_WITH_SAME_KEYS` when an order holds the same item on two lines, and records
|
|
4698
4710
|
that already hold repeated lines fail the same way once a key is set.
|
|
4711
|
+
- |-
|
|
4712
|
+
A key field is read from the existing lines, never written, so a read-only field keys as well
|
|
4713
|
+
as a writable one. The mapper's "Items : Line ID" is `line` (the fulfillment's own line number,
|
|
4714
|
+
equal to the order line only on a fresh full transform) and "Items : Line Number" is `linenum`;
|
|
4715
|
+
`orderline` and `kitmemberof` are not in its picker — type `item[*].orderline` /
|
|
4716
|
+
`item[*].kitmemberof` as the destination.
|
|
4717
|
+
- |-
|
|
4718
|
+
Kit components on a fulfillment: the item is the only default key that reaches a component
|
|
4719
|
+
line, so a component two kit lines share fails with `MULTIPLE_LINES_WITH_SAME_KEYS`. Keying the
|
|
4720
|
+
component rows on the KIT's order line (`line` or `orderline`) selects the kit line instead and
|
|
4721
|
+
the save fails with `You cannot create an inventory detail for this item`. When the source
|
|
4722
|
+
carries the kit's order line on its component rows, keep the item as a key and add
|
|
4723
|
+
`item[*].kitmemberof` mapped from that line id as a second key, keep the kit rows in the list
|
|
4724
|
+
(their empty `kitmemberof` matches the kit line) with `item[*].celigo_ignore_current_line_invdetail_subrecord`
|
|
4725
|
+
true so no inventory detail is written on them, and build the inventory detail from each
|
|
4726
|
+
component row's own picks; component rows alone leave every kit line unfulfilled (`You must
|
|
4727
|
+
enter at least one line item for this transaction`). When the source can supply each
|
|
4728
|
+
component line's own order line id, key every row on `orderline` instead.
|
|
4699
4729
|
x-celigo-agent:
|
|
4700
4730
|
- mapping
|
|
4701
4731
|
lookups:
|
package/dist/tool.yml
CHANGED
|
@@ -16495,13 +16495,13 @@ components:
|
|
|
16495
16495
|
jsonPath:
|
|
16496
16496
|
type: string
|
|
16497
16497
|
description: |
|
|
16498
|
-
JSONPath
|
|
16499
|
-
data feeding this subrecord. Semantics depend
|
|
16498
|
+
JSONPath from the source record root that selects
|
|
16499
|
+
the data feeding this subrecord. Semantics depend
|
|
16500
16500
|
on placement:
|
|
16501
16501
|
* Line-level (on `lists[].fields[].`
|
|
16502
|
-
`subRecordMapping`) —
|
|
16503
|
-
|
|
16504
|
-
|
|
16502
|
+
`subRecordMapping`) — the array of lines the
|
|
16503
|
+
sublist iterates (`lineItems`); `$` only when
|
|
16504
|
+
each record is itself one line.
|
|
16505
16505
|
* Body-level (on `fields[].subRecordMapping`)
|
|
16506
16506
|
— a path into the source record root.
|
|
16507
16507
|
Defaults to `$`.
|
|
@@ -16693,9 +16693,10 @@ components:
|
|
|
16693
16693
|
type: boolean
|
|
16694
16694
|
description: |-
|
|
16695
16695
|
When true, this field is a key for matching the record's existing sublist lines: a
|
|
16696
|
-
mapped line updates the one existing line whose key fields hold the same values
|
|
16697
|
-
|
|
16698
|
-
|
|
16696
|
+
mapped line updates the one existing line whose key fields hold the same values —
|
|
16697
|
+
every key field must match, so several keys narrow the match. `lists` says which
|
|
16698
|
+
records match lines, the keys used when no field sets `isKey`, and what a line that
|
|
16699
|
+
matches no line, or several, does.
|
|
16699
16700
|
immutable:
|
|
16700
16701
|
type: boolean
|
|
16701
16702
|
description: When true, this field is only set on record creation, not on updates.
|
|
@@ -16774,13 +16775,19 @@ components:
|
|
|
16774
16775
|
jsonPath:
|
|
16775
16776
|
type: string
|
|
16776
16777
|
description: |
|
|
16777
|
-
|
|
16778
|
-
|
|
16779
|
-
subrecord
|
|
16780
|
-
|
|
16781
|
-
|
|
16782
|
-
|
|
16783
|
-
Defaults to `$`.
|
|
16778
|
+
Path from the source record root to the
|
|
16779
|
+
array of lines whose elements feed this
|
|
16780
|
+
subrecord — the same array the sublist
|
|
16781
|
+
iterates (`lineItems`, `items`); the n-th
|
|
16782
|
+
element populates the n-th sublist line.
|
|
16783
|
+
`$` only when each source record is itself
|
|
16784
|
+
one line. Defaults to `$`.
|
|
16785
|
+
x-celigo-ai-guidance:
|
|
16786
|
+
- |-
|
|
16787
|
+
`$` on a record whose lines sit under a field renders no subrecord for any
|
|
16788
|
+
line, and NetSuite rejects the first numbered line with `Please configure the
|
|
16789
|
+
inventory detail in line N of the item list`; name the line array
|
|
16790
|
+
(`lineItems`), never the current-line context.
|
|
16784
16791
|
mapping:
|
|
16785
16792
|
type: object
|
|
16786
16793
|
description: |
|
|
@@ -16891,6 +16898,11 @@ components:
|
|
|
16891
16898
|
with `MULTIPLE_LINES_WITH_SAME_KEYS` ("Multiple lines found with keys item=<value> ..."). A
|
|
16892
16899
|
line that matches none is added as a new line, which an item fulfillment's `item` sublist
|
|
16893
16900
|
refuses with `SSS_INVALID_SUBLIST_OPERATION`: its lines are its order's.
|
|
16901
|
+
|
|
16902
|
+
On a fulfillment created from an order, a kit's lot-, serial- or bin-managed components are
|
|
16903
|
+
lines of their own under the kit's line, each with its own `line` and `orderline` (the
|
|
16904
|
+
component's own order line) and `kitmemberof` holding the kit line's id; the inventory detail
|
|
16905
|
+
belongs on those component lines, and a kit line refuses it.
|
|
16894
16906
|
x-celigo-ai-guidance:
|
|
16895
16907
|
- |-
|
|
16896
16908
|
To make an update replace a sublist's lines, also map the body field
|
|
@@ -16905,6 +16917,24 @@ components:
|
|
|
16905
16917
|
field, or, on a fulfillment, the order line's id mapped to `orderline`. Keying on the item fails
|
|
16906
16918
|
with `MULTIPLE_LINES_WITH_SAME_KEYS` when an order holds the same item on two lines, and records
|
|
16907
16919
|
that already hold repeated lines fail the same way once a key is set.
|
|
16920
|
+
- |-
|
|
16921
|
+
A key field is read from the existing lines, never written, so a read-only field keys as well
|
|
16922
|
+
as a writable one. The mapper's "Items : Line ID" is `line` (the fulfillment's own line number,
|
|
16923
|
+
equal to the order line only on a fresh full transform) and "Items : Line Number" is `linenum`;
|
|
16924
|
+
`orderline` and `kitmemberof` are not in its picker — type `item[*].orderline` /
|
|
16925
|
+
`item[*].kitmemberof` as the destination.
|
|
16926
|
+
- |-
|
|
16927
|
+
Kit components on a fulfillment: the item is the only default key that reaches a component
|
|
16928
|
+
line, so a component two kit lines share fails with `MULTIPLE_LINES_WITH_SAME_KEYS`. Keying the
|
|
16929
|
+
component rows on the KIT's order line (`line` or `orderline`) selects the kit line instead and
|
|
16930
|
+
the save fails with `You cannot create an inventory detail for this item`. When the source
|
|
16931
|
+
carries the kit's order line on its component rows, keep the item as a key and add
|
|
16932
|
+
`item[*].kitmemberof` mapped from that line id as a second key, keep the kit rows in the list
|
|
16933
|
+
(their empty `kitmemberof` matches the kit line) with `item[*].celigo_ignore_current_line_invdetail_subrecord`
|
|
16934
|
+
true so no inventory detail is written on them, and build the inventory detail from each
|
|
16935
|
+
component row's own picks; component rows alone leave every kit line unfulfilled (`You must
|
|
16936
|
+
enter at least one line item for this transaction`). When the source can supply each
|
|
16937
|
+
component line's own order line id, key every row on `orderline` instead.
|
|
16908
16938
|
x-celigo-agent:
|
|
16909
16939
|
- mapping
|
|
16910
16940
|
lookups:
|
package/package.json
CHANGED