# Greyed out linked record field

**URL:** <https://community.noloco.io/t/greyed-out-linked-record-field/1343>\
**Category:** Bugs\
**Created:** [October 17, 2024, 11:21am UTC](https://community.noloco.io/t/greyed-out-linked-record-field/1343 "2024-10-17T11:21:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![EthosLuke](https://avatars.discourse-cdn.com/v4/letter/e/46a35a/32.png) [@EthosLuke](https://community.noloco.io/u/EthosLuke)\
**Post date:** [October 17, 2024, 11:21am UTC](https://community.noloco.io/t/greyed-out-linked-record-field/1343/1 "2024-10-17T11:21:05Z")

</div>

Someone has just reported an odd bug to me, where if you go to create a record from a related record collection, change your mind and then click to the collection page (either from breadcrumb or nav bar) and go to add a record there, it leaves the linked record field as disabled so it is no longer selectable…

For context as the above sounds confusing…

We have a collection called applications and a collection called documents. They have a many-to-many relationship.

From the application page there is a collection of related documents, if you start adding a new document from this collection it automatically links the application and disables the field which is fine

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/1X/d3e278046a0fd672f51deaab7e92ef0eb6594a84.png)  
but if the user then navigates to the “Documents” page without saving this and then clicks to create a new document, the applications field is left empty but still disabled:  
 ![image](https://europe1.discourse-cdn.com/flex005/uploads/noloco/original/1X/7dd2d68e802618fa098a3f96ffefe44e032fc142.png)

---

<div class="post-metadata">

**Author:** ![darragh](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/darragh/32/12_2.png) [@darragh](https://community.noloco.io/u/darragh)\
**Post date:** [October 21, 2024, 5:57am UTC](https://community.noloco.io/t/greyed-out-linked-record-field/1343/2 "2024-10-21T05:57:12Z")

</div>

Thanks for reporting this @EthosLuke

Could you share a link to the 2 pages you’ve mentioned so we can verify there’s not something else unusual happening