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

Don't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.

Reply
greyniall
Frequent Visitor

Slicer with timestamps in 2 seperate tables

Hi all,

 

For some reason I can't find out why my simple charts are not working. The only way the slicer works is if I use it to select all blank values. I created an simplistic example, as follows:

 

I created two tables: Table1 and Table2

greyniall_0-1665236944888.png

greyniall_1-1665236956812.png

 

Next I create a date dimension table (DimTable) as follows (all the way to 31/12/2022)

greyniall_2-1665237001945.png

 

Next I create the required relationship:

greyniall_6-1665237177305.png

 

 

 

Finally I create the two graphs and a slicer based on DimTable[Date]. So far so good. 

greyniall_3-1665237055322.png

 

Now if I use the slicer to select data, I either get all the data or none. If I use a different type of slicer, I see that there is a blank field which is where all the data is in. 

greyniall_4-1665237090892.png

 

Can anyone point me in the right direction? 

Thanks!

 

 

 

 

1 ACCEPTED SOLUTION

Hi @greyniall,

 

I guess you should do it. I really don't see the relevance of using a timestamp as a slicer. While you may have values for the same date, it is highly unlikely that you'll get matching values for the same timestamp. Also, how would you have every second of the day in your Date Dimension? That would 86,400 rows for one day. Imagine a dimension for 4-5 years🙂.

 

Did I answer your question? Mark this post as a solution if I did!

View solution in original post

6 REPLIES 6
Shaurya
Memorable Member
Memorable Member

Hi @greyniall,

 

I created 3 tables similar to yours and I am able to select part of the data using date from the dimension table as slicer.

 

Example:

 

Screenshot 2022-10-08 200345.jpg

 

Screenshot 2022-10-08 200250.jpg

 

The most probable reason why this is not happening in your report is because you are using bidirectional relationships which is not recommended while joining facts and dimensions.

 

Try this:

 

Screenshot 2022-10-08 200359.jpg

 

Mark this post as a solution if that works for you!

Thanks for your quick reply Shaurya! 

 

I tried changing the dimensions to one-way and it doesn't seem to help. I must be making a very stupid mistake somewhere along the way. Could you share your Pbx with me please? 

Hi @greyniall,

 

Hope you can download it from this link:

 

https://drive.google.com/file/d/1QNPmjk5yKrJyHdjwHCK8Jh5RrsQ03Pef/view?usp=sharing

 

Works for you? Mark this post as a solution if it does!

Thanks again Shaurya! 

 

The difference is: my data tables have times included whereas yours only have dates with 00:00:00 as time. That's why they match. It seems I may have to seperate the time and date to be able to filter them. Except, I want to have the time included on the xaxis in case one zooms in a lot. 

Hi @greyniall,

 

I guess you should do it. I really don't see the relevance of using a timestamp as a slicer. While you may have values for the same date, it is highly unlikely that you'll get matching values for the same timestamp. Also, how would you have every second of the day in your Date Dimension? That would 86,400 rows for one day. Imagine a dimension for 4-5 years🙂.

 

Did I answer your question? Mark this post as a solution if I did!

Thanks again. There are other ways I have found. Basicely you create a date and time dimension table seperately and link them. And then e.g. use two sliders. But for now, converting timestamps to just dates works OK I guess. Cheers!

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!

Jan25PBI_Carousel

Power BI Monthly Update - January 2025

Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.

December 2024

A Year in Review - December 2024

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