# \[DONE\] Ability to Access Current Entity in Non-Automation Formula **URL:** \ **Category:** Ideas & Features\ **Created:** [April 4, 2022, 8:13pm UTC](https://community.fibery.io/t/done-ability-to-access-current-entity-in-non-automation-formula/2681 "2022-04-04T20:13:40Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![DarrenLSchultz](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@DarrenLSchultz](https://community.fibery.io/u/DarrenLSchultz)\ **Post date:** [April 4, 2022, 8:13pm UTC](https://community.fibery.io/t/done-ability-to-access-current-entity-in-non-automation-formula/2681/1 "2022-04-04T20:13:40Z")
As I understand it currently, while it is possible to access the current entity fields when using a filter in an **_automation_ formula** — i.e., a formula constructed for use in an action button or rule, where the current entity is referred to as the “`Step 1`” entity — there is no such ability to do this when constructing a **_non_-automation formula**. Is there a reason why this is so? Is there a way that such functionality can be added for use in a non-automation formula? (NOTE: I wish to use such functionality so as to create a lookup (via formula) to return a single entity rather than by having to link that entity via a relation.) To the extent that such functionality is not currently possible, I suggest this as a new feature. Any thoughts or suggestions are appreciated. Thank you! ---
**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 5, 2022, 6:35am UTC](https://community.fibery.io/t/done-ability-to-access-current-entity-in-non-automation-formula/2681/2 "2022-04-05T06:35:32Z")
Can you provide a concrete example of what you want to do. It might be possible. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [June 15, 2022, 6:22pm UTC](https://community.fibery.io/t/done-ability-to-access-current-entity-in-non-automation-formula/2681/3 "2022-06-15T18:22:32Z")
It sounds like you are describing the ordinary function of a Formula field, which can access the current entity’s fields, and return any of them. Perhaps I don’t understand correctly? ---
**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:** [June 15, 2022, 11:33pm UTC](https://community.fibery.io/t/done-ability-to-access-current-entity-in-non-automation-formula/2681/4 "2022-06-15T23:33:45Z")
I think the need is for being able to use ‘this’ entity in a filter, e.g if a Project has Meetings (many-to-many), and you want a formula for only those Meetings where the due date is later than one week after the Project start date. The formula field in the Project should be something like Meetings.Filter([Due date] \> this.[Start date] + Days(7)) where ‘this’ refers to the Project itself It’s not currently possible. But sometimes there are workarounds, which is why I was curious for the concrete use case. ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [June 16, 2022, 12:10am UTC](https://community.fibery.io/t/done-ability-to-access-current-entity-in-non-automation-formula/2681/5 "2022-06-16T00:10:21Z")
Is this is what we do with formulas like: `[Some Collection].Filter( ).Sort( [Creation Date] ).First()` ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [January 3, 2023, 9:36am UTC](https://community.fibery.io/t/done-ability-to-access-current-entity-in-non-automation-formula/2681/6 "2023-01-03T09:36:39Z")
🎈 Now we have `[This ...]` within the `Filter(...)` function of non-automation Formulas: ```plaintext Meetings.Filter([Due date] > [This Project].[Start date] + Days(7)) ``` > [@December 29, 2022 / SOC 2 Type II compliance, \[This ...\] in Formulas](https://community.fibery.io/t/december-29-2022-soc-2-type-ii-compliance-this-in-formulas/3751): > > locked SOC 2 Type II certification Last week, our company achieved a major milestone: the SOC 2 Type II certification. This isn’t just any old certification you can buy off the internet for $9.99 (although we did consider it after 7 months in the process). No, this is the real deal - a rigorous audit of our controls and processes to ensure the security and privacy of our customers’ data. So raise a glass (or a coffee mug, if it’s early) and join us in celebrating this achievement. Contact us… ---
**Author:** ![antoniokov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/antoniokov/32/201_2.png) [@antoniokov](https://community.fibery.io/u/antoniokov)\ **Post date:** [January 3, 2023, 9:36am UTC](https://community.fibery.io/t/done-ability-to-access-current-entity-in-non-automation-formula/2681/7 "2023-01-03T09:36:55Z")