on 12-13-2023 12:20 PM
Hello people, I am trying to understand a strange issue about sap.ui.model.FilterOperator. In our application, we would like to filter the data we get from oData service. In this example, our read operation gets more than 100 entries (indexes). When we have less than 100, the filter operator working as intended but when we exceed 100 indexes it bypasses the filter and gets the whole set.
Result: (wrong one)
Check if the request contains the filter correctly in the URL, then check if it's correctly used in the backend.
Unfortunately there is not much to look at from your screenshots, the front-end code seems ok. Note that you're using only one of those 3 filters. Is that intended?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
78 | |
9 | |
9 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.