cancel
Showing results for 
Search instead for 
Did you mean: 

SAP UI5 filter operator doesn't work while reading entity from oData.

ciyradyl
Explorer
0 Kudos

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)

Accepted Solutions (0)

Answers (1)

Answers (1)

AlexNecula
Active Contributor
0 Kudos

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?

ciyradyl
Explorer
0 Kudos

Yes, it is intended. We are using the other filters for another read function. As I said that, it was working fine before adding more freight orders to the system(more than 100). When we exceeded 100 indexes, it started to bypass the filters for all read functions.

AlexNecula
Active Contributor
0 Kudos

There is no logic that I know of to ignore filters when having more than 100 lines in the database. Check what I mentioned in my previous comment.

ciyradyl
Explorer
0 Kudos

Thanks for the answer, I will check the url and backend.