module function · N/machineTranslation

createDocument()

machineTranslation.createDocument(options)

Creates a document to be used as source content when calling the translation service.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
machineTranslation.createDocument(options)
Returns
Object
Governance
None
Script types
Server scripts
Version
SuiteScript 2.x, documented for 2.1; since NetSuite 2025.1
call shapefrom Oracle's parameter table
1machineTranslation.createDocument({2    id:       /* string, required */,3    text:     /* string, required */,4    language: /* string, optional */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.idstringrequiredThe ID of the document.
options.textstringrequiredThe text of the document.
options.languagestringoptionalThe language of the document. Use values from the machineTranslation.Language enum to set the value of this parameter. If you don't specify the document language, the translation service detects the language automatically when you pass the document to machineTranslation.translate(options) .
B

No Mynt syntax yet.

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

C

Competing syntax for createDocument, from GitHub Discussions. Select two or more to compare them side by side.

All discussions

Loading proposals from GitHub…

D

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/machineTranslation · machineTranslation.createDocument(options)

Suggest syntax for createDocument