Record object method · N/record
insertLine()
Record.insertLine(options)
Inserts a sublist line.
- Implementation
- Implemented published in npm 0.0.1
- Design
- Accepted
add r.sublist { ... }
A
suitescript api
1objRecord.insertLine({2 sublistId: /* string, required */,3 line: /* number, required */4});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.sublistId | string | required | The internal ID of the sublist. This value is displayed in the Records Browser. For more information, see Working with the SuiteScript Records Browser . |
| options.line | number | required | The line number to insert. Note that line indexing begins at 0 with SuiteScript 2.x. |
B
mynt syntax
Supported syntax · compiles today
1add order.item {2 item = "100"3 quantity = 24}1{2 const item$line = order.getLineCount({ sublistId: "item" });3 order.insertLine({ sublistId: "item", line: item$line });4 order.setSublistValue({5 sublistId: "item",6 fieldId: "item",7 line: item$line,8 value: "100"9 });10 order.setSublistValue({11 sublistId: "item",12 fieldId: "quantity",13 line: item$line,14 value: 215 });16}Published on npm since 0.0.1. Verified with mynt build on 13 Oct 2026.
C
community proposals
Competing syntax for insertLine, from GitHub Discussions. Select two or more to compare them side by side, with the syntax Mynt supports today as a baseline.
Mynt today
add order.item {Loading proposals from GitHub…
D
suggest an alternative
Write the Mynt you wish you could write.
A good proposal shows the syntax, the SuiteScript it should become, and argues for it: why it is clearer, how it fits the rest of the language, what it makes harder.
- Clarity. Does it say what happens, without ceremony?
- Consistency. Does it read like
load,saveandRef[field]? - Expressiveness. Does it cover the cases people actually write?
- Honesty. Does it hide a NetSuite cost, such as governance, that a reader should see?