# CurrentValue Conflict in Nested Formulas

**URL:** <https://connect.superhuman.com/t/currentvalue-conflict-in-nested-formulas/50489>\
**Category:** Bugs\
**Created:** [August 9, 2024, 8:57pm UTC](https://connect.superhuman.com/t/currentvalue-conflict-in-nested-formulas/50489 "2024-08-09T20:57:04Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Nikola\_Lajic](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/nikola_lajic/32/21708_2.png) [@Nikola\_Lajic](https://connect.superhuman.com/u/Nikola_Lajic)\
**Post date:** [August 14, 2024, 8:29am UTC](https://connect.superhuman.com/t/currentvalue-conflict-in-nested-formulas/50489/3 "2024-08-14T08:29:54Z")

</div>

I run into this “issue” almost daily, and the formulas are much more verbose because of the withName workarounds.

I created a suggestion a while ago: [Custom name for current value as a function parameter](https://connect.superhuman.com/t/custom-name-for-current-value-as-a-function-parameter/45003)

---

_[View the full topic](https://connect.superhuman.com/t/currentvalue-conflict-in-nested-formulas/50489)._