mynt

Document object method · N/xml

createAttributeNS()

Document.createAttributeNS(options)

Creates an attribute node of type ATTRIBUTE_NODE, with the specified namespace value and optional specified value.

Implementation
Not started
Design
Open for proposals suggest how it should read
Proposals
A suitescript api
Signature
Document.createAttributeNS(options)
Module
N/xml
Returns
xml.Attr
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.createAttributeNS({2    namespaceURI:  /* string, required */,3    qualifiedName: /* string, required */,4    value:         /* string, optional */5});
Oracle reference for this method
ParameterTypeRequiredDescription
options.namespaceURIstringrequiredNamespace URI of the attribute to create. Value can be null .
options.qualifiedNamestringrequiredQualified name of the new attribute node.
options.valuestringoptionalValue for the attribute node. If unspecified, the value is an empty string.
B mynt syntax

No Mynt syntax yet.

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

C community proposals

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

Suggest syntax for createAttributeNS