# Rows of data for each entity (2D data entry)

**URL:** <https://community.fibery.io/t/rows-of-data-for-each-entity-2d-data-entry/1376>\
**Category:** Get Help\
**Created:** [February 17, 2021, 12:28am UTC](https://community.fibery.io/t/rows-of-data-for-each-entity-2d-data-entry/1376 "2021-02-17T00:28:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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:** [February 17, 2021, 8:29am UTC](https://community.fibery.io/t/rows-of-data-for-each-entity-2d-data-entry/1376/2 "2021-02-17T08:29:41Z")

</div>

I don’t think there is an especially easy/convenient way of doing what you want, since the data in the invoice needs to be linked in two dimensions (e.g. $3000 needs to be part of Invoice 1 but also related to the Task called Design Development) which is not necessarily something fibery is good at.  
It’s something that I’ve encountered before.  
Potentially, when the ability to [limit relation linking based on filters](https://community.fibery.io/t/relationships-filter/1364) is implemented, then you could achieve it by making the Invoice entity contain a collection of ‘Invoice amount’ entities, and then these can have a relation to a Task, selectable based on a shortlist of Tasks that meet the filter Task.Project = Invoice.Project.  
In the meantime, a workaround with single select fields and/or auto relations might get you something close, but probably a bit kludgy.

---

_[View the full topic](https://community.fibery.io/t/rows-of-data-for-each-entity-2d-data-entry/1376)._
