Record object method · N/record
getSublistValue()
Record.getSublistValue(options)
Returns the value of a sublist field.
- Implementation
- Implemented published in npm 0.0.1
- Design
- Accepted
line.field
A
suitescript api
1objRecord.getSublistValue({2 sublistId: /* string, required */,3 fieldId: /* string, required */,4 line: /* number, required */5});
| 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.fieldId | string | required | The internal ID of a standard or custom sublist field. See, Finding Internal IDs of Record Fields . |
| options.line | number | required | The line number for the field. Note that line indexing begins at 0 with SuiteScript 2.x. |
B
mynt syntax
Supported syntax · compiles today
if line.quantity < 1 {
1if (2 order.getSublistValue({3 sublistId: "item",4 fieldId: "quantity",5 line: line$index6 }) < 17) {
Published on npm since 0.0.1. Verified with mynt build on 13 Oct 2026.
C
community proposals
Competing syntax for getSublistValue, from GitHub Discussions. Select two or more to compare them side by side, with the syntax Mynt supports today as a baseline.
Mynt today
if line.quantity < 1 {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?