iSheets API version 2 - iSheet admin - API - Column CRUD operations - Edit column
OVERVIEW
Add a column to an existing iSheet
PUT /api/3/isheets/admin/{isheetid}/columns/{columnid}
Request Body
send column object
Response
If the operation is successful, the API returns a progressive key resource object . Based on this progressive key, you can see the status of the iSheet column otherwise an error object is returned with the appropriate error code.
To get the status of an iSheet column based on a progressive key
POST /api/3/progressivekeystatus/{progressive_key}
Name | Type | Description |
---|---|---|
progressive_key | String |
This key shows the status of your progress. When a delete request is sent a progressive key, is returned back so the status can be checked. |
If the delete operation is successful, the API returns a progressive key resource object with a status of either 'in-progress', 'done', or 'failed'. If there is a failure, an error object is returned with the appropriate error code.
Internal Information
JIRA : https://dev.highq.com/jira/browse/COL-48540
Andrew Quinn as always thank you for raising the issue. I have asked the engineering team to look into this. Thanks
Hi Imran Aziz, I've looked more into this, and it seems this endpoint is sensitive to concurrency, i.e. it only seems to work when one edit column "transaction" is made at a time. By "transaction" I mean that you have to wait for the progress to complete before issuing the next edit column request - issuing two or more results in the "infinite" progress status described above.
Can you (HighQ Dev's) confirm this is the case, and that this is a bug?
Thanks in advance, Andrew
I tried to edit a column by simply modifying the column conditions.
is interesting that on this particular column no matter how long i wait i only get
{
"progressivekey": "2IVUYtGtFG_1534983930441",
"siteid": null,
"progressivekeystatus": "INPROGRESS",
"userid": null,
"responsebody": null,
"message": null,
"messagecode": null,
"integrationResponseDBO": null,
"error": null,
"downloadlink": null
}
ie in progress..it seems like is stuck on that status?
Could this be a bug?
Comments
3 Comments