# July 13, 2023 / Icons for Entities, search comments, better markdown import **URL:** \ **Category:** Changelog\ **Created:** [July 13, 2023, 4:27pm UTC](https://community.fibery.io/t/july-13-2023-icons-for-entities-search-comments-better-markdown-import/4790 "2023-07-13T16:27:37Z")\ **Posts on this page:** 1\ **Showing post:** 17
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 27, 2023, 6:17am UTC](https://community.fibery.io/t/july-13-2023-icons-for-entities-search-comments-better-markdown-import/4790/17 "2023-09-27T06:17:19Z")
Have a look at this: > [@Set Icon via Formula](https://community.fibery.io/t/set-icon-via-formula/5190/2): > > I think the problem is that there is a difference between the Icon field and a field with the name Icon. As an analogy, if you create a field called State, you won’t be able to add the Workflow field, since it has to have the name State and that name is now already taken. This doesn’t mean that the field you created will function in the same way as the native workflow field. Similarly, if you define a (formula) field called Icon, you are prohibiting yourself from using the native Icon function… Lookups effectively behave like formulas, so getting an Icon from another entity will not mean that the resultant field behaves like a ‘native’ icon field. --- _[View the full topic](https://community.fibery.io/t/july-13-2023-icons-for-entities-search-comments-better-markdown-import/4790)._