Forum Discussion
Intersection between two Table visuals created in dashboard
I have created two table visuals on dashboard consists of one columns from main data source(present in Field). How can I find intersection between them.
Table 1 visual
Custid
1
2
3
Table 2 visual
Custid
4
5
3
Expected output Visual
Custid
3
5 Replies
- pratyashasamalMemorable Member
Hi Bikashjha ,
You can use INTERSECT DAX function to find the intersection between two tables.
Syntax :- INTERSECT(<table_expression1>, <table_expression2>)Please refer to this link :-
https://learn.microsoft.com/en-us/dax/intersect-function-daxThanks,
Pratyasha Samal
Has this post solved your problem? Please Accept as Solution so that others can find it quickly and to let the community know your problem has been solved.
If you found this post helpful, please give Kudos C - TomMartensSuper User
Hey Bikashjha ,
it's difficult to provide any solution or even guidance. As the information you provided is too scarce.
What is needed:
- are the two table visuals fed by the same table of the Power BI dataset
- what filters are active that influence the result of both table visuals
Nevertheless, you can consider creating a table that reflects on the intersection of "two tables" (assumption due to the scarce information) using the Merge transformation inside Power Query: Merge queries overview - Power Query | Microsoft Learn
The next images show how this can be achieved:
Hopefully, this provides an idea of how to tackle your challenge.
Regards,
Tom
- BikashjhaFrequent Visitor
Hi TomMartens ,
Thanks for the solution. But I want to find intersection between table visuals in dashboard(Table 1 and Table 2 in my case). Please find my dasboard on this link: https://drive.google.com/file/d/1VccYRCnyK_-rUleBwLuP6f1ildCg93Vr/view?usp=share_link
Let me know If you need anything else.
Thanks is advance😀
- TomMartensSuper User
Hey Bikashjha ,
I can tell you that this will not work, the reason is:
- a table can not be generated from an existing table initiated by slicer selection
This means the model of the dataset has to be adjusted. I will think about a solution in the next couple of days.
Regards,
Tom