Forum Discussion
Drillthrough is not working correctly
Hi All,
I hope that someone can help me. I am using drillthrough to deepdive in the dataset. The drillthrough can be done on [problemcode]. In the drillthrough tab we can see in which processteps this problemcode was given and by which operator. Herefor I have two tables [screening] and [wip]. The WIP data includes the detail information.
For example:
If I do a drillthrough on "problemcode A" then I want to see only the processteps for that problem code (only "Screening"), but I see also the other processteps where the unit got other problemcodes.
| Serial | ProblemCode | Processtep |
| A | A | Screening |
| A | B | Inspection |
| A | C | Final |
Thanks in advance.
It works as expected based on the active relationship. I believe you are trying to include the Problemcode as well in the active relationship.
Create a new key column in both the tables as below..
Simply, you could join the tables based on the new column to achieve what you need.
Or
you have to build a new dimension for Serial and ProblemCode as below and use that to define relationships
Serial ProblemCode Key
A A AA A B AB B C BC A A B B Note that I have removed Serial and ProblemCode from other two tables.
The graph in the overview page and drillthrough filter will use Problemcode from the new table.
If it helps, mark it as a solution
Kudos are nice too
8 Replies
- VasTg
Memorable Member
Do you have Processstep added in your drillthrough filter?
If so, Do you see it filtered for "Screening" in your detail page after drillthrough?
When there are no direct filter conditions, it will crossjoin to bring in all the data.
If it helps, mark it as a solution
Kudos are nice too
- TomMartens
Super User
Hey BYENER ,
I'm not sure if I understand your data model 100%, but I assume that you "just" have 2 tables.
I suggest, that you create a 3rd table: ProblemCode that contains the distinct values. Relate this table to the screening table (on the many side) and the wip table (on the many side).
Use the new ProblemCode table for the table visual and also use this column for the drillthrough.
Hopefully, this provides what you are looking for if not, please consider to create a pbix that contains sample data (but still reflects your data model), upload the pbix to onedrive or dropbox and share the link.
Regards,
Tom