module function · N/search
createSetting()
search.createSetting(options)
Creates a new search setting and returns it as a search.Setting object.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1search.createSetting({2 name: /* string, required */,3 value: /* string, required */4});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.name | string | required | The name of the search parameter to set. This value sets the Setting.name property. Use one of the following values for this parameter: consolidationtype : This value corresponds to the Consolidated Exchange Rate setting. includeperiodendtransactions : This value corresponds to the Show Period End Transactions setting. |
| options.value | string | required | The value of the search parameter. If you are executing a joined search, this value is the join ID used for the search field specified by the options.name parameter. This value sets the Setting.value property. If you specify consolidationtype as the search parameter name, use one of the following values for this parameter: ACCTTYPE AVERAGE CURRENT HISTORICAL NONE The default value is ACCTTYPE , which represents the type of consolidation associated with the account. If you specify includeperiodendtransactions as the search parameter name, use one of the following values for this parameter: F FALSE T TRUE The default value is false . These values are not case sensitive. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to search.createSetting(options) today. How should it read?
C
community proposals
Competing syntax for createSetting, 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?