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

Be one of the first to start using Fabric Databases. View on-demand sessions with database experts and the Microsoft product team to learn just how easy it is to get started. Watch now

Reply
emmasd
Regular Visitor

slicer not affecting my other visuals

Hi,

I have tables as below:

emmasd_0-1720019590265.png

 

each table has a "Symbol column" and the relationships are as below:

emmasd_1-1720020120748.png

All tables are connected to information by "Symbol"

 

My slicers are only interactive if I use columns from the information table, I can not move the column "date" to the information table because the "Symbol" column in "Information" has unique values which is not the case in the "annual BS" and "annual IS" because each symbol has different values on different date as below:

emmasd_2-1720020559806.png

 

The date slicer only works with either the "annual BS" if I use the date column from the same table, but it does noty interact with the other tables and visuals.

Also I checked the edit interactions under format and all is good there .

Any ideas???

 

1 ACCEPTED SOLUTION
Shosher
Regular Visitor

Your relationship from the Date table to your central table is wrong. A date table should have one unique date for each row between a set date range. It is what is known as a dimension used to filter your facts. The facts would be in this case your central table. so the relationship should be always Date One -> Central table many. 

If for some reason you arent able to fix this right now because of date constraints we cannot see you can fix this right now by setting the filter direction in your date <- information relationship to both. This should fix it for now. You from that point on shouldnt really connect the date table to anything else because ambigious routes can and will exist!

 

View solution in original post

2 REPLIES 2
Shosher
Regular Visitor

Your relationship from the Date table to your central table is wrong. A date table should have one unique date for each row between a set date range. It is what is known as a dimension used to filter your facts. The facts would be in this case your central table. so the relationship should be always Date One -> Central table many. 

If for some reason you arent able to fix this right now because of date constraints we cannot see you can fix this right now by setting the filter direction in your date <- information relationship to both. This should fix it for now. You from that point on shouldnt really connect the date table to anything else because ambigious routes can and will exist!

 

MFelix
Super User
Super User

Hi @emmasd ,

 

Since the relationship is going from the Information table to the Date table the filter is only allowed in one direction so when you filter on dates it won't filter on the Information table that would filter other tables.

 

You need to check if the relationship is correct.

 

If you have a single date value on the Date table try to reverse the relationship from 1(information) to many  (Date) and be 1( Date) to many (information)


Regards

Miguel Félix


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

Proud to be a Super User!

Check out my blog: Power BI em Português



Helpful resources

Announcements
Las Vegas 2025

Join us at the Microsoft Fabric Community Conference

March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!

Dec Fabric Community Survey

We want your feedback!

Your insights matter. That’s why we created a quick survey to learn about your experience finding answers to technical questions.

ArunFabCon

Microsoft Fabric Community Conference 2025

Arun Ulag shares exciting details about the Microsoft Fabric Conference 2025, which will be held in Las Vegas, NV.

December 2024

A Year in Review - December 2024

Find out what content was popular in the Fabric community during 2024.