# Allow Rules to trigger "When linked entity is Updated"

**URL:** <https://community.fibery.io/t/allow-rules-to-trigger-when-linked-entity-is-updated/2927>\
**Category:** Ideas & Features\
**Tags:** automations\
**Created:** [June 8, 2022, 4:18pm UTC](https://community.fibery.io/t/allow-rules-to-trigger-when-linked-entity-is-updated/2927 "2022-06-08T16:18:42Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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 9, 2022, 2:45pm UTC](https://community.fibery.io/t/allow-rules-to-trigger-when-linked-entity-is-updated/2927/3 "2022-06-09T14:45:25Z")

</div>

@Chr1sG, yes there are existing workarounds.

The case for this is really about reducing complexity, i.e. not having to create additional lookups, and avoiding having to remember that a particular field is actually modified from a related entity (which is not how I like to build things). It’s a maintenance headache.

I have actually found myself _forgetting_ why I created a particular lookup or relation, and deleting it, only to (re)discover later that it was added it to perform some kind of work-around (usually in a script or rule).

If we were able to notate each field and DB, that would also help with this situation.

---

_[View the full topic](https://community.fibery.io/t/allow-rules-to-trigger-when-linked-entity-is-updated/2927)._