Result object method · N/search
getValue()
Result.getValue(options)
Used on formula fields and non-formula (standard) fields to get the value of a specified search return column.
- Implementation
- Not started used inside other constructs
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objResult.getValue({2 name: /* string, required */,3 join: /* string, optional */,4 summary: /* string, optional */,5 func: /* string, optional */6});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.name | string | required | The search return column name. |
| options.join | string | optional | The join id for this search return column. Join IDs are listed in the Records Browser. For more information, see Working with the SuiteScript Records Browser . |
| options.summary | string | optional | The summary type for this column. See search.Summary . |
| options.func | string | optional | Special function for the search column. See Column.function . |
B
mynt syntax
No syntax of its own.
The compiler already calls Result.getValue(options) inside search T and load Search, so programs use it without naming it. Writing it directly has no syntax yet.
C
community proposals
Competing syntax for getValue, 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?