Hi We have active implementations and use cases where we utilize search on customer endpoint with attributes filter. Like so: https://integration.visma.net/API/controller/api/v1/customer?attributes=%7B%22TESTATTR%22:%224%22%7D&pageSize=100&pageNumber=1 We also adhere to pagination since that is mandatory. The problem we are experiencing is the following. Under certain circumstances (more on that below) we receive no customer when we should receive customer. See the following examples: # Match found, customer returned, as it should https://integration.visma.net/API/controller/api/v1/customer?attributes=%7B%22TESTATTR%22:%224%22%7D&pageSize=100&pageNumber=1 # No match found, no customer retured, but should have https://integration.visma.net/API/controller/api/v1/customer?attributes=%7B%22TESTATTR%22:%223828598964310%22%7D&pageSize=100&pageNumber=1 If we tweak the last call and omit pageSize & pageNumber or increase pageSize to 1000, we can see the following different outcome. # Match found, customer returned, as it should https://integration.visma.net/API/controller/api/v1/customer?attributes=%7B%22TESTATTR%22:%223828598964310%22%7D # Match found, customer returned, as it should https://integration.visma.net/API/controller/api/v1/customer?attributes=%7B%22TESTATTR%22:%223828598964310%22%7D&pageSize=1000&pageNumber=1 Our conclusion is that there is a conflict in search/filter and pagination where customers (in this case) are missed due to them being later in the register than page size. Missed or at least not correctly returned in response. The first query returns correctly matched customer since its in the top 100 range. The next that doesn't correctly return is furter down in the 400 range and thus not returned when using page size 100 in this case. Since pagination is best practise mandatory we end up in catch 22. Would like feedback on above scenarios and how to proceed. Thanks!
... View more