<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>OData on Stephan Bruijnis .dev</title><link>/tags/odata/</link><description>Recent content in OData on Stephan Bruijnis .dev</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright (c) 2024 Stephan Bruijnis</copyright><lastBuildDate>Tue, 24 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/odata/index.xml" rel="self" type="application/rss+xml"/><item><title>External Entities: Not all OData retrieves are optimized</title><link>/posts/external-entities-odata-optimizations/</link><pubDate>Tue, 24 Mar 2026 00:00:00 +0000</pubDate><guid>/posts/external-entities-odata-optimizations/</guid><description>Question: Does Mendix fully leverage the OData features when retrieving External Entity data?
Answer: No. While Mendix does use the OData query parameters like $filter, $top and $skip, it leaves some performance gains on the table.
In Mendix, external entities are published as a standard OData service which exposes its data as entities. On the consuming end, Mendix abstracts it by importing the service contract into the app allowing developers to work with remote entities as if it were local entities without managing the underlying REST calls themselves.</description></item></channel></rss>