Looking for Solutions: Date Filter Not Functioning with M Query Parameter

[kteja]

Hi Fabric Community,

I’ve recently set up an M Query Parameter in Power BI with Snowflake as my database, using Direct Query mode. My requirement is to create a date filter where users can select a date and filter the data accordingly.

The challenge is that the date field is currently bound to the parameter, which prevents standard filters from working. I’ve tried a few workarounds, but ran into issues:

1. Creating a duplicate of the date column (not bound to the parameter) — but the data doesn’t match correctly.

2. Adding a custom column using the “Add Custom Column” option — again, the data doesn’t match.

3. Creating a new date column in DAX that references the bound date column — still results in mismatched data.

Data does match correctly when I use the native Power BI date slicer. However, this isn’t user-friendly for my scenario, since customers would need to scroll for several minutes just to pick a single date.

Could anyone suggest an alternative approach or a filter solution that would work in this case?

Thank you!

[v-nmadadi-msft]

Hi @kteja 

As we haven’t heard back from you, we wanted to kindly follow up to check if the suggestions  provided by the community members for the issue worked. Please feel free to contact us if you have any further questions.

Thanks and regards

[v-nmadadi-msft]

Hi @kteja 

May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.

Thank you

[v-nmadadi-msft]

Hi @kteja 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

[v-nmadadi-msft]

Hi @kteja ,
Thanks for reaching out to the Microsoft fabric community forum.

In Power BI desktop you will find slicer options in visual pane

From there you can change the date slicer from dropdown to any other mode of your choice

I hope this information helps. Please do let us know if you have any further queries.
Thank you

[Shahid12523]

Problem: M Query Parameters in DirectQuery filter data before it reaches Power BI, so standard slicers or DAX columns won’t work properly.

Solutions:

Separate Date Table + Relationship – Use a Date table not bound to the parameter; slicer filters fact table via relationship.

Start/End Date Parameters – Fetch only a date range via two parameters; users select dates via parameter UI.

Load All Dates – If dataset is small, remove parameter and use normal slicer.

Searchable Date Dropdown – Create a distinct date lookup table; use a slicer with search enabled for user-friendly selection.

Recommended: Use parameter to limit range + separate searchable Date table for efficient filtering.