Hello,
The Microsoft community has identified a major error with PowerBI. This error relates to using date slicers. For some users, when we input a date slicer, it causes other visualizations to error out. In the first picture below, you can see an example. This is with the date slicer. In the second picture, the only difference is that I've deleted the date slicer.
This problem does not occur if you use other means to filter down to a date range (E.g. drilling down on a line chart), it only occurs when there is a date slicer present. I am using a Windows Surface Pro 11 and the May 2025 version of PowerBI. Comments in the thread below indicate that microsoft is aware of this issue but there is no timeline to fixing it. There is no reason why a customer using the latst version of PowerBI and the latest Microsoft computer cannot reliably use one of the most basic features of PowerBI. This should be a priority 0 issue for Microsoft.
- RaphaelBNeto on: Allow Conditional Formatting on Matrix Labels to T...
- excel_enjoyer93 on: Python and R visuals supported in "Publish to web"...
- bmorante on: Managed Identity for Fabric items
-
nschachter
on:
Tags/Labels to structure all fabric content
-
nschachter
on:
Tags and Status Counts to the Power BI Monitor Tab
-
rocketporg
on:
Fabric free trial
- szig on: Data limit suddenly causes error in table visual. ...
- Chris_GSD on: Allow Optional ‘End Date’ for Semantic Model Sched...
- pistachiogod on: MS Fabric Connections in Notebook
-
OldDogNewTricks
on:
Expose User Prompt and Agent Response Logs for Fab...