Don't miss your chance to take the Fabric Data Engineer (DP-600) exam for FREE! Find out how by attending the DP-600 session on April 23rd (pacific time), live or on-demand.
Learn moreNext up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now
I got slicer on form which always add nonexistent blank value to check (blanks not exists in table).
I can override it with page selection filter, select all but (blank) value, but this is still UNSOLVED error 😞
For example, I got report group by years, and last year, slicer values was (blank), 2016 and 2017.
I skip (blank) by uncheck it in report filter.
This year 2018, we got new data, but I forget to check this selection to "add" 2018.
Report filter got uncheck (blank), check 2016, check 2017, UNCHECK 2018 !
Report is incorrect, because of "blank slicer" bug.
When it will be corrected, it's annoying to check every slider on every report whenever new search attribute is appear in any tables!
Hi @sekic,
This year 2018, we got new data, but I forget to check this selection to "add" 2018.
Report filter got uncheck (blank), check 2016, check 2017, UNCHECK 2018 !
Report is incorrect, because of "blank slicer" bug.
When it will be corrected, it's annoying to check every slider on every report whenever new search attribute is appear in any tables!
Instead of unchecking blank and checking the years manually, you should be able to use the Advanced Filtering Filter Type with "Show item when the value: is not blank" option to dynamically apply the report level filter in your scenario. ![]()
Regards
Hi, yes, I find same workaround before, but my question is why this bug appears?
Sometime my customers said that they "fill" all needed attributes in tables and they're right, and ask from me to show where is that row with "blank" or null value?
And sometime, blanks (null) value really exists in table. So, I will not accept "select all but blank" as solution, because it's allways risk to get incorect results from table.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 48 | |
| 45 | |
| 41 | |
| 20 | |
| 17 |
| User | Count |
|---|---|
| 69 | |
| 63 | |
| 32 | |
| 31 | |
| 25 |