Hi Aziz, you are correct; a column is either a formula column or a user-editable column. It cannot be both.
However, there are a number of ways to approximate a middle ground.
-
A column and a back-up column. The simplest solution is often the best. One column will be editable, and the second will be a formula that provides a backup when that one is blank (or some other condition):
[User Text].IfBlank(<some formula>)
; or
If(condition, [User Text], <some formula>)
In your case, it would beIf(Passed, "Passed on", [User Text])
-
Automation. If you don’t mind being a little slower and clumsier, you can set an automation rule in your doc to change the Response column to “Passed on” every time the checkbox is checked. In your case, you could also do the same thing faster with a button.
-
Canvas Column. The most complex option (might be a bit overkill) is to use a canvas column where the template canvas contains just one formula:
If(Passed, "Passed on", "Change this text directly in the formula.")
See also this post for an even more complex ways of using canvas columns.