Document object method · N/xml

getElementById()

Document.getElementById(options)

Returns the element that has an ID attribute with the specified value as an xml.Element object.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A
Signature
Document.getElementById(options)
Module
N/xml
Returns
xml.Element
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
1objDocument.getElementById({2    elementId: /* string, required */3});
Oracle reference for this method
ParameterTypeRequiredDescription
options.elementIdstringrequiredUnique ID value for an element.
B

No Mynt syntax yet.

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

C

Competing syntax for getElementById, 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/xml · Document.getElementById(options)

Suggest syntax for getElementById