Is there a way to mark a column as a mandatory field?
Ideally I don’t want a row to be created or saved unless there are 3 specific fields that have been completed.
4 Likes
not currently @Litra_Sales -you can periodically run automations to clean up/delete incomplete rows
You could also create an Input table which would trigger an Automation that checks whether the input is valid before putting it in its final destination.
If the the new row in the Input table was not complete, it could warn the user about the omitted data.
One (hacky) way to warn the user is to use a button to add a row to a Warnings table that opens the row when the Warning is created.
Example (from another doc that I was sharing earlier)
1 Like
Multiple ways to go around it, but what I’d usually do is create a separate table just for inputs (or a whole flow), with a button in the end to save all the values to the destination table if everything’s correct.
Thanks guys, I will give these workarounds a go 
This is something I’d really like to see too. But I think these solutions with the “input table” is one of the least complex workarounds I’ve seen in Coda, haha, and should work for me for now.
My particular use of this is that I’d like to treat different rows across Coda as “types,” similar to Jira issue types, and I’d like to set up that they can’t go in unless that is assigned at the time of creation. So for example, some work item in dev has to be either named a “bug” or a “task” or it should’t be allowed to be created.
Fingers crossed you guys can bring this functionality in soon!
Would love to see this feature