Form object method · N/ui/serverWidget

addButton()

Form.addButton(options)

Adds a button to the form.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
Form.addButton(options)
Returns
serverWidget.Button
Governance
None
Script types
Suitelets and beforeLoad user events
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1objForm.addButton({2    id:    /* string, required */,3    label: /* string, required */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.idstringrequiredThe internal ID of the button. If you are adding the button to an existing page, the internal ID must be in lowercase, contain no spaces, and include the prefix custpage . For example, if you add a button that appears as Update Order , the button internal ID should be something similar to custpage _updateorder.
options.labelstringrequiredThe label for this button.
B

No Mynt syntax yet.

Nothing in the language compiles to Form.addButton(options) today. How should it read?

C

Competing syntax for addButton, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

Loading proposals from GitHub…

D

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, save and Ref[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?

N/ui/serverWidget · Form.addButton(options)

Suggest syntax for addButton