A few weeks ago I wrote an article “Conditional Formatting Using Icons In Power BI” about the Power BI Icon feature released in July 2019.
There were 2 common questions/themes coming from readers’ comments, and I want to address those here.
Where can I find a list of Power BI Icon Names?
As I pointed out last time, it is possible to refer to the icons inside a measure by name.
Icon Set Measure = SWITCH( TRUE(), [% Change vs Prior Year] < 0, "data:image/svg+xml;utf8, <svg xmlns='http://www.w3.org/2000/svg' x='0px' y='0px' width='100' height='100' viewBox='0 0 100 100'> <circle cx='50' cy='50' r='40' stroke='purple' stroke-width='4' fill='purple' /> </svg>", [% Change vs Prior Year] < 0.4, "StarMediumLight", "https://i.gifer.com/Omjx.gif" )
In the measure above, note the reference to the standard icon “StarMediumLight”. The above switch measure will return
- An SVG icon if [% Chg vs Prior Year] is less than 0,
- The standard icon “StarMediumLight” if it is less than 0.4,
- Otherwise an animated gif file.
You can see the results below.
The benefit of this approach is you can leverage all the standard icons and then add you own icons as well, effectively extending the default icon set. But where can I find a list of all the names of the standard icons?
I asked this question in the Power BI Blog thread (as did some others). A list of names was provided by Francisco Mullor in the comment section of that blog post (sorry, I can’t seem to link to the exact comment). I have taken the information provided by Francisco and produced the following Power BI report.
You can download the list of names from within the report. I also created a shortcut URL to quickly return to the report if you want to https://xbi.com.au/icons
SVG Images Not Rendering at PowerBI.com
The other common issue I heard about what that sometimes the SVG code used to create an icon was not working when the workbook was published to PowerBI.com. The problem occurs because some browsers are not able to correctly interpret the hash # icon in the SVG code as shown below.
There is a simple fix – just replace the hash # character with %23 as follows:
In my testing, this fixes the problem.