module function · N/workbook
createPositionUnits()
workbook.createPositionUnits(options)
Creates a position defined by units.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1workbook.createPositionUnits({2 unit: /* workbook.Unit, required */,3 x: /* number, required */,4 y: /* number, required */5});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.unit | workbook.Unit | required | The units to use for x-y coordinates. |
| options.x | number | required | The x coordinate. |
| options.y | number | required | The y coordinate. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to workbook.createPositionUnits(options) today. How should it read?
C
community proposals
Competing syntax for createPositionUnits, from GitHub Discussions. Select two or more to compare them side by side.
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,saveandRef[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?