Slicer don't working , didn't filter my table

[Jatin_Sharma]

Please help me to understand why it is not working and how I fix it .

I have two tables 

Dim_customer

Age_group

Avg_income

City

Customer_id ( primary key)

Gender 

Marital status 

Occupation 

Fact_spend ( 2nd table)

Category 

Customer_id (foreign key)

Month

Payment_type

Spend 

I made visuals 

Total customers by age group 

Total customers by city

By marital status

By occupation 

Cards - total customers, toatal transaction, female customers, male customers 

But when I put any column from fact_spend table for use them as slicers or filters then they don't filter any of my visual , only Total transaction card filter but only one time example of I choose credit card option then total transaction changes but when I choose or change it to any other then same problem nothing change , it don't work .

Please help .

[v-lgarikapat · Accepted solution]

Hi @Jatin_Sharma ,

Thanks for reaching out to the Microsoft fabric community forum.

 @Ilgar_Zarbali , @johnbasha33 Thanks for your prompt response

@Jatin_Sharma  

To help us understand your issue better, please share sample data that clearly shows the problem (in text or table format, not a screenshot), without including any sensitive or unrelated information, and also show the expected result based on that data. If possible, share the PBIX file as well, provided it doesn’t contain any sensitive information.

Looking forward to your response.

Best Regards,

Lakshmi Narayana

[v-lgarikapat]

Hi @Jatin_Sharma ,

I wanted to follow up and confirm whether you’ve had the opportunity to review the information  provided by @Ilgar_Zarbali , @johnbasha33 . If you have any questions or need further clarification, please don’t hesitate to reach out.

Best Regards,

Lakshmi.

[v-lgarikapat]

Hi @Jatin_Sharma ,

I just wanted to check if your issue has been resolved. If you still have any questions or need help, feel free to reach out I’m happy to assist.

Thank you for being an active part of the community. Looking forward to hearing from you!

Best regards,
Lakshmi

[v-lgarikapat]

Hi @Jatin_Sharma ,

I just wanted to check if your issue has been resolved. If you still have any questions or need help, feel free to reach out I’m happy to assist.

Thank you for being an active part of the community. Looking forward to hearing from you!

Best regards,
Lakshmi

[Ilgar_Zarbali]

Thanks to @johnbasha33 for sharing helpful guidance!

The main issue is likely because your visuals and most of your cards are based on the Dim_Customer table, but your slicers come from the Fact_Spend table. Slicers can only filter visuals if there’s an active relationship between the fields used and the data in visuals.

•  Solution: Use fields from Dim_Customer in your slicers instead of Fact_Spend, or create visuals using fields from Fact_Spend too.

Also, double-check that the relationship between Dim_Customer[Customer_id] and Fact_Spend[Customer_id] is active and set to single direction unless you need bi-directional.

•  If this answer helps, kindly give kudos and mark it as a solution.

[johnbasha33]

@Jatin_Sharma 

This usually happens because of incorrect or inactive relationships in your data model. Your current setup is:

Dim_customer (Dimension Table)

• Primary key: Customer_id

• Contains demographic details

Fact_spend (Fact Table)

• Foreign key: Customer_id

• Contains transactional data

When you add slicers from Fact_spend (e.g., Payment_type) and visuals from Dim_customer, filtering won’t work unless the relationship between the two tables is:

1. Properly defined

2. Set to filter in the correct direction
   
   

   1. Check the Relationship in Model View

   • Go to Model View in Power BI (or your data tool).

   • Ensure there is a relationship:

     • Dim_customer[Customer_id] → Fact_spend[Customer_id]

     • Cardinality: One-to-Many (1:*)

     • Cross filter direction: Should be Single or Both (preferably Both for slicers to work across both tables).

   👉 Fix:

   If the cross-filter direction is Single (default from Dim_customer to Fact_spend), slicers from Fact_spend won’t affect Dim_customer. Change it to Both:

   • Double-click the relationship line.

   • In the dialog box, set Cross filter direction to Both.

Click OK.

Check the Fields in Your Slicers

• Make sure the slicer uses fields from Fact_spend only.

Don’t mix dimensions (like age group from Dim_customer) with fact slicers without proper relationships.

Test the Slicer

• Create a new table visual with:

  • Customer_id from Dim_customer

  • Spend from Fact_spend

• Now apply the slicer using Payment_type from Fact_spend.

If the relationship is correct and cross-filtering is enabled, the visual should update.

Consider a Star Schema Design

Make sure you're following a star schema:

• Dim_customer is a lookup table.

• Fact_spend is the transactional table.

• The relationship should flow from dimension to fact.

Do not put slicers from fact tables unless you're sure about relationships.

Advanced Tip (if needed): Use DAX Measures

If you're using measures like Total Customers, ensure it's defined with context awareness, e.g.:
Total_Customers = DISTINCTCOUNT(Dim_customer[Customer_id])

Did I answer your question? Mark my post as a solution! Appreciate your Kudos !!