# 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:** 3

<div class="post-metadata">

**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\
**Post date:** [January 5, 2024, 6:52pm UTC](https://community.fibery.io/t/rules-conditions-for-update-action-on-one-to-relations/5621/3 "2024-01-05T18:52:33Z")

</div>

Thanks for the options:

> [@Chr1sG](#):
>
> - including a filter in the trigger for the automation (may require a lookup/formula field in the original db)
> - incorporating the condition in the update action via a formula

I think the lookup from the original db is the only option I have since the field I am trying to update is a single-select field (per [Setting dropdown value via formula](https://community.fibery.io/t/setting-dropdown-value-via-formula/5557), we can’t use a formula for setting the value).

I guess the third option is using a script to do all the update steps in one 🙂

Is there any value in creating a feature request for this or is there an underlying limitation which makes this difficult?

---

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