Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
I have a YOY measure using DAX with a filter for year to select only one year for a bullet chart KPI. It will display fine in a table but in the bullet chart it seems to ignore the year filter. I submitted the issue to Microsoft but in the mean time, I am looking for a work around. I was thinking possibly a DAX table that includes only the 2018 year I want to display could work but I haven't been able to get DAX syntax to work in this fashion. Open to any ideas.
Solved! Go to Solution.
Follow up - I was able to fix this by creating a DAX date table. Then I had to create a new field in the DAX table that was derived with a string formation of the date - "1/1/" & [Year]. Then that has to be converted to a date form. For some reason that is the only version of the field that plays well with the bullet chart. I did try that same process within my original data table but it wasn't working (I think because it wasn't continuous - but also because the heirarchy kept automatically getting put on it). Sorry I don't really understand why this worked or why it was necessary - but it is resolved for now.
Hi @ahumke
How do you structure your dataset?
Which columns do you add to the bullet chart?
Best Regards
Maggie
Follow up - I was able to fix this by creating a DAX date table. Then I had to create a new field in the DAX table that was derived with a string formation of the date - "1/1/" & [Year]. Then that has to be converted to a date form. For some reason that is the only version of the field that plays well with the bullet chart. I did try that same process within my original data table but it wasn't working (I think because it wasn't continuous - but also because the heirarchy kept automatically getting put on it). Sorry I don't really understand why this worked or why it was necessary - but it is resolved for now.
User | Count |
---|---|
98 | |
78 | |
77 | |
49 | |
26 |