Hi Isomorphic,
I'm seeing a behaviour in 12.0p, where I think it might be a bug:
I have a operationType:custom-DSRequest, that can be sent for one or many items of a list from clientside. In case many entries are selected, the requests are sent as a queue.
Now this request fails for some entries, which is fine in general. The problem is the handling of relatedUpdates in the non-failing requests in the queue.
In this case the relatedUpdates of request 1 is applied in the GUI/ResultSet, while the whole transaction is rolled back serverside.
An example where DSRequest 2 and 3 of 3 fail, while DSRequest 1 on it's own succeeds:
Thank you & Best regards
Blama
I'm seeing a behaviour in 12.0p, where I think it might be a bug:
I have a operationType:custom-DSRequest, that can be sent for one or many items of a list from clientside. In case many entries are selected, the requests are sent as a queue.
Now this request fails for some entries, which is fine in general. The problem is the handling of relatedUpdates in the non-failing requests in the queue.
In this case the relatedUpdates of request 1 is applied in the GUI/ResultSet, while the whole transaction is rolled back serverside.
An example where DSRequest 2 and 3 of 3 fail, while DSRequest 1 on it's own succeeds:
- Queue-response
- operationType:custom-DSResponse
- status:0
- queueStatus:-1
- relatedUpdates: some proper relatedUpdate-record
- operationType:custom-DSResponse
- status:-1
- queueStatus:-1,
- data: my error message text
- operationType:custom-DSResponse
- status:-1
- queueStatus:-1,
- data: my error message text
- operationType:custom-DSResponse
Thank you & Best regards
Blama
Comment