Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
leolapa_br
Resolver II
Resolver II

Report visual turns blank when dropping slicer with field under bind M parameter

To keep things short, I've put together the process I prepared in order to get to the following goal: an accounts payable (A/P) dashboard where the user gets to pick on a slicer the A/P report cut off date, and such slicer triggers an M parameter that filters out a direct query table, updating the dashboard.

Process.png

In order to test it I whipped up a quick table visual that lists all vendors and the payables total amount due for each vendor:

Table Visual.png

But as soon as I drop a slicer with the cut off dates so the user can select which report date they want to visualize, the table visual returns blank.

Table Visual With Slicer.png

So I refreshed the visual with Performance analyzer on, copied the query plan and pasted on DAX query view to realize the code starts calling the M parameter, underlined as a faulty code and thus returning blank results.

Table Visual DAX Query Plan.png

As soon as I get rid of that M parameter call the code returns valid results.

Table Visual DAX Query Plan, Removing M Par.png

What am I doing wrong that I just can't make it work? I followed the required steps by the dot and still can't make it work...

Thanks...

1 ACCEPTED SOLUTION
leolapa_br
Resolver II
Resolver II

I managed to solve the issue by switching the M parameter from date type to text type (and tweaking the filtering code on the date column), although date type parameter is not listed as unsupported, but that did the trick.

View solution in original post

3 REPLIES 3
leolapa_br
Resolver II
Resolver II

I managed to solve the issue by switching the M parameter from date type to text type (and tweaking the filtering code on the date column), although date type parameter is not listed as unsupported, but that did the trick.

MohamedFowzan1
Responsive Resident
Responsive Resident

Hi @leolapa_br 

From what I have checked, the expected interaction of the parameter in Real Time is the limitation.
https://learn.microsoft.com/en-us/power-bi/connect-data/desktop-dynamic-m-query-parameters

MohamedFowzan1_0-1754329082742.png

 




Could you try by reading the value from what is selected and if that works instead of pointing to the parameter directly
SelectedCutoff = SELECTEDVALUE('DateTable'[Date])

Hi @MohamedFowzan1,

 

I took a look at the Microsoft Learn article from the link you provided and it doesn't seem like I'm using any of the unsuported parameter types, filters or operations for that matter.

 

Also, following your suggestion I created a measure that captures whatever choice I make on the report page slicer:

Data_Base_Sel = SELECTEDVALUE(Data_Base_Lista[Data-base])

It looks like your measure suggestion calls the SELECTEDVALUE function against the Date column from the calendar table. My measure instead calls SELECTEDVALUE against the date column from the table of cutoff dates, which is another table apart from the calendar table and the one I'm actually using for the slicer.

 

Anyways, I then dropped that measure to a card visual and the card works just fine as per the screenshot below:

Report Page With Card Visual.png

Helpful resources

Announcements
August Power BI Update Carousel

Power BI Monthly Update - August 2025

Check out the August 2025 Power BI update to learn about new features.

August 2025 community update carousel

Fabric Community Update - August 2025

Find out what's new and trending in the Fabric community.