mynt

module function · N/search

createColumn()

search.createColumn(options)

Creates a new search column as a search.Column object.

Implementation
Not started used inside other constructs
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
search.createColumn(options)
Module
N/search
Returns
search.Column
Governance
None
Script types
Client and server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2015.2
call shapefrom Oracle's parameter table
1search.createColumn({2    name:     /* string, required */,3    join:     /* string, optional */,4    summary:  /* string, optional */,5    formula:  /* string, optional */,6    function: /* string, optional */,7    label:    /* string, optional */,8    sort:     /* string, optional */9});
Oracle reference for this method
ParameterTypeRequiredDescription
options.namestringrequiredName of the search column. See Column.name .
options.joinstringoptionalJoin ID for the search column. See Column.join .
options.summarystringoptionalSummary type for the column. See search.Summary and Column.summary .
options.formulastringoptionalFormula for the search column. See Column.formula .
options.functionstringoptionalSpecial function for the search column. See Column.function .
options.labelstringoptionalLabel for the search column. See Column.label .
options.sortstringoptionalThe sort order of the column. Use the search.Sort enum for this argument. Also see Column.sort .
B mynt syntax

No syntax of its own.

The compiler already calls search.createColumn(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 createColumn, 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/search · search.createColumn(options)

Suggest syntax for createColumn