mynt

module function · N/dataset

createCondition()

dataset.createCondition(options)

Creates a dataset condition (criteria).

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
dataset.createCondition(options)
Module
N/dataset
Returns
dataset.Condition
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2020.2
call shapefrom Oracle's parameter table
1dataset.createCondition({2    values: /* Array< null|Object|number|string|boolean|Date>, optional */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.valuesArray< null|Object|number|string|boolean|Date>optionalThe values for the condition. For the top-level condition in a dataset (the single condition that child conditions are combined into), this property is always an empty array. Child conditions are implicitly combined using the appropriate operator (AND, OR) to produce a single condition, so no values need to be specified.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

Competing syntax for createCondition, 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/dataset · dataset.createCondition(options)

Suggest syntax for createCondition