Record object method · N/record
setText()
Record.setText(options)
Sets the value of the field by a text representation.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objRecord.setText({2 fieldId: /* string, required */,3 text: /* string | array, required */4});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.fieldId | string | required | The internal ID of a standard or custom body field. See, Finding Internal IDs of Record Fields . |
| options.text | string | array | required | The text or texts to change the field value to. If the field type is multiselect : This parameter accepts an array of string values. This parameter accepts a null value. Passing in null deselects all currently selected values. If the field type is not multiselect , this parameter accepts only a single string value. Inline HTML fields accept strings. Strings containing HTML tags are represented as strings in UI, this is demonstrated in Syntax section below. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to Record.setText(options) today. How should it read?
C
community proposals
Competing syntax for setText, 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?