Microsoft is giving away 50,000 FREE Microsoft Certification exam vouchers!
Enter the sweepstakes now!See when key Fabric features will launch and what’s already live, all in one place and always up to date. Explore the new Fabric roadmap
hi everyone, I have one problems where I have a date range filter in my report using transaction date in Db. this filter is not impacting the table visual as in I edit interaction and select None for table visual. I only want to use this date filter in my leave calculation (example for transaction type = carryover, entitlement, expiry, etc).
however, I cant get the calculation to honour the selected date range. says I want to calculate the expiry leave between Jan 1, 2025 - Jan 31, 2025.. it will sum up all expiry transaction type records in the table. how do I fix this or anyone has any idea how to make it work?
I've tried with calculated column and measure but both doesnt seems to work
Hi @farhanaizzatie,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like you want a date range slicer based on "Transaction Date" to only impact your leave calculation (like for Transaction Type = "expiry") and not affect the table visual. You did the right thing by using Edit Interactions -> None on the table visual, so the slicer doesn’t filter it directly. That part’s perfect. However, for your measure to actually respond to the date range, your DAX needs to explicitly reference the slicer context, because disabling visual interaction doesn’t stop the slicer from affecting the model, it just stops it from filtering that visual.
You can try this DAX measure:
ExpiryLeaveInDateRange :=
CALCULATE (
SUM ( Transactions[LeaveAmount] ), -- Or whatever column you’re summing
Transactions[TransactionType] = "expiry",
FILTER (
ALL ( Transactions[TransactionDate] ),
Transactions[TransactionDate] >= MIN ( Transactions[TransactionDate] )
&& Transactions[TransactionDate] <= MAX ( Transactions[TransactionDate] )
)
)
Here "ALL ( Transactions[TransactionDate] )" removes any existing date filters (important if you later want full control) while MIN and MAX re-apply the slicer’s selected date range dynamically. This lets your measure honor the slicer even if the slicer doesn’t visually filter the table.
I would also take a moment to thank @Deku, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support Team
If this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Ok, from my understanding
The problem is because the interation is set to None, there is no date filter context on the table for the leave measure to pick up.
Since you are creating a leave calculation, you should be turn the interation back on. You can get the filtered rows to reappear with the measure. in the measure you can use CALCULATE( , REMOVEFILTER( Date ) ) to remove the effect of the date slicer. With VALUES( date[date] ) you can grab all the dates from the slicer for use in your calculation
Cant comment without having a understanding of your semantic models structure
hi @Deku , let me share my report structure.
I have one table with leave transaction details and a custom table where I create the calendar table
User | Count |
---|---|
91 | |
74 | |
71 | |
58 | |
55 |
User | Count |
---|---|
41 | |
38 | |
34 | |
32 | |
30 |