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 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.
2 Likes