# Dynamic Tags using Multi-Select field

**URL:** <https://community.fibery.io/t/dynamic-tags-using-multi-select-field/3130>\
**Category:** Ideas & Features\
**Tags:** automations\
**Created:** [August 1, 2022, 4:05pm UTC](https://community.fibery.io/t/dynamic-tags-using-multi-select-field/3130 "2022-08-01T16:05:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dominic](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dominic/32/5348_2.png) [@Dominic](https://community.fibery.io/u/Dominic)\
**Post date:** [August 1, 2022, 4:05pm UTC](https://community.fibery.io/t/dynamic-tags-using-multi-select-field/3130/1 "2022-08-01T16:05:58Z")

</div>

Our team loves using multi-select fields on databases for displaying various “Tags” on entities such as “Urgent”, “Blocked”, “Archived”, etc. We like it because multi-select fields are flexible, easily readable, and don’t clutter views when not in use. Also , when updated, theses Tags fields can then be used in a variety of filters or automations.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/0/01f64449ec5db00127675bae3db7233086aa8a8d.png)

Here’s our problem :  
We would like to automate some of these tags and we can’t find a way to do it. For example if a “Task” entity is due for tomorrow, we would like to create a rule that ADDS the “Urgent” tag to the entity without deleting the previously applied tags.

Right now it seems like multi-select options are stored in a special type of database **which can’t be accessed through formulas or automations** and thus we are unable to create new rules for simply adding a new Multi-Select element to an entity without replacing everything.

We are aware that one easy solution for this would be to stop using Multi-Select fields and to create a “Tag” database that can be linked many-to-many to everything in our workspace. However we would loose the nice UX features multi-selects have, such emojis and color coding, single-line display on board cards, etc. so that isn’t a viable solution for us as it would affect readability and usability too much.

Here are 2 suggestions on how this could be fixed :

- Making multi-select databases accessible through formulas and relations
- Adding customizable database icons and colour coding options per entity in normal databases

Any thoughts? Thanks 😀!

---

<div class="post-metadata">

**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:** [November 27, 2023, 3:31pm UTC](https://community.fibery.io/t/dynamic-tags-using-multi-select-field/3130/2 "2023-11-27T15:31:13Z")

</div>

> [@Dominic](#):
>
> Adding customizable database icons and colour coding options per entity in normal databases

Just for the benefit of future readers, it is possible (since July) to add icons per entity:

> [@July 13, 2023 / Icons for Entities, search comments, better markdown import](https://community.fibery.io/t/july-13-2023-icons-for-entities-search-comments-better-markdown-import/4790):
>
> champagne Pick a custom icon for any Entity Add emoji icons for Entities of tag-like [Databases](https://the.fibery.io/@public/User_Guide/Guide/Databases-7) like Category, Status, or Team to make your workspace shine: [select-entity-icon] Many of you (and us!) have already put emojis in names. Now we’ve made sure the icons look alright throughout Fibery: in relations, search, history, etc. Icons are especially useful when you use regular Databases in place of [Select Fields](https://the.fibery.io/@public/User_Guide/Guide/Select-Field-87) (e.g. to share Status between Stories an…