Question

OData Integration Filtering and Pagination Performance

0

Hi communityWe have exposed a Mendix entity via OData. An external BI tool is consuming it and running $filter and $skip/$top queries. For large datasets (500k+ records) the queries are extremely slow. Is Mendix pushing filter predicates down to the database or doing in-memory filtering?

asked 2026-06-06

Rakesh

1 answers

Gurumoorthy J · Accepted Answer · 2026-06-06

Hi Rakesh

Mendix does push OData $filter, $skip, and $top down to the database as SQL for simple attribute based filters. However, there are several cases where it falls back to in-memory filtering which kills performance at scale,Filtering on associated entity attributes (cross-entity path filters) Using non-persistent entities or virtual attributes in the OData mapping Applying access rules with XPath constraints that cannot be translated to SQL Diagnose by enabling query logging (com.mendix.core.Core → TRACE). If you see a SELECT without a WHERE clause followed by large result sets, filtering is in-memory.