Forum Discussion
Compatibility Issues with Special Symbols Between Power Query and Power BI
No, these aren't all from the same family of characters. Unicode characters are allocated into 'Blocks' and 'Planes'. Both 10004 and 10060 are in the '0 BMP' Plane, and the 'Dingbats' block. 11093 is also in the '0 BMP' Plane, but in the 'Misc Symbols and Arrows' Block. More info on this can be found here:
https://en.wikipedia.org/wiki/Unicode_block
Therefore, it seems that Power Query does not contain all unicode characters within its 'language' set. It's not a bug. If it were up to me, PQ wouldn't contain any Unicode characters as it's just not designed for graphical output like this.
If you're really into using unicode symbols for reporting, I've attached a PBIX I made that you might find interesting/helpful. It picks up the latest unicode list from the link above, converts the codes from Hex to Decimal, and attempts to display them all in PBI with search capabilities. Enjoy 🙂
Pete
Hi Gino ,
While Power Query correctly displays both ⭕ and ❌, Power BI’s data model appears to misinterpret or simplify certain Unicode characters (like ⭕) during the data load, leading to inconsistent rendering.
We agree that while the workaround is effective, it doesn’t fully resolve the underlying issue.
For now, we’ll proceed with closing this thread.Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread or reopen this thread. We’ll be happy to help.
Thank you for your understanding and participation.
Hi Gino,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
When a column contains both ⭕ and ❌ values, everything looks fine in Power Query. But once the data is loaded into Power BI, all values in that column are displayed as ⭕.
If I replace ⭕ with ✔️, both ✔️ and ❌ display correctly in both PQ and PB.
This issue still persists. While it's now possible to work around it, that doesn’t mean the problem has truly been fixed.
