module function · N/ui/dialog

create()

dialog.create(options)

Creates a dialog with specified buttons.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
dialog.create(options)
Returns
Promise
Governance
None
Script types
Client scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2016.1
call shapefrom Oracle's parameter table
1dialog.create({2    buttons: /* string[], optional */,3    title:   /* string, optional */,4    message: /* string, optional */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.buttonsstring[]optionalA list of buttons to include in the dialog. Each item in the button list must be a Javascript Object that contains a label and a value property. By default, a single button with the label OK and the value true is used.
options.titlestringoptionalThe dialog title. This value defaults to an empty string.
options.messagestringoptionalThe content of the dialog. This value defaults to an empty string.
B

No Mynt syntax yet.

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

C

Competing syntax for create, 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/dialog · dialog.create(options)

Suggest syntax for create