# Last Project Meeting

**URL:** <https://community.fibery.io/t/last-project-meeting/1429>\
**Category:** Get Help\
**Created:** [March 6, 2021, 10:34pm UTC](https://community.fibery.io/t/last-project-meeting/1429 "2021-03-06T22:34:48Z")\
**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:** [March 7, 2021, 9:23am UTC](https://community.fibery.io/t/last-project-meeting/1429/2 "2021-03-07T09:23:53Z")

</div>

It’s not possible to refer to an entity’s own fields in the filter expression (you can only use the fields of the entity collection the filter applies to).  
It has been discussed before, in another context

> [@\[DONE\] Siblings as Children of Parents: filter self](https://community.fibery.io/t/siblings-as-children-of-parents-filter-self/981):
>
> Bit of a confusing title, but basically: When using self-relations in a type, the uni-directional type is often a great fit for the relation (that is - not for situations where I’d want the basic / undirected / bi-directed siblings), where the concept of “parent” entities and “child” entities exists, but they really are all the same type. In such scenarios, it’s often nice to see automatic sibling links, through a lookup: using the children of parents. The problem is that this results in inclu…

Anyway, I have made a demo app that sort-of solves your problem.

> **[Start for free, upgrade when you love it — Fibery](https://shared.fibery.io/sign-up?appShareId=a9614110-fa57-4c13-a94d-a60459057884-meeting-links)**
>
> Create Fibery account. Build your company workspace with no code.

It uses a formula in the project type to find the date of the latest meeting, and then adds a ‘Latest’ flag to the whichever meeting has the matching date.  
Then there is another project formula to find the latest date from all meetings that don’t have the ‘Latest’ flag set, in order to find the date of the penultimate meeting. The meeting that matches this date is flagged as ‘Penultimate’.

Finally, all meetings have a formula field to list the meetings that have either flag set (‘Latest’ and ‘Penultimate’). In this way, whichever meeting you are curently looking at, you can quickly navigate to the latest or penultimate.  
I know it doesn’t exactly provide what you asked for, but I hope it helps your use case.

---

_[View the full topic](https://community.fibery.io/t/last-project-meeting/1429)._
