# Make it so clicking lines to navigate to a record is less challenging

**URL:** <https://community.noloco.io/t/make-it-so-clicking-lines-to-navigate-to-a-record-is-less-challenging/884>\
**Category:** Feature Requests\
**Created:** [June 25, 2024, 1:34pm UTC](https://community.noloco.io/t/make-it-so-clicking-lines-to-navigate-to-a-record-is-less-challenging/884 "2024-06-25T13:34:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![nathan](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/nathan/32/46_2.png) [@nathan](https://community.noloco.io/u/nathan)\
**Post date:** [June 25, 2024, 1:34pm UTC](https://community.noloco.io/t/make-it-so-clicking-lines-to-navigate-to-a-record-is-less-challenging/884/1 "2024-06-25T13:34:31Z")

</div>

Me and the users I work with struggle to click on lines on tables in Noloco. It seems that linked record fields, edit in line fields, and date fields, amongst others, create a large un-clickable area on table lines. Here’s an example of a user trying to find a clickable area:

> **[Gyazo Screen Video](https://gyazo.com/12d7bd89b9893ac9bcdb7c10d50c7b83)**
>
> Gyazo is the easiest way to record screenshots & videos you can share instantly. Save time with async visual communication that's effortless and engaging.

For certain users, this is surmountable. But for many standard users, it becomes frustrating and a major roadblock.

I’m not sure about the exact solution, but it seems to me that one way to improve would be making more of the empty areas clickable to a line, and also having some sort of visual indicator that a user is hovering over an area that would navigate them to the record. (Like a highlight)

---

<div class="post-metadata">

**Author:** ![nathan](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/nathan/32/46_2.png) [@nathan](https://community.noloco.io/u/nathan)\
**Post date:** [June 25, 2024, 1:37pm UTC](https://community.noloco.io/t/make-it-so-clicking-lines-to-navigate-to-a-record-is-less-challenging/884/2 "2024-06-25T13:37:27Z")

</div>

Another field type that is problematic is multi-select fields. If there is no value in the field, it is perfectly blank but a user cannot click that area to visit the record.

---

<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:** [June 25, 2024, 3:54pm UTC](https://community.noloco.io/t/make-it-so-clicking-lines-to-navigate-to-a-record-is-less-challenging/884/3 "2024-06-25T15:54:06Z")

</div>

This is one of the downsides of over-using inline editing.

Truthfully there’s no great solution, as reducing the clickable area makes inline editing even worse.

We usually suggest disabling row click and using an action button to navigate to the record view instead, would that work?

---

<div class="post-metadata">

**Author:** ![nathan](https://dub1.discourse-cdn.com/flex005/user_avatar/community.noloco.io/nathan/32/46_2.png) [@nathan](https://community.noloco.io/u/nathan)\
**Post date:** [June 25, 2024, 4:10pm UTC](https://community.noloco.io/t/make-it-so-clicking-lines-to-navigate-to-a-record-is-less-challenging/884/4 "2024-06-25T16:10:19Z")

</div>

I think your solution is the best one for now, it’s just a lot of extra buttons to make with a large solution.

I run into this issue even without inline editing, but the inline editing definitely makes it worse. For examples of when it’s rough even without inline editing, blank multi-select fields are not clickable.

---

<div class="post-metadata">

**Author:** ![rutgerhofste](https://avatars.discourse-cdn.com/v4/letter/r/ba9def/32.png) [@rutgerhofste](https://community.noloco.io/u/rutgerhofste)\
**Post date:** [October 15, 2024, 2:49pm UTC](https://community.noloco.io/t/make-it-so-clicking-lines-to-navigate-to-a-record-is-less-challenging/884/5 "2024-10-15T14:49:00Z")

</div>

That’s too bad. I’m trying to implement the suggested solution using a button. I tried adding a record button - view details - this record. My intended use is to navigate into the detail page of the row’s record. I’m likely doing something wrong here.
