mynt

Form object method · N/ui/serverWidget

addSecretKeyField()

Form.addSecretKeyField(options)

Add a secret key field to the form.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
Form.addSecretKeyField(options)
Returns
serverWidget.Field
Governance
None
Script types
Suitelets and beforeLoad user events
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2016.1
call shapefrom Oracle's parameter table
1objForm.addSecretKeyField({2    id:        /* string, required */,3    label:     /* string, required */,4    container: /* string, optional */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.idstringrequiredThe internal ID of the secret key field. The internal ID must be in lowercase, contain no spaces, and include the prefix custpage if you are adding the field to an existing page.
options.labelstringrequiredThe UI label for the field.
options.containerstringoptionalThe internal ID of the tab or field group to add the field to. By default, the field is added to the main section of the form.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

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

All discussions

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, 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.addSecretKeyField(options)

Suggest syntax for addSecretKeyField