Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes! Register now.
Hello
I have made a custom table on Power BI that I want to filter with slicers on my report page. At the moment the slicers are not working for my custom table but are working as normal for the other tables on the page. I have attached the DAX code below that I'm using for my custom table. Any help would be v gratefully received!
@Greg_Deckler there are only two rows in my custom table which show MTD and YTD values respectively for different fields and my slicers contain date filtering information and department information and for that reason there won't be any matching values between the tables.
The values of the custom table are made up by measures which do work using filters within the rest of my report so I'm not sure why they don't work with the custom table. Unless there is some sort of DAX code that needs to be placed within the custom table syntax?
@tloup From the information you have presented I don't see how this is possible given how you constructed your calculated table. You don't have anything in your calculated table that relates to your slicers like Store or Week so there's no way to determine which store or week or anything else the data relates to. You would have to blow out your table with additional columns for store, week, etc.
Unless I am completely missing something, it seems like all you have is a calculated table with a single row for MTD and another for YTD so there's no way this will ever be able to be affected by your slicers because there is nothing to form relationships on or even do any kind of lookup.
@Greg_Deckler thanks for the reply and I think you have a fair point. What confuses me is that in my calculated table, all I am doing to fill cells is use measures that I've previously made for other tables and when I use these measures in a standard table format they become filtered by my slicer (in this case I am looking for MTD & YTD figures by store for the filtering). Why is it that when I create a calculated table the slicers don't affect figures but when I use the normal table they are?
There is a work around to this solution by using two different tables in standard format but this is not going to look as neet as a calculated table.
@tloup Did you create relationships between your custom table and the table where the slicers are coming from?