Forum Discussion
Date Slicer on Direct Lake Semantic Model does not work since yesterday
When I make a selection on a Date Slicer all Measures in Visuals are empty. This happens in visuals where another field from Calendar Dimension is used. This happens in Service and in Desktop.
Since the day before yesterday that worked fine. No changes on report or semantic model.
Only when I clear the Date Slicer, data is shown in those visuals.
In my helpless trial-and-error efforts, I happened to discover that the month field (type: date) and the calendar week field (also date) did indeed work in the slicer. So I figured I’d just create another field for the day. To do that, I had to recreate the calendar data mart table (because of “Direct Lake”). And that was it. After that, everything worked again. So somewhere in the Fabric data warehouse, some bit had gotten out of place. I didn’t even need to use the new field after all...
Since some measures had worked but others hadn’t, it hadn’t occurred to me earlier that the calendar table could be the cause...
The whole thing cost me three days. But it was undoubtedly a glitch on Microsoft’s end. /o\
3 Replies
Hi carsten_cohrs,
Thank you for reaching out to Microsoft Fabric Community.
Since the report was working correctly before, no changes were made to the semantic model and the issue occurs in both desktop and the service, this does not looks like a report or DAX issue.
- First try refreshing the direct lake semantic model to ensure its metadata is up to date. If the issue persists, this is most likely a direct lake service side issue or regression rather than a configuration problem.
In that case, please open a Microsoft Fabric Support ticket so the engineering team can investigate the backend behaviour.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thanks and regards,
Anjan Kumar Chippa
This is still open as the support ticket was not successful so far.
It happes in a procuction environment of a customer and leeds to enourmous discrepancy.
In my helpless trial-and-error efforts, I happened to discover that the month field (type: date) and the calendar week field (also date) did indeed work in the slicer. So I figured I’d just create another field for the day. To do that, I had to recreate the calendar data mart table (because of “Direct Lake”). And that was it. After that, everything worked again. So somewhere in the Fabric data warehouse, some bit had gotten out of place. I didn’t even need to use the new field after all...
Since some measures had worked but others hadn’t, it hadn’t occurred to me earlier that the calendar table could be the cause...
The whole thing cost me three days. But it was undoubtedly a glitch on Microsoft’s end. /o\
