Drill-through Not Working Between Pages Using Different Data Sources in Power BI

[bhavanikaruppia]

I’m trying to implement a drill-through from a main page to a subpage in Power BI. Each page is based on a different underlying data source, though both tables have the same column structure. However, the drill-through functionality is not working as expected.

Workarounds Attempted:

• Created a view using UNION ALL to combine both source tables into a single dataset and introduced a source_table column to differentiate between the two sources.

• Applied page-level filters using the source_table column to isolate records relevant to each page.

• Added a slicer with the source_table field on both pages to dynamically control filtering.

Despite these attempts, the drill-through feature still does not function correctly.

Additional Context:
The ETL logic behind the two tables is as follows:

• Table A includes a filter to retain only records with Rank = 1.

• Table B contains the full dataset without ranking applied.
  Other than this difference, the column definitions in both tables are identical.

Please advise on how to enable drill-through functionality in this scenario or suggest an alternative approach.

[BhavaniK]

Thank you @rajendraongole1 , it solved the issue. 

[v-echaithra]

Hi @bhavanikaruppia ,

Thank you for sharing your update and confirming that you dont have any issue. i request you to please accept the post that resolved your issue as the solution, this will help other community members who might face a similar issue.

Thanks again for your contribution!

[HarishKM]

@bhavanikaruppia  Hey,

Steps to follow
1) Create a combined table in power query
something like below

SELECT *, 'SourceA' AS source_table FROM TableA WHERE Rank = 1
UNION ALL
SELECT *, 'SourceB' AS source_table FROM TableB

step 2- Use only field and drill thorough filters from your newly union table for drill - through - This will only work if visual and drill thorough page from same table

step 3 - add a page level filter from on drill through page

Thanks

Harish KM

Please accept this as a solution if this solves your problem and give kudos as well.

[rajendraongole1]

Hi @bhavanikaruppia  - you can create a seperate dim table and load it to your model related to table a and table b.

Power BI considers them as distinct lineages,even if you use a UNION in a view and a source_table column, if the drill-through visual uses fields from the original tables, it won’t match the combined field in your target page.

add, use a slicer or page-level filter on source_table to isolate which records should appear on the target page.

Hope this helps.

[BhavaniK]

Hi @rajendraongole1 , thanks for the suggestion. Here’s what I’ve implemented so far:

• Created a Dim_table using a UNION of TableA and TableB.
• Added a keycolumn using RowNumber across TableA, TableB, and Dim_table.
• Established many-to-one relationships from:
• Dim_table → TableA
• Dim_table → TableB
• Used common columns from Dim_table in the visuals on both pages.
• Added a drill-through filter sourced from Dim_table.
• Structured the report pages as follows:

• Main page: All columns are from Dim_table since they’re required for drill-through.
• Target page: Contains columns from both Dim_table and TableB.

However, the drill-through isn’t functioning as expected:

• It redirects to the target page but includes more records than it should.

[rajendraongole1]

Close to the solution, Make only one relationship active at a time.

In your model view, keep the relationship from Dim_table → TableB active.

Keep the Dim_table → TableA relationship inactive (unless you need it for measures).

Check below :

1.Visuals on the main page are from Dim_table

2.Visuals on the target page are from TableB and Dim_table.

3.This ensures filter propagation flows cleanly during drill-through from Dim_table to TableB.

this works, Ensure your drill-through filter field is the same field used in the relationship (i.e., KeyColumn from Dim_table).