You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From Ritense, the following issue has been found. I've been able to reproduce it by using PUT against an existing object with a modified field and after that trying to match the old objects' contents.
From Ritense, the following issue has been found. I've been able to reproduce it by using PUT against an existing object with a modified field and after that trying to match the old objects' contents.
We have object e89cca88-... with a status field:
GET https://objects-api/api/v2/objects?&page=1&type=https://objecttypes-api/api/v1/f972b43c-...&data_attrs=adresinformatie__status__exact__IN_SANERINGSPROJECT
We modify the object to the new status:
PUT https://objects-api/api/v2/objects/e89cca88-...
However when searching for the old status, this matches the modified object which isn't expected:
GET https://objects-api/api/v2/objects?&page=1&type=https://objecttypes-api/api/v1/f972b43c-...&data_attrs=adresinformatie__status__exact__IN_SANERINGSPROJECT
The question then is how the API user can use object_list and ensure that only the objects with the status "IN_SANERINGSPROJECT" are found.
The text was updated successfully, but these errors were encountered: