# How to assign relations to child entity on creation?

**URL:** <https://community.fibery.io/t/how-to-assign-relations-to-child-entity-on-creation/1489>\
**Category:** Get Help\
**Created:** [March 27, 2021, 1:40am UTC](https://community.fibery.io/t/how-to-assign-relations-to-child-entity-on-creation/1489 "2021-03-27T01:40:29Z")\
**Posts on this page:** 1\
**Showing post:** 16

<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:** [April 15, 2021, 3:07pm UTC](https://community.fibery.io/t/how-to-assign-relations-to-child-entity-on-creation/1489/16 "2021-04-15T15:07:09Z")

</div>

> [@Matt\_Blais](#):
>
> since a Task may be related to any number of Products (including zero), there is no “general” way for Fibery to infer what Project a Task should relate to, from the Products relation.

Absolutely this 🙂

Anyway, I think this issue is not easily addressable currently, but I fully expect it to be easy with automations, assuming you can describe the rules to be applied.

For example

> [@Matt\_Blais](#):
>
> “when a Task becomes related to a Product, and the Task is not already related to a Project, then inherit the Product’s Project relation.”

…what should happen if the Task _is_ already related to a Project? Should linking to a Product be blocked?

> [@Matt\_Blais](#):
>
> a Task could be related to multiple Products that belong to different Projects ( **not that this should happen in practice** )

I would hope that [relations filters](https://community.fibery.io/t/approved-relationships-filter/1364) might be able to prevent that from happening.

---

_[View the full topic](https://community.fibery.io/t/how-to-assign-relations-to-child-entity-on-creation/1489)._