Record object method · N/record
setSublistValue()
Record.setSublistValue(options)
Sets the value of a sublist field.
- Implementation
- Implemented published in npm 0.0.1
- Design
- Accepted
line.field = value
A
suitescript api
1objRecord.setSublistValue({2 sublistId: /* string, required */,3 fieldId: /* string, required */,4 line: /* number, required */,5 value: /* number | Date | string | array | boolean, required */6});
| 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 of the sublist. Note that line indexing begins at 0 with SuiteScript 2.x. |
| options.value | number | Date | string | array | boolean | required | The value to set the sublist field to. The value type must correspond to the field type being set. For example: Text, Radio and Select fields accept string values. Checkbox fields accept boolean values. Date and DateTime fields accept Date values. Integer, Float, Currency and Percent fields accept number values. Note: There may be a few exceptions to value and field type matching in SuiteScript. For example, the Role field on the Resource subtab of project records is a multi-select field. However, in SuiteScript, this field can only accept one internal ID and does not accept an array of values. The only workaround to select multiple values for this field is to use the NetSuite UI. |
B
mynt syntax
Supported syntax · compiles today
line.quantity = 1
1order.setSublistValue({2 sublistId: "item",3 fieldId: "quantity",4 line: line$index,5 value: 16});
Published on npm since 0.0.1. Verified with mynt build on 13 Oct 2026.
C
community proposals
Competing syntax for setSublistValue, from GitHub Discussions. Select two or more to compare them side by side, with the syntax Mynt supports today as a baseline.
Mynt today
line.quantity = 1Loading 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?