module function · N/query
createRelativeDate()
query.createRelativeDate(options)
Creates a query.RelativeDate object that represents a date relative to the current date.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1query.createRelativeDate({2 dateId: /* string, required */,3 value: /* number, required */4});| Parameter | Type | Required | Description |
|---|---|---|---|
| options.dateId | string | required | The ID of the relative date to create. Use the query.DateId enum to set this value. |
| options.value | number | required | The value to use to create the relative date. This value depends on the value that you specify for options.dateId . For example, to create a relative date that represents the date five days before the current date, use an options.value value of 5 and an options.dateId value of query.DateId.DAYS_AGO . |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to query.createRelativeDate(options) today. How should it read?
C
community proposals
Competing syntax for createRelativeDate, 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?