module function · N/render
packingSlip()
render.packingSlip(options)
Creates a PDF or HTML file object containing a packing slip.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1render.packingSlip({2 entityId: /* number, required */,3 printMode: /* string, optional */,4 formId: /* number, optional */,5 fulfillmentId: /* number, optional */,6 inCustLocale: /* boolean, optional */7});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.entityId | number | required | The internal ID of the transaction associated with the packing slip. |
| options.printMode | string | optional | The print output type. Set using the render.PrintMode enum. By default, uses the company/user preference for print output. |
| options.formId | number | optional | The packing slip form number. |
| options.fulfillmentId | number | optional | The fulfillment ID number. |
| options.inCustLocale | boolean | optional | Applies when advanced templates are used. Print the document in the customer's locale. If basic printing is used, this parameter is ignored and the transaction form is printed in the customer's locale. |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to render.packingSlip(options) today. How should it read?
C
community proposals
Competing syntax for packingSlip, 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?