This service is deprecated:
POST /entity/#/table/deleterows
Instead, rows can be deleted by updating a change set that has row IDs but no values. This can be done in the form of a csv upload or by a row set sent as a request body.
The task then is to update the Py client row deletion to use a non-deprecated approach.
Regarding validation: I checked that the table row deletion code is correct in the client. The next step I would do is to check that the use of the deprecated service drops off after the client is released. Is that OK or is there something else you would like me to do before the client is released?
Regarding validation: I checked that the table row deletion code is correct in the client. The next step I would do is to check that the use of the deprecated service drops off after the client is released. Is that OK or is there something else you would like me to do before the client is released?
In addition to checking the implementation, validation should also be done from the user's perspective where syn.delete() is a back box. Perform a syn.tableQuery() and syn.delete() the results to make sure deletion is still working properly. If you have already done that then there is nothing else left to do.
I made a table with two columns and two rows, then verified that the following deletes them: