Drillthrough with different field name and no relationship

[dude95]

I'm pulling information in from Jira.  I've got an issue table (IssueId is key) and a link table (with SourceId and DestId that are the issue ids for the respective issues)

I'm trying to do a drill through.  One report is the parent request and total number of child issues.  Drill into the second report for a listing of all of those children.

The problem is I can't manage to filter the drill down report to just the ones that the IssueId in the header corresponds to the SourceId in the link table.  I can't put in a relationship with the two fields because I will want to use the DestID (Child Issue ID) in relationship to the header sometimes also.

Here's a pbx with the data.

BTW - posted a question around this yesterday, but feel like this is a different question so posting seperately.

[MFelix]

Hi @dude95 ,

I'm assuming that the connection you want to make is the one below correct?

If this is the relation then you have to place on the drill trough the field IssueId and that should work properly.

Please check file attach.

[dude95]

I can't have this relationship because the relation from the issue header table will sometimes be to SourceId and sometimes be to DestID

[v-deddai1-msft]

Hi @dude95 ,

If you mean drill 'summarize table' to 'detail table' without relationship, it is impossible. the filter can't be pass through summarize table to detail table.

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Best Regards,

Dedmon Dai

[MFelix]

Hi @dude95 ,

How do you know when is one connection or the other one? For the drill trough to work you need to setup the relationship in he tables or trough some kind of measure otherwise the model will not know what you want to filter.

[dude95 · Accepted solution]

Have now faked it out.  Added measure to table with following

SourceID =

VAR __IssueID = max(JiraHdrSet[IssueId])

VAR __Count = CALCULATE (

COUNT ( JiraLinkSet[SourceId] ),

FILTER ( JiraLinkSet, JiraLinkSet[SourceId] = __IssueID ) )

RETURN

__Count

Added that measure to my table - and it filters out all of the non-relevant tickets.  Change the column name to 1, shrunk the column to not visable.  By no means is it pretty...but it does work.