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 am playing around with the new Dataverse connector in Power BI , which now provides real-time data and support for the Dataverse security model, which is great.
I have created an out-of-the-box many to many relationship in Dataverse between the Opportunity and Product/service (custom table). When I add the tables to Power BI, the relationships are discovered as below:
Now I would simply like to filter the opportunity table based on a a slicer that contains the Products and services. However, with the current setup that does not seem to work.
In Power Apps (Dataverse) I can filter the opportuny table based on one or more products/services like this:
And the FetchXML looks like this:
So, do I need to alter something in Power BI to achieve the same result?
Solved! Go to Solution.
I dont know much about the dataverse connector but from the relationship view you can see the direction in which the arrows are being pointed, that shows what table can filter which other table. To me it looks like you cant get as far as the table you want to because you have single direction relationships.
watched this video last night which might be useful in helping you to do what you need to.
https://www.youtube.com/watch?v=6WU7Ze32Q3w&t=972s
Proud to be a Super User!
I dont know much about the dataverse connector but from the relationship view you can see the direction in which the arrows are being pointed, that shows what table can filter which other table. To me it looks like you cant get as far as the table you want to because you have single direction relationships.
watched this video last night which might be useful in helping you to do what you need to.
https://www.youtube.com/watch?v=6WU7Ze32Q3w&t=972s
Proud to be a Super User!
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.
User | Count |
---|---|
97 | |
97 | |
81 | |
77 | |
66 |
User | Count |
---|---|
126 | |
105 | |
103 | |
81 | |
72 |