The Custom Picker Field only offers plaintext in its pop-up suggestions, with no particular plans to change that as far as I know.

My suggestion to you is, consider using the new (19.2+) paging / "Read-Only" grid to create a picker for yourself, as this grid is capable of using the full capabilities of the Rich Text Display Field component, including rich text icons, colors, images, etc.  If you would like to do this but need to keep the ability to allow the user to search for the required item via a text search, my normal trick is to just have a "filter" text box right above or right below the grid which instantly filters down the grid's contents as the user types.

Hello Mike,

Thank you for you answer !

I tried with the read-only and an input text and it's working fine.

Regards,

Bruno.

great, thanks for confirming - if you'd be willing, it would be great if you could upvote and/or verify my suggestion above 

You suggestion works fine, but the behavior is not exactly the same.

When the grid is displaying data, all components bellow move down. When I use a picker, choices are displayed over the other components. 

bmarie said:

but the behavior is not exactly the same

i agree- my method is definitely a workaround; since we can't display icons/pictures in a Custom Picker, then when showing icon/pictures is more important than having the original functionality of the custom picker, it can be used as a viable alternative.

If you're OK with line drawings, you could use the char() function to display emoji via unicode characters.  Chrome and other browsers support full-color emoji renderings, though it often has more to do with the OS than the particular browser.

If your users are going to be accessing your application on multiple devices, they may see the emoji rendered differently, and some aren't supported on some browsers but are on others.

For instance, none of these are displayed like I would expect on my browser, to some degree maybe nicer than I expected.  On my own Appian environment they wouldn't do this, and the Mexican flag on the end wouldn't be supported at all.

If it works, and the icon is good enough for your purposes, you just need to find the Unicode code point value for the icon you want, convert that to decimal (they're usually presented in hexadecimal value) and plug that into the char() function.  In chrome most will be rendered in full color, but other than that treated no differently than any other letter.

That means you can add the emoji to the text of your picker, and still use the default custom picker component with the full-color emojis.

If you're OK with line drawings, you could use the char() function to display emoji via unicode characters.  Chrome and other browsers support full-color emoji renderings, though it often has more to do with the OS than the particular browser.

If your users are going to be accessing your application on multiple devices, they may see the emoji rendered differently, and some aren't supported on some browsers but are on others.

For instance, none of these are displayed like I would expect on my browser, to some degree maybe nicer than I expected.  On my own Appian environment they wouldn't do this, and the Mexican flag on the end wouldn't be supported at all.

If it works, and the icon is good enough for your purposes, you just need to find the Unicode code point value for the icon you want, convert that to decimal (they're usually presented in hexadecimal value) and plug that into the char() function.  In chrome most will be rendered in full color, but other than that treated no differently than any other letter.

That means you can add the emoji to the text of your picker, and still use the default custom picker component with the full-color emojis.

Hello,

Thanks for your reply.

works fine too.