# \[DONE\] In Table view, make it easier to differentiate between input and calculated columns **URL:** \ **Category:** Ideas & Features\ **Tags:** table-view\ **Created:** [January 7, 2022, 6:07pm UTC](https://community.fibery.io/t/done-in-table-view-make-it-easier-to-differentiate-between-input-and-calculated-columns/2352 "2022-01-07T18:07:24Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Dimitri\_S](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dimitri_s/32/1683_2.png) [@Dimitri\_S](https://community.fibery.io/u/Dimitri_S)\ **Post date:** [January 7, 2022, 6:07pm UTC](https://community.fibery.io/t/done-in-table-view-make-it-easier-to-differentiate-between-input-and-calculated-columns/2352/1 "2022-01-07T18:07:24Z")
This is a problem in many other no code platforms as well, where its not immediately apparent what columns / fields you _can_ edit and which ones are there just to provide context (read-only). I find myself clicking the Name field a lot only to realize its the formula type and I actually need to enter the name info elsewhere. A simple and clean solution would be to color the read-only type fields a slight grey. Something like this or maybe a few shades lighter: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/fefabf5882963d899b66b476fa9cd88940aa5af2.png) ---
**Author:** ![Dimitri\_S](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dimitri_s/32/1683_2.png) [@Dimitri\_S](https://community.fibery.io/u/Dimitri_S)\ **Post date:** [February 7, 2022, 8:45pm UTC](https://community.fibery.io/t/done-in-table-view-make-it-easier-to-differentiate-between-input-and-calculated-columns/2352/2 "2022-02-07T20:45:38Z")
Thinking about this some more, one potential problem would be how to handle the row based Color Coding. For example, if a user has a light grey row highlighting filter it would clash with the read-only field color. I guess an easy solution would be that the column type highlighting supersedes row Color Coding, in which case the Color Coding is applied only to the input cells. A slightly more complicated solution is color mixing where the Color Coding is made one shade darker on calculated cells. Another platform (Grist) tackles the input vs calculated columns differentiation problem with an icon prefix (example below), which works well but isn’t as clean from a design perspective IMO. I think most users understand that a grey form field (when others are white) indicates read-only. ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/a/a80db6d33d8fed198b3dc172a2bb13eed2cfe6d0.png) ---
**Author:** ![mdubakov](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/mdubakov/32/10_2.png) [@mdubakov](https://community.fibery.io/u/mdubakov)\ **Post date:** [November 23, 2023, 11:41am UTC](https://community.fibery.io/t/done-in-table-view-make-it-easier-to-differentiate-between-input-and-calculated-columns/2352/3 "2023-11-23T11:41:20Z")
Implemented in latest release > [@Nov 23, 2023 / wolf New Table View, discoverable Undo actions](https://community.fibery.io/t/nov-23-2023-new-table-view-discoverable-undo-actions/5438): > > wolf New Table View Time has come and we’re replacing all Table Views with the new… Table View (some of you knew it as a Grid View sweat_smile). The new Table View is a combination of Table and List ideas, so you can now create hierarchical tables, such as Projects → Tasks or Products → Features → Tasks. Today, all your tables look slightly different. What’s new in the new Table View? We addressed many (but not all) requests, so [in the new Table View…](https://the.fibery.io/@public/User_Guide/Guide/Table-View-11) ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [October 4, 2024, 6:15am UTC](https://community.fibery.io/t/done-in-table-view-make-it-easier-to-differentiate-between-input-and-calculated-columns/2352/4 "2024-10-04T06:15:55Z")