and it looks kinda cool. I was going to take it out because I'm not sure what it could break, but I'm thinking about just leaving it there.
What would get tricky is someone having the emoji (unicode) at the beginning of their first or last name. Trying to search for a sunflower without knowing the unicode, or knowing that you need to search for it, could prove costly.
With them displaying that kind of adventurous spirit, you may want to keep an eye on that person for future volunteering or employment at the church
Their name happened to come up in a report grid module from a custom query, and the emoji is still there. Well, it looks fine on the page in Arena. It lost it and turned into code when I exported to excel ...no surprise.
But, I'm having one of those moments when you start thinking about the potential of this new found thing. I've used images of colored flags and tiny icons in report grids before to help highlight, identify, and summarize data. Looks like you could use emojis in some of those places. Hmmm.
After a few quick tests, it looks like you can use  followed by the rest of the emoji code after the 1F in HTML to display the emoji. For example:
CASE WHEN flower=1 THEN '🌻' ELSE '' END AS flower_when_needed
I am probably more excited about this than what should be normal. But, it's the little things.
It's little things that add some fun, attitude and color to drab pages. Thanks for figuring this out. I am already thinking about how I can use this too!
While this could be totally fun, it could also play havoc on things "under the hood" in certain places. As an example, I thought, "What if I change my system admin account to have a nickname of ?" I did. It's fun. However, that account can no longer access anything and I get a server side error. I can see it from a different login, but that account no longer can get into Arena. So, just be cautious about where and how you use it. I doubt it showing up as an output through a query will cause any trouble, but storing it in places could be problematic.