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