Form object method · N/ui/serverWidget
addSublist()
Form.addSublist(options)
Adds a sublist to the form.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objForm.addSublist({2 id: /* string, required */,3 label: /* string, required */,4 tab: /* string, optional */,5 type: /* string, required */6});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.id | string | required | The internal ID name of the sublist. The internal ID must be in lowercase, contain no spaces, and include the prefix custpage if you are adding the sublist to an existing page. For example, if you add a sublist that appears as Purchase Details , the sublist internal ID should be something equivalent to custpage_purchasedetails or custpage_purchase_details . |
| options.label | string | required | The label for this sublist. |
| options.tab | string | optional | The tab under which to display this sublist. If empty, the sublist is added to the main tab. |
| options.type | string | required | The sublist type. Use the serverWidget.SublistType enum to set the value. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to Form.addSublist(options) today. How should it read?
C
community proposals
Competing syntax for addSublist, from GitHub Discussions. Select two or more to compare them side by side.
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?