Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hello all,
I have a table containing tickets opened / closed.
| TicketRef | Type | CreatedDate | ResolvedDate |
| 001 | Keyboard | 01/06/2021 | 08/06/2021 |
| 002 | Car | 05/06/2021 | 06/06/2021 |
| 003 | Keyboard | 08/06/2021 | 08/06/2021 |
I have a Date Dimension table and the following relationships are setup:
| Relationship Status | From | To |
| Active | DateDimension | TicketInformation (CreatedDate) |
| Inactive | DateDimension | TicketInformation (ResolvedDate) |
By using measures and activating the ResolvedDate relationship via USERELATIONSHIP, I am able to see the total tickets created / resolved within a period that I select.
If I set the date slicer to 08/06/2021 and view my resolved breakdown:
| Type | Total |
| Keyboard | 2 |
All good. However.........
I'd now like to drill down on this "Keyboard" type to see the two tickets that were resolved When I drilldown, I only see 1 ticket, not 2. This is because the Active join is on the created date, and only 1 of the 2 tickets that were resolved were created on the date selected in the slicer.
How can I get it so that if I drill down on either the created tickets or resolved tickets, the correct join is used? Or, do I need to re-model my data in someway so that I can have an active join on both the created / resolved date?
There must be others who have got both created/resolved dates in the same table, what am I doing wrong?! 🙂
@amitchandak - Thank you. I have tried that this morning - it does work for resolved tickets, but then the breakdown for Created tickets then doesn't work properly! 😁 It's like if one works, the other doesn't!
If I drill through from Table 1 (Created tickets), I want it to use the Active join on Created Date, but If I drill through from Table 2 (Resolved tickets), I want it to use the Inactive join on Resolved Date.
Is that possible to do with just one drill-through page?
The only way I can see this being possible so far is to duplicate the dataset, have two active joins (one from each dataset), then have 2 separate drill-through pages, with one using dataset1 and the other using dataset2. I just feel like it will be a pain further down the line in a year or so!
Hope this makes sense!
Hi @Anonymous
Have you solved your problem? If yes, kindly accept it as the solution. Otherwise, please provide more details about your problem so that we can work on it further. Thanks😃
Best Regards,
Community Support Team _ Tang
If this post helps, please consider Accept it as the solution✔️ to help the other members find it more quickly.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 51 | |
| 37 | |
| 35 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 70 | |
| 64 | |
| 39 | |
| 33 | |
| 23 |