I have a lot of situations where I like to use a formula to automatically calculate and update the value in a column, but sometimes I want to enter a value manually that overrides the calculated value.
At the moment I do this by having two columns, one with the formula and a second where I place the manual override. See for example this table where the estimated size of a task as calculated based on the sub-tasks, but I can override this estimate with a manual entry (see Task 1 versus Task 2). Functionally works fine, but is a bit inelegant having to see both columns and while makes sense for me as the doc maker, it’s not always intuitive for other users.
Rather than a simple yes/no override, it would be ideal if this could be conditional (similar to disable button if …). That would support my third example Task 3, which I might initially estimate as Large but then as I the sub-tasks increase in size above this the manual override could be disabled.
From a design perspective, columns that have override enabled could be signified with a small symbol right of the column title (similar to the display column).
2 Likes
Good idea! I’ve often felt the need for a hybrid column that’s both formulaic and editable, this solution could work
The Value for new rows field is sometimes not enough as it only computes on row creation
3 Likes
This usually works. But a lot of the time I run into timing issues where the value needed is derived from another column that doesn’t have a value at time of creation.
3 Likes
Hey @James_Pawluk ,
I have had situations similar to what you describe. While creating workarounds I often wished the same thing you are asking for…until I realized that having hybrid columns really ends up being a can of worms.
How would another user (or you after a while) know the calculated value has been overruled by a manual entry. You should be able to rely on the values shown in calculated rows without asking yourself if this is calculated or a user entry.
My workaround has been: if I really want to override a calculated value, I use helper rows (1-calculated value and 2-override column). These fields are hidden on the canvas table. The canvas table has a column that by formula shows either helper column 1 or, if helper column 2 is not blank, column 2. These fields are visible on a modal, where you can manually edit column 2. The result column that is visible in the full table view has a conditional format color, that shows a distinct background color if helper column 2 is not blank.
It is a bit of work (but not much) to set up and it creates a table that instantly shows either calculated of overruled values, without any doubt (or searching) about the source of the value (calculated or manually entered).
For your visible result column you can set conditions as to when the manual entry is valid (or not) and have the conditional formatting disappear (or change to another format) if a threshold has been reached.
Greetings,
Joost
1 Like
Hi Joost. Thanks for your suggestion. I guess I have numerous scenarios where I don’t believe it matters for the user to know whether it’s a default value or not. Certainly not at as a trade off for more convenient editing and ease of reading a table. That said I’m sure the amazing developers at Coda could integrate your approach with my an implementation of my suggestion if they decided to process it. Cheers
1 Like
