Hi,
We have tested this and the correct syntax for finding multiple attributes is as below:
customer?attributes={"DATETEST":"2019-01-01","TEST":"testvalue"}
When encoding, the equal signs should not be encoded, both examples below works:
customer?attributes=%7B"DATETEST":"2019-01-01","TEST":"testvalue"%7D
customer?attributes=%7B%22DATETEST%22%3A%222019-01-01%22%2C%22TEST%22%3A%22testvalue%22%7D
Regarding the pagination,
The returned metaData totalCount:
We have a case in the backlog for this, the issue is that the operation first gets all objects for the endpoint, and then skipping the objects that don't match the attributes. So the totalCount is set during the initial SQL search.
The solution for this is to create new V2 endpoints where the JOIN is done in the initial SQL query.
The result when using pagination is incorrectly returned:
We can confirm that this is happening and will open a case with the developers. Progress will be posted in this thread.
In our test:
customer?attributes={"TEST":"testvalue"}&pageNumber=1&pageSize=1 : Two objects match this criteria.
pageSize=1:
pageNumber=1: Incorrectly returns empty array
pageNumber=2: Returns 1st object
pageNumber=3-4: Returns empty array
pageNumber=5: Returns 2nd object
pageSize=2:
pageNumber=1: Returns 1st object
pageNumber=2: Returns empty array
pageNumber=3: Returns 2nd object
pageSize=3 & 4
pageNumber=1: Returns 1st object
pageNumber=2: Returns 2nd object
pageSize=5
pageNumber= 1: Returns both objects as expected
... View more
.gif "VISMA"){kind=icon}
Visma Denmark
Visma Finland
Visma Latvia
Visma Netherlands
Visma Norway
Visma Sweden
Visma Developers & Partners
Visma Latin America