If the OData page was working before and now loads empty after some app changes, the first thing I would check is whether one of the published OData entities, associations, or access rules became invalid after your update.

In Mendix, OData pages usually stop showing data when the exposed entity is no longer reachable for the current user, the published service metadata changed, or one of the related objects/attributes used in the service is no longer available the way it was before. So this is often not a Snowflake issue directly, but a configuration issue in the published OData service after model changes.

What I would suggest is to recheck the setup step by step. First open your Published OData Service and verify that the entity is still included, all attributes you expose still exist, and no renamed or deleted association is still being referenced. Then make sure the service is active and that the user role you are testing with still has access to the entity and its attributes. Also check whether the page is calling the same endpoint as before and whether the service metadata still opens correctly in the browser.

If the metadata endpoint opens but the page is empty, then I would look at entity access and XPath constraints next. If the metadata itself fails or returns incomplete information, then I would review the published service definition and republish it after the model changes.

For troubleshooting, it can also help to create a very small test OData service with just one simple entity and a few attributes. If that works, then the problem is likely in the current service definition rather than in the platform setup itself.

If this resolves your issue, please mark it as accepted.

Hi Maciej Bedlin,

OData was working properly earlier, but now it has stopped retrieving data while consuming the OData service. This likely means that the published OData service is no longer accessible.

1. This might have occurred due to recent changes made to the Published OData Service configuration. Please review any modifications that were made recently.
2. Another possibility is that the Consumed OData Service configuration has not been updated after those changes.
3. A third possibility is to verify that the authentication configuration is still valid.

It is also recommended to add an error handler when retrieving data from the external entity. This will help capture the exact error message and make it easier to identify the root cause of the issue.