Single Selection Date Slicer not working as intended

[srlabhe]

Hi Team,

I am using the trick explained at link below for selecting single date from calendar to filter the table visual in report.

https://www.linkedin.com/pulse/power-bi-single-date-picker-without-dax-torsten-wanka/ 

Everything works fine, but when I select say 11/25/2025 in Calendar and try serching an ID in Visual Level Filter pane , it shows the IDS for historical dates as well like from 11/23/2025.

But If I just select a date and export in excel I cant find the same IDS in excel export.

Any ideas why it shows data for IDs in report selected for 11/25/2025 whild Ids are for 11/23/2025?

And how to restrict the Table visual tos how data only for selected date in Date Slicer Calendar?

I tried creating DAX and apply on visual but it throws "Query out of resources error" as my query has mor ethan 1.2M recs.

Appreciate your help here.

[srlabhe · Accepted solution]

Created a complex join in query based on date table and used the Date Table Date field in report and it worked well.Thanks for your help 

[v-karpurapud]

Hi @srlabhe 

I wanted to check if you’ve had a chance to review the information provided. If you have any further questions, please let us know. Has your issue been resolved? If not, please share more details so we can assist you further.

Thank You.

[Rufyda]

Quick fix for Single Date Slicer in Power BI:

Use a page-level filter instead of a visual-level filter:

Remove any ID filters from the visual.

Add Date[Date] as a page-level filter and select the desired date.

 Ensures the table shows only rows for the selected date without heavy DAX calculations.

Source:
Microsoft Power BI Community – Single Selection Date Slicer

Did it work? ✔ Give a Kudo • Mark as Solution – help others too!
Regards,
Rufyda Rahma | Microsoft MIE

[srlabhe]

Thanks but we need a Date Slicer on top tos elect a single date as part fo requirement

[v-karpurapud]

Hi @srlabhe 

Thank you for contacting the Microsoft Fabric community forum.
 

Seeing extra IDs in the visual-level filter list is normal when using a disconnected or trick-based single-date slicer, because Power BI shows all distinct IDs in the column, not only the ones for the selected date. The table visual and Excel export are still correct they reflect only the chosen date.

To make the single-date filter work properly and avoid resource errors, use a clean date-only column in your fact table and connect it to a proper marked Date table with an active relationship. This ensures the slicer filters the fact table accurately. If you need to search IDs, use an ID slicer instead of the visual-level filter, as it respects the date context and is lighter on performance.

I hope this information is helpful. If you have any further questions, please let us know. we can assist you further.

Best Regards.
 

[Anonymous]

Hi @srlabhe ,

Try below steps.

1.  Create this measure

SelectedDate =

SELECTEDVALUE('Calendar'[Date])

2.  Create this measure to check row date

ShowRow =

IF ( MAX('Fact'[Date]) = [SelectedDate], 1, 0 )

3. Apply it to the Table visual

Visual → Filters → “ShowRow” → is 1

This will give, table always shows only the selected date rows. No heavy calculation. No need for complex DAX.

No need to modify the date table trick.

If my response as resolved your issue please mark it as solution and give kudos.

[srlabhe]

This throws an error "Query out of resources error"

[Kedar_Pande]

@srlabhe 

Remove visual-level ID filter

Use page-level filter on Date = slicer selection instead

This forces table to respect single date strictly

If this answer helped, please click Kudos or Accept as Solution.
-Kedar
LinkedIn: https://www.linkedin.com/in/kedar-pande

[amitchandak]

@srlabhe , If date and table is connected it should show that data , If not a measure like this should help 

countrows(filter(Table, Table[Date] = selecteddate(Date[Date]) ) )