Slicer issue with weekend date selection

Hi anonymous2967 ,
I understand that you are facing a slicer issue with weekend date selection, to the best of my understanding, the issue you're facing is due to how the slicer reacts when weekend dates (which might not have data) are selected, even though users have KPI targets within that month.

The DAX solution I am sharing should help. However, since I haven’t seen your actual Power BI file and data structure, it would be much better if you could provide access via Google Drive. That way, I can review it more accurately.

💭 Assuming:

• KPI table includes columns: UserID, Date, Target

• Users table includes: UserID, UserName

• Date table includes: Date, Month, Day, IsWeekend (optional)

• Relationship:

  • KPI[Date] → Date[Date]

  • KPI[UserID] → Users[UserID]

  • Contact is not directly relevant unless it filters users
    
    

✅Calculated Table DAX Solution (for Slicer):

Create a new table for slicer that only includes users with a target in the selected month:

UsersWithMonthlyTarget = 
VAR SelectedMonth =
    SELECTEDVALUE('Date'[Month]) -- or use MonthNumber or Month-Year as needed
RETURN
FILTER (
    Users,
    CALCULATE (
        COUNTROWS (KPI),
        FILTER (
            KPI,
            MONTH (KPI[Date]) = SelectedMonth
            && NOT ISBLANK(KPI[Target])
        )
    ) > 0
)

This ensures that only users with a KPI target in the selected month will show in the slicer, even if a weekend date is selected.

💡 Alternative (If Using Measure Instead in Visual):

If you want to keep your existing slicer but make usernames appear even when weekends are selected, you can modify the filtering behavior using a measure like:

HasTargetThisMonth = 
CALCULATE (
    COUNTROWS (KPI),
    FILTER (
        KPI,
        MONTH (KPI[Date]) = MONTH(SELECTEDVALUE('Date'[Date]))
            && NOT ISBLANK(KPI[Target])
    )
)

Then filter the slicer using a visual-level filter: HasTargetThisMonth > 0

Notes:

• This won't require any change to the underlying data model or relationships.

• Works dynamically with your existing slicers for date/month.

• If your Date table has Month-Year, use that for better precision (not just month number).
  
  

⭐Hope this solution helps you make the most of Power BI! If it did, click 'Mark as Solution' to help others find the right answers.
💡Found it helpful? Show some love with kudos 👍 as your support keeps our community thriving!
🚀Let’s keep building smarter, data-driven solutions together! 🚀