|
Filter on attributes which did not exist, gave an error message.
(For details of the issue)
|
After the release of 8.91, if you tried to filter on attributes on inventory which did not exist, you got an error message. This was a breaking change.
We have now removed the error message. The functionality will now work as before and return 200 OK, with no data.
the performance improvement on inventory endpoint, has been enabled, again, which was initially introduced with 8.91. |
Due dates for breaking change
|
Breaking change on Inventory endpoint for GET operation - better errorhandling
|
In the current solution, if you try to filter on an attribute on inventory which does not exits, you get an empty JSON response.
So, if you have misspelled or are trying to filter on an attribute that does not exist, you will not get any indication about this.
From version 8.97, we will start returning 400 Bad Request for this operation, and give an error message that the value you are trying to filter on does not exist
-
Example:
{"message":"Attribute 'ACTIVE' not found"} |
May 17, 2022 |
.gif "VISMA"){kind=icon}
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America