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.
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.
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.
I was going to play with using them in column headings on RGFQs. Good to have the heads up on not using it in names or accounts.