Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by watching the DP-600 session on-demand now through April 28th.
Learn moreJoin the FabCon + SQLCon recap series. Up next: Power BI, Real-Time Intelligence, IQ and AI, and Data Factory take center stage. All sessions are available on-demand after the live show. Register now
When I add a date slicer to the report (marked as a Date Table) almost all of the data disappears from the column chart, even when all dates are selected with a slider control. There are approximately 1,800 records it should be capturing, but this is reduced to 36 records after adding the slicer.
This is the relationship between the tables:
I've used the Performance Analyser to try to find out what's happening when I add the slicer, and it produced the following output:
I cannot work out why the vast majority of records fail to be captured, the date slicer captures the full range of dates. Both the slicer date and the date in the table the chart is modelling are of 'Date' type (not 'Date/Time').
Is there anything I need to be aware of when using Direct Query for Dataverse tables that might be causing the problem?
Any advice would be gratefully appreciated.
Check out the April 2026 Power BI update to learn about new features.
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.
| User | Count |
|---|---|
| 41 | |
| 37 | |
| 34 | |
| 21 | |
| 16 |
| User | Count |
|---|---|
| 64 | |
| 58 | |
| 31 | |
| 25 | |
| 25 |