# Rules - Conditions for update action on one-to-\* relations

**URL:** <https://community.fibery.io/t/rules-conditions-for-update-action-on-one-to-relations/5621>\
**Category:** Get Help\
**Tags:** automations\
**Created:** [January 4, 2024, 12:19am UTC](https://community.fibery.io/t/rules-conditions-for-update-action-on-one-to-relations/5621 "2024-01-04T00:19:52Z")\
**Posts on this page:** 1\
**Showing post:** 4

<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:** [January 5, 2024, 10:11pm UTC](https://community.fibery.io/t/rules-conditions-for-update-action-on-one-to-relations/5621/4 "2024-01-05T22:11:56Z")

</div>

> [@cannibalflea](#):
>
> Is there any value in creating a feature request for this or is there an underlying limitation which makes this difficult?

There is no underlying limitation, but rather that in most cases, a filter only makes sense if you want to update (or delete or whatever) a subset of linked items, therefore it is meaningless for to-one relations.

It would be solved if/when there was the option to [define trigger filters using formulas](https://community.fibery.io/t/to-be-able-to-use-formula-in-automation-filters/3706), in which case, you would only trigger the automation in the case where the related entity meets the required criteria.

In your case, the current workaround is a lookup / formula field on the triggering entity.

---

_[View the full topic](https://community.fibery.io/t/rules-conditions-for-update-action-on-one-to-relations/5621)._