Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
In the model below, I have an Dimension Table (HoursTable) (hour/day/month/year) linked by a 1-Many by the hour column to a Telemetry table (Where TImeKey is the foreign key) and it is in hours).
In a BarChart I am showing the Distance vs Time (where the X-axis Time, is the Hour/Day/Month Hierarchi) from the Hour Table.
All that is working fine.
But I am also have a TimeLine (2.4.0) visual From MSFT that I am using as slicer. Funny thing. I though I should be able to set that "slicer" to use the same HourTable (with the same hierarchy) as the Bar chart. IF I do that then it seems to slice, but in fact there is no cross filtering on the page, and the bar chart does not uipdate.
Only if I specificy the TimeKey (which is part of the telemetry table) does the slicing work properly
There is something here, I want to fully understand about the internals of PowerBI not just to get it to work. And I think this shows something subtle in the data model that is underneath the system.
Anyway Pictures will make this much more clear. Here is the model, and the settings for the two visuals:
Let me update this so it is even more clear. I will show you the time slicer that works (with its settings) the slicer that does not work, and the settings on the bar chart and the model.
Chart
Broken Slicer
Model
Good Slicer
"I wanted you to see the configuration of both the time slicer and the bar chart. That is the difference between top and bottom." - I'm sure this is obvious to you but it isn't obvious to me. Can you please explain what the difference is?
"Anyway Pictures will make this much more clear." - I don't think they do. What are we supposed to be seeing here? The top and bottom pictures look the same to me.
Also - there is an 'i' warning on the slicer. Can you investigate that as well please.
I wanted you to see the configuration of both the time slicer and the bar chart. That is the difference between top and bottom.
The "I" warning is about too many TimeKey values. Not surprizing, but it does not effect the TimeLine. But again, I did not want that visual to have to use TimeKey from Telemetry, but rather the Time Hierarchy from the HourTable Dimension, there woudl be far fewer values if I could use that.
Check out the July 2025 Power BI update to learn about new features.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
User | Count |
---|---|
70 | |
68 | |
43 | |
34 | |
26 |
User | Count |
---|---|
86 | |
49 | |
45 | |
38 | |
37 |