Chasing a computed column (rel/query) link does not 'goto' to the Computed Column, only to the table

First time reporting a bug? Refer to our Start Here post.


Team ID:
(Glide)

App ID:
(Glide)

Description
When following a relation/query from a component details in the Layout Panel, Glide editor takes you to the table (in the Data Editor) but not to the specific column you are examining. The column is highlighted but the developers has to search or scroll for the column to find it. This is very cumbersome when working with wide tables and is a change. This also affects “Find uses” when a developer chases a computed column reference the builder takes you to the table within the Data Editor but NOT to the underlying column.

How to replicate
I built a test App (included above) that demonstrates this. Go to Companies Page. Select a Company. Layout Panel will show 2 collections (Contacts, Contacts in Country). Select either and go to Data/Source and ‘chase/follow’ the link (circled arrow)
image

Previously you were taken directly to the column in the table in the data editor. Now you are taken to the table (but not the column) and have to scroll/search for the column. This is a changed behavior and makes using/debugging large/wide tables very cumbersome.

For “Find uses” go to Contact table, Select ‘Find uses’ in Country column the chase the computed columns. You will be taken to the table but NOT to the underlying column. You have to scroll or search for it.
image

What I have found with this is if you click a second time once you land in the table, you’ll be taken to the column.

In the Find use case - yes. When chasing from the Layout Panel - didn’t work for me.

Have you submitted a ticket?

Hmmmm….maybe I didn’t do it correctly. I will re-check. Thanks Thinh!!

Thanks for the heads up- I did not submit it correctly; now I have (with a Loom screen recording to boot)

1 Like

Generally said, submitting tickets to the team will help them see the problem earlier, since they have access to your builders, not us, but in many cases the forum can help with identifying if it’s a user error or a bug before directing you to support, thus making sure any tickets submitted is indeed a bug they need to look at.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.