To further enhance the idea that was implemented : https://community.mendix.com/link/space/integrations/ideas/564
My problem is that I cannot publish an OData services for entity associations that are many-many using as associated object id. This case was resolved in the idea above to publish associations as links but does not address the issue of where associations have to be published using object ids.
My use case is for Power BI OData consumption which cannot detect associations as a link. This seems to be a common issue for a lot of users trying to expose data to Power BI.
The same applies to Spotfire - it would be great if both options were available. Currently, in Spotfire, as in other BI tools, OData associations are not interpreted automatically. You have to manually add ID columns and create relationships, which is cumbersome. Support for handling associations more flexibly or allowing the choice between exposing them as links or as associated object IDs would significantly simplify integration.
The association tables/links are not detected. You can select to add the entities and then have no way to manually (or automatically) create the relationships.
Reading the question and answer attached below - you can write custom logic in Azure to make them accessible but this does not sound like the most effective solution.
https://community.mendix.com/link/space/integrations/questions/95322
Can you give some more details of what goes wrong when you publish associations as links and consume them in Power BI?