# Rules can't trigger on updated many:many Relation field

**URL:** <https://community.fibery.io/t/rules-cant-trigger-on-updated-many-many-relation-field/2924>\
**Category:** Bugs & Issues\
**Tags:** automations\
**Created:** [June 7, 2022, 4:32pm UTC](https://community.fibery.io/t/rules-cant-trigger-on-updated-many-many-relation-field/2924 "2022-06-07T16:32:29Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [June 7, 2022, 4:32pm UTC](https://community.fibery.io/t/rules-cant-trigger-on-updated-many-many-relation-field/2924/1 "2022-06-07T16:32:29Z")

</div>

When creating a Rule and selecting which changed-fields it should trigger on, I cannot select a many:many relation field.

**Use case:** I have a `Tags` DB, linked as a many:many relation to various (many) other DBs. I would like a Rule to will trigger when I add/remove/change the Tags on an entity in a particular DB. Or, when a particular Tag is added to/removed from any entity.

---

<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:** [June 7, 2022, 9:56pm UTC](https://community.fibery.io/t/rules-cant-trigger-on-updated-many-many-relation-field/2924/2 "2022-06-07T21:56:57Z")

</div>

I think this should work using the ‘Entity linked…’ trigger (or ‘Entity unlinked…’)

---

<div class="post-metadata">

**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\
**Post date:** [June 7, 2022, 10:32pm UTC](https://community.fibery.io/t/rules-cant-trigger-on-updated-many-many-relation-field/2924/3 "2022-06-07T22:32:03Z")

</div>

Ugh, not the first time I tripped over this 🙄

It’s very unintuitive that I can’t just use “Entity Changed” to detect this.

And I need two separate Rules - one for linked, one for unlinked.

---

<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:** [June 8, 2022, 6:05am UTC](https://community.fibery.io/t/rules-cant-trigger-on-updated-many-many-relation-field/2924/4 "2022-06-08T06:05:22Z")

</div>

It’s true that it would be nicer if ‘linked’ and ‘unlinked’ triggers could be combined.  
However, they differ slightly from ‘updated’ in that the item added/removed is passed as a parameter to the next steps (s well as the triggering entity).