I’ve searched high and low and can’t seem to find a good answer for a seemingly easy question:
I have a row that has Status field with choices like “Not Started” “Blocked” “In Progress” “Done”
The row also contains a Progress Slider.
I’d like for folks to update the Progress Slider
I’d like the Progress Slider to automatically change to 100 when user selects Status == Done
I’d like to avoid making the user press a Done Button and no amount of formula writing seems to work.
Conditional formatting doesn’t seem to be the right path.
I tried creating a new column that is a checkbox that marks itself true when Statue is made “Done” but can’t get that to work, either (“ModifyRows” doesn’t work outside of button creation, it seems?)
I found this, but seems there wasn’t an adequate solution offered (as this will autopopulate “100” when marked to Done, but is not user-changeable)
Unfortunately, the two things that you are trying to do are mutually exclusive. Either you allow people to modify the progress bar manually, or you have the bar updated automatically.
In general terms, columns in Coda are either updated formulaically, or manually.
The easiest way to achieve your solution is with a button. Using a button with a runAction() you can update both the status column, as well as the progress bar.
Is it possible to have a hidden button field trigger a button press to max out progress bar when a user changes a task to DONE? Or does the button need to be pressed by the user?
if i understand your requirements correctly i.e. needing both the Status column and Progress Bar column to be editable/user changeable and avoiding additional manual steps i.e. button push, my suggestion about be using an automation?
the caveat is that automations arent that instant/fast, usually there’s a 5-10 secs delay.
please see demo below:
Here is the demo doc for your reference should you want to incorporate into yours.
another thing to note if youre setting it up/using it - the cursor needs to be clicked outside of status cell for the automation to trigger/process the status was changed. Otherwise it will still think you’re making a change.
hopefully this makes sense and helps avoids you doubting yourself in the event youre sitting there thinking “why isnt this working??!!” lol
Thanks so much, Mel - greatly appreciated. This does indeed accomplish what I am seeking, though the performance is a bit slow. Might give it a go and see how it works for the team. Thanks again!
the former i try to not use often as more row buttons affects doc performance and the latter, its a bit black magic and will run into performance issues later as well when doc size grows.
Pros and Cons for you and your team to weight up
