Drillthrough question

[synergised]

I have two page (Class Build and Class Drop) that drillthrough to another page (Log Data) based on a LeadId.  Think of it as two parent pages and one child page.

The problem is on the context menu when I drill through from the Class Build I see (Class Drop and Log Data) since they share the same drillthrough filter.   Is there anyway to stop the "parent" page "Class Drop" from showing in the context menu?

[v-frfei-msft]

Hi @synergised,

Could you please tell me what does the context menu stand for? Also please share your pbix to me so that I can help with that.

Regards,

Frank

[synergised]

The pbix is too large to share.. if you need a sample we can probably put one together next week if these screen shots don't do the trick.

We have two main pages and a log data page.

We have a drillthrough filter on "Class Build Detail", "Class Build Fall Off" and "Log Data"

Accessing drillthrough from main pages we get all other the pages that have the same drillthrough filter.  What we want to see is only the Log Data menu option.  It would be cool if it would only add "Hidden" pages to the context menu or the pages with a return button on them. 

From Classs Build Detail

From Class Build Fall Off

Log Data Page is the only page with a return button on it.

[v-frfei-msft]

Hi @synergised,

Based on my test, we can put both Leadid columns from different tables to the DRILLTHOUGH of Log data page. Then there will be only one option when you use drillthrough in Page Class Build and Class Drop.

For more details, please check the pbix as attached.

https://www.dropbox.com/s/8z9k85j2vobjk1u/Drillthrough%20question.pbix?dl=0

Regards,

Frank

[synergised]

It looks like the menus can be turned off using your solution.. but log data is only filtered based on the first filter.

The two pages we have are the same date table ... just filtered differently between the two pages.  So, I don't see how we could "manufacture" another LeadId to be used as a filter.

[synergised · Accepted solution]

I went back and retried the solution and got it to work this time.. so not quite sure what I missed last time.

I ended up using the LeadId from my fact table for one and the LeadId from my main lead table for the the other one. 

[v-frfei-msft]

Hi @synergised,

Does that make sense, If so, kindly mark my answer as a solution to close the case please.

Regards,

Frank