-
Type: Bug
-
Status: Open
-
Priority: Major
-
Resolution: Unresolved
-
Affects Version/s: 10.3-SNAPSHOT
-
Fix Version/s: QualifiedToSchedule
-
Component/s: Core
-
Tags:
When using the operation Document.Update with the parameter changeToken, the returned document still has the same value for changeToken as the one before the update.
From what I have understood, it's because of the CoreSession.save() done in the OperationContext.close() that occurs after returning the updated document in the operation.
Our use case was the following:
- We have a dashboard with a list of documents, for each of them we can update a metadata and we used the operation for that
- Because we don't want to refresh the page provider after each update, we simply update the changeToken for the updated items
- As it was the same value returned, multiple updates of the same item without a refresh of the page lead to a 409 error
Our workaround was to use the CRUD endpoint instead of the Operation.