mynt

module function · N/dataset

createTranslation()

dataset.createTranslation(options)

Creates a translation expression based on a Translation Collection.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
dataset.createTranslation(options)
Module
N/dataset
Returns
workbook.Expression
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2021.2
call shapefrom Oracle's parameter table
1dataset.createTranslation({2    collection: /* string, required */,3    key:        /* string, required */4});
Oracle reference for this method
ParameterTypeRequiredDescription
options.collectionstringrequiredThe Translation Collection to use.
options.keystringrequiredThe translation term to use.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

Competing syntax for createTranslation, 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.createTranslation(options)

Suggest syntax for createTranslation