SuiteQLTask object method · N/task
addInboundDependency()
SuiteQLTask.addInboundDependency(options)
Adds a scheduled script task or map/reduce script task to the SuiteQL task as a dependent task.
- Implementation
- Not started
- Design
- Open for proposals suggest how it should read
A
suitescript api
1objSuiteQLTask.addInboundDependency({2 scriptId: /* string, required */,3 taskType: /* string, required */,4 deploymentId: /* string, optional */,5 params: /* Object, optional */6});
| Parameter | Type | Required | Description |
|---|---|---|---|
| options.scriptId | string | required | The script ID of the scheduled script record or map/reduce script record for the dependent task. |
| options.taskType | string | required | The type of dependent task. This property uses one of the following values in the task.TaskType enum: task.TaskType.SCHEDULED_SCRIPT task.TaskType.MAP_REDUCE |
| options.deploymentId | string | optional | The script ID of the script deployment record for the dependent task. To use this property, the scheduled script or map/reduce script for the dependent task must be deployed. If you do not specify a value for this property, an available deployment is selected automatically. |
| options.params | Object | optional | The parameters for the scheduled script or map/reduce script. To use this property, you must first create script parameters that are required for the dependent task. For example, if your dependent task requires a reference to the CSV result file, you must create a script parameter that maps the CSV result file ID to the file name, as in the following example: { 'custscript_query_res' : 'resultFile.csv' } For more information about script parameters, see Creating Script Parameters (Custom Fields) . |
B
mynt syntax
No Mynt syntax yet.
Nothing in the language compiles to SuiteQLTask.addInboundDependency(options) today. How should it read?
C
community proposals
Competing syntax for addInboundDependency, 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?