This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
Hi All,
I have a report which shows several metrics related to service events. One of the slicers used is a date filter which allows our end users to filter based on the date in which the service event was updated. This works fine for those events that have been updated, however, this causes new/untouched events to be excluded from the report (since they do not have an "Updated Date" yet). Is there any way for an end user (in Service) to exclude this slicer? If the user blanks out the date range, the values simply default to the first and last dates in the data set, preventing those new events from displaying.
Thanks!
Matt
Very dependent on use case, you could potentially create a measure which ignores the slicer but not sure if you want this for all users, particular users, all the time, some of the time. A nice note on the report or a comment in the Service might go a long way towards user education?
Hi Greg,
Unfortunately, I don't think that will work with my situation. We have records such as:
ID Upload Date Summary Update Date
1 11/15/2019 Event 11/20/2019
2 11/15/2019 Event
3 11/15/2019 Event 11/21/2019
4 11/15/2019 Event 11/18/2019
5 11/15/2019 Event
Our users need the ability to filter on both Upload Date and Update Date. Because of this, I have slicers for each, allowing the user to enter a date range. However, if they want to see all events that were uploaded on 11/15, they cannot do this. They can select that date range for that slicer, however, since two of the records have yet to be updated, regardless of the date range they enter for Update Date, those two "new" events do not show in the result set.
Thanks,
Matt
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 11 | |
| 10 | |
| 9 | |
| 8 | |
| 8 |
| User | Count |
|---|---|
| 49 | |
| 27 | |
| 25 | |
| 20 | |
| 20 |