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

The ultimate Microsoft Fabric, Power BI, Azure AI & SQL learning event! Join us in Las Vegas from March 26-28, 2024. Use code MSCUST for a $100 discount. Register Now

Reply
tommeboy
Frequent Visitor

Date Slicer NOT filtering correctly ?

I've got 3 slicers, 2 behave correctly, but a Year slicer I have works fine when set to ALL, but will not filter my GROUP SWITCH when Years are selected ?  (see image)

Untitled-3.jpg
How do I get the GROUP to recalc based on whats also selected in YEAR ?

Thx


8 REPLIES 8
tommeboy
Frequent Visitor

Bumping this thread as still cannot get this to work?

When set to YEAR = ALL the group counts are accurate,
But changing to 2021, they are not accurate

tommeboy
Frequent Visitor

Can you get to this ?
Sample Workbook 

tommeboy
Frequent Visitor

Here's what I was expecting (2 AVGs > 100)

tommeboy_0-1629651780882.png

 

tommeboy
Frequent Visitor

if this helps .. pretty simple data model

tommeboy_0-1629650963620.png

 

Hi @tommeboy ,

it is difficult to answer without having access to the report. Are you able to share the model here?

dim_client table
client_id,client_name,state
1,Client A,IL
2,Client B,CA
3,Client C,OH
4,Client D,CA

fact table
client_id,job_id,date,rev,hours,type
1,1,9/23/2020,44364,116,1
1,1,1/1/2021,44973,127,0
1,2,3/7/2020,53596,175,1
1,2,6/15/2020,7477,0,1
1,2,8/20/2020,0,155,1
1,3,8/20/2019,19594,117,1
1,3,11/28/2019,50113,197,1
1,4,2/1/2019,31001,173,0
1,4,5/12/2019,50331,73,0
1,5,4/7/2018,31980,200,0
1,5,7/16/2018,7134,78,0
1,5,10/24/2018,8164,104,1
1,6,2/1/2018,9486,115,1
2,7,3/15/2018,11721,99,1
3,8,6/15/2020,3283,118,0
3,8,9/23/2020,1575,69,1
3,8,1/1/2021,9581,20,0
1,9,3/7/2020,5818,115,1
2,10,11/28/2019,2263,163,1
4,11,8/20/2019,1328,150,1
2,12,5/12/2019,1893,33,0
2,13,2/1/2019,5196,45,0







I posted a link to the example .. it's tiny

below are the 2 datasets (also tiny) just for example
dim_client

client_idclient_namestate
1Client AIL
2Client BCA
3Client COH
4Client DCA


fact table

client_idjob_iddaterevhourstype
119/23/2020443641161
111/1/2021449731270
123/7/2020535961751
126/15/2020747701
128/20/202001551
138/20/2019195941171
1311/28/2019501131971
142/1/2019310011730
145/12/201950331730
154/7/2018319802000
157/16/20187134780
1510/24/201881641041
162/1/201894861151
273/15/201811721991
386/15/202032831180
389/23/20201575691
381/1/20219581200
193/7/202058181151
21011/28/201922631631
4118/20/201913281501
2125/12/20191893330
2132/1/20195196450


The data is super clean .. no blanks ect, so I know that's not the issue

It really comes down to the GROUP Calculated Column IS NOT respecting the YEAR slicer.
it does work fine for the other 2 slicers though (customer name and state) ?




Sample Workbook Sample Workbook  

Helpful resources

Announcements
Fabric Community Conference

Microsoft Fabric Community Conference

Join us at our first-ever Microsoft Fabric Community Conference, March 26-28, 2024 in Las Vegas with 100+ sessions by community experts and Microsoft engineering.

February 2024 Update Carousel

Power BI Monthly Update - February 2024

Check out the February 2024 Power BI update to learn about new features.

Fabric Career Hub

Microsoft Fabric Career Hub

Explore career paths and learn resources in Fabric.

Fabric Partner Community

Microsoft Fabric Partner Community

Engage with the Fabric engineering team, hear of product updates, business opportunities, and resources in the Fabric Partner Community.

Top Solution Authors