Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
I have an OData V3 data source which reflects a object hierarchy in the back end. That is, there will be an OData entity that is DERIVED from another and so on. I've uncovered a limitation that data relationships can only be detected automatically, or semi automatically using the AutoDetect button, when the relationship is in the current/'lowest' level entity.
Power BI desktop can properly detect base properties for an entity going all the way up through an entity hierarchy, but it ignores base relationships - leaving the designer to have to figure out and create them manually, which is not feasible in a complex data source.
I put in a wish list item on this:
Support OData Derived Relationships
If this is of use to you, please put in your votes to get this into the product.
Can anyone from the MS side verify this is an issue, or if there might be a workaround? If not, then I need to put some hacks in my service to be able to expose the OData relationships so Power BI can pick them up.
Not being able to detect OData relationships in domain classes that are developed using MS's own best practices is a crippling limitation to Power BI.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.