I've encountered a number of situations where I need to make a HTTP POST and my JSON payload includes a simple array of numbers such as version: [201, 500] for example. After setting the schema this array will not appear in the parameter list such that you can assign it to a list for instance.
I find this to be a huge flaw and something that needs to be addressed. I'm not certian if it's only an issue with the clients connector or if I built a connector from scratch if I'd still have this issue. It's pretty annoying as I'd be done with this in Python by now however, I'm relying on Workato to handle the authentication.
In the example JSON payload I'm unable to set the versionIds in workato. The connector won't provide an input field for versionIds although the parameter has been created.
Michael Owen
Cannot make HTTP POST with JSON list array.
I've encountered a number of situations where I need to make a HTTP POST and my JSON payload includes a simple array of numbers such as version: [201, 500] for example. After setting the schema this array will not appear in the parameter list such that you can assign it to a list for instance.
I find this to be a huge flaw and something that needs to be addressed. I'm not certian if it's only an issue with the clients connector or if I built a connector from scratch if I'd still have this issue. It's pretty annoying as I'd be done with this in Python by now however, I'm relying on Workato to handle the authentication.
In the example JSON payload I'm unable to set the versionIds in workato. The connector won't provide an input field for versionIds although the parameter has been created.
{
"versionIds": [
208],
"additionalColumns": [{
"id": "InstallationStatusDataTreeDescription_AssembleProperty",
"type": "string"
}, {
"id": "Handle",
"type": "string"
}],
"ruleSet": null,
"groupingId": null,
"expandLevel": 1,
"selectedRowIds": [],
"n_Level": 0,
"nodeId": null,
"sortFederatedId": null,
"sortDirection": "Asc",
"colorsEnabled": false,
"colorizationProperty": null
}