# Error: Can't create Lookup field, because "it already exists"?

**URL:** <https://community.fibery.io/t/error-cant-create-lookup-field-because-it-already-exists/3572>\
**Category:** Bugs & Issues\
**Created:** [November 20, 2022, 10:34pm UTC](https://community.fibery.io/t/error-cant-create-lookup-field-because-it-already-exists/3572 "2022-11-20T22:34:12Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**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:** [November 20, 2022, 10:34pm UTC](https://community.fibery.io/t/error-cant-create-lookup-field-because-it-already-exists/3572/1 "2022-11-20T22:34:12Z")

</div>

I don’t understand this error, when I try to add a Lookup field and name it “Project” (but it works if I use a different name) –

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/4/44d0f57ec0ef96c7a222d1941c4ce9db0d8c4f82.png)

---

<div class="post-metadata">

**Author:** ![Eren\_Turgut](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/eren_turgut/32/4425_2.png) [@Eren\_Turgut](https://community.fibery.io/u/Eren_Turgut)\
**Post date:** [November 21, 2022, 4:53pm UTC](https://community.fibery.io/t/error-cant-create-lookup-field-because-it-already-exists/3572/2 "2022-11-21T16:53:32Z")

</div>

Might be because the field in the other database itself is called Project, so I’m guessing it gives an error because it would be unclear whether you mean the Lookup field “Project” or the original field of the other database called “Project”.

---

<div class="post-metadata">

**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:** [November 21, 2022, 8:52pm UTC](https://community.fibery.io/t/error-cant-create-lookup-field-because-it-already-exists/3572/4 "2022-11-21T20:52:33Z")

</div>

Must be something like that, since it works when using a different name, but I don’t know why the confusion on Fibery’s part is necessary. Maybe related to how things are being named internally…

---

<div class="post-metadata">

**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\
**Post date:** [November 21, 2022, 9:08pm UTC](https://community.fibery.io/t/error-cant-create-lookup-field-because-it-already-exists/3572/5 "2022-11-21T21:08:06Z")

</div>

I think I ran into something similar where I couldn’t name something “Task”, if I recall correctly. These seem to be reserved names internally to Fibery. Confirmation from the team would be helpful though.

---

<div class="post-metadata">

**Author:** ![Viktar\_Zhuk](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/viktar_zhuk/32/1934_2.png) [@Viktar\_Zhuk](https://community.fibery.io/u/Viktar_Zhuk)\
**Post date:** [November 22, 2022, 10:43am UTC](https://community.fibery.io/t/error-cant-create-lookup-field-because-it-already-exists/3572/6 "2022-11-22T10:43:41Z")

</div>

Hi Oshyan

There are some hidden fields created for Databases used in Integrations but none of them are Task or Project. It looks like a bug with deleted Fields. Could you check in Audit Log that there is no deleted field for that database with that name?