This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
I'm working on creating a visual that states how many notices are resolved and how many notices are open. Each of these fields is a card, and use the measure below to pull the number of records with the Open or Resolved statuses:
Resolved Notices = calculate(count(tblNotice[noticeStatus]),tblNotice[noticeStatus]="Resolved")
Open Notices = calculate(count(tblNotice[noticeStatus]),tblNotice[noticeStatus]="Open")
For some reason, resolved notices updates correctly upon refreshing the data, but Open Notices stays at a value of one (which, it's worth noting, was never actually one to begin with as there were seven Open Notices when I originally loaded the table).
Any ideas why this could be acting up?
Solved! Go to Solution.
I think I've solved the issue actually--I had a brainstorm and realized the problem was a slicer I put in that was filtering on the resolution date. Oops!! And to think I spent an hour on this.
I have to guess that what you THINK says "Open" does not actually say "Open". Maybe a space before/after?
Only other thing I can say is that I tend to use COUNTROWS(tblNotice), instead of COUNT( ) -- but I don't *think* that makes any difference.
Thanks for your reply scottsen,
Not sure if this would change anything but I've noticed now that if I set a report level filer, the filter box does seem to acknowledge that there are 8 open notices. However the visual still reads "1". Does that make any difference?
I'm going to try playing with leading/trailing spaces now and see if that might have anything to do with it.
In your table, you could add a calculated column that is just IsOpen = tblNotice[noticeStatus] = "Open" and make sure you are getting a "TRUE" where you expect?
It's returning "true" for all values I expected 😕
I think I've solved the issue actually--I had a brainstorm and realized the problem was a slicer I put in that was filtering on the resolution date. Oops!! And to think I spent an hour on this.
Bam! Congrats 🙂
woah.
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
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 |
|---|---|
| 26 | |
| 25 | |
| 22 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 42 | |
| 41 | |
| 40 | |
| 21 | |
| 20 |