Bases: Ability to pin / freeze columns

[Flummic]

Use case or problem

In the future I can imagine some bases getting pretty large with many columns (property-fields), which will cause them to scroll horizontally.

In those cases it would be nice to be able to pin columns so that they stay visible no matter how far you have scrolled away horizontally.
That way the filename or other field could always be visible and provide valuable context.

I imagine this to be very similar to the typical Excel/Spreadsheet-Functionality where you can also pin Columns/Rows to always stay visible

Related FR:

Bases: Ability to Pin / Freeze Base Table Headers

Use case or problem Bases table headers disappear when scrolling down to browse tables with a large number of records. Without the columns as references, context is lost and columns with similar content might get confused. Example, columns: Effort: 3 Priority: 2 Risk: 4 Value: 4 created time: modified time: date: start: due: It can get quite confusing to navigate the table without the header row reference. (as well as without the first column reference - See the related feature reques…

[Astrusia]

+1
Other programs like Google sheets call this freeze. Just for anyone interested.

[Luxly]

+1 and headers too!

[renatomen]

This feature is a high priority for me.
When managing databases such as projects, tasks, books and others, I typically have multiple columns and constantly need to scroll to visualise hidden columns.

I’d like the ability to freeze the first columns (pin them) so that they don’t scroll and allow me to maintain context while checking the rightmost columns (I use left to right).

One very concrete example is editing project dates or assignees. When I scroll using bases, I lose sight of which data or assignee relates to which project or task.

In dataview I use CSS to freeze the first column. (See image below).