Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
I built a graph to track open tickets for the last 90 days. The graph line changes as some tickets remain open, some are closed, and new tickets are added. In my example, on 10/5/22 (the left-most graph point) there were 34 tickets open. And on 1/2/23 (the right-most graph point) there were 24 tickets open.
Design is to have the graph interact with the table, thus showing the tickets that are open as of the selected date. When a point is selected on the graph, the table should show the requests. Currently not working. All tickets, whether open or closed, are shown on the table when any data point is selected from the graph. Note, there is a relationship, as can be seen in the snapshot of the model, where the Tickets table (sc_task) has a 1 to 1 relationship to the Requests table (via the request column). And the Requests table is built from the Tickets table.
On the second graph, which has a relationship between the Date table (Dates_Last_90_Days-Test) and the Ticket table (sc_task), there is a working interaction between the graph and the table. Only tickets that were opened on that date are listed in the table. That's due to the relationship just explained. The relationship is made of the Tickets opened_at column and Date column of the Date table.
I have checked Edit Interactions in PBI and both mentioned graphs cross-filter on the table visualization.
Snapshots
Data model
Graphs and table visualization
Measures
Used for Y-axis of graph "Total Open, as of Date":
Used for Y-axis of graph "Total Opened on Date":
@Anonymous ,refer if this can help. It is for drill through but should work for drill across
Power BI Drill Through when Userelationship is used: https://youtu.be/1BM_WGATrQA
Hi Amit, thanks for the YouTube video. It was helpful. I tried using the USERELATIONSHIP and CROSSFILTER function modifiers in my measures, but to no avail. I think what I'll do is to simplify my testing by focusing only on the one graph and table that are not crossfiltering. Thus, I can remove other tables which will remove their relationships and not supersede the needed relationship. Afterwards, I'll update this discussion.
Regardz, Mike.
Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!
Check out the October 2025 Power BI update to learn about new features.