![]() ![]() ![]() The end result was a new section of the report, dedicated to calling out slicer selections. Same report with additional section for slicer filter selection: The end result looked something like this So, I essentially wanted to do something similar here, but to call out the filter selection for each slicer. I actually did something similar to this with Dynamic Titles when I posted about Power BI’s new Drill Through feature last year, that article can be found here. The beautiful thing about DAX, as mentioned in many articles on our site, is that it can easily return text values. The client and I brainstormed, and we decided to create card visuals to identify filter selections. Primary sections for – Headers, Slicers, Visuals/Tables: Please click here to download the workbook to follow along. At the end of the day, we need to cater the report to the client’s needs. Truth be told though, it only partially matters what we think. Personally, I think a well-designed Power BI report has clear “enough” call-outs on the filters. Overall it comes down to this, data ambiguity can render a report A) Untrustworthy, B) Dangerous, or C) Useless. Now this is a scenario I’ve encountered a few times over the years, whether it’s been in Power BI, Excel, or other reporting tools. However, the client didn’t think the active filters in the report were easy to identify. I was working on a project for a client, and needed to create a Power BI report for them. I think it’s a scenario at least a few of you will relate to. Hello P3 Adaptive Nation, I’m excited to be back and writing a technical post again…it’s been too LONG! Today I want to talk to you about a real-world business problem and solution I encountered last year. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |