Yeah, definitely see that same issue. Interestingly, it’s even worse in the published version. Even with the column already populated with something different, such as ‘xxx’ and submitting an edit with a description change, the description will update in the data, but the yes/no columns will not update. This definitely does seems like a bug. I had/have a somewhat similar issue in one my other apps, but in that case I’m filling user specific columns, so I assumed it was only a user specific column issue. In that case it worked fine in the builder, but the published version seemed to be a step behind and populated certain columns with old values that had already been changed to new values. Hard to explain, as it’s a bit complicated of an app, but I explain it more here: Set Column Bugs. I can’t retest my app at the moment due to another bug with IF columns that I found.
I tried a few different things, which seemed to make it work in the builder, but the published version still wouldn’t work correctly. I switched to a custom action and tried with clears to those columns followed by setting them. I also tried setting them to yes/no twice, but no luck. Even with the columns already populated, it just wouldn’t bring them back to the server database. I think there has always been something off with the Set Column action in a Add/Edit/Form screen and I usually try to avoid using it there. I think there gets to be some weird sync issues when you are trying to update a row twice within a split second.
Instead, as a workaround solution (previously the only solution prior to having any onSubmit actions) is to instead create some template yes/no columns in your user profile sheet. Then you can simply pass those user profile column values through the Edit (or Add, or Form) screens. That method has always worked reliably and you are only making one update to the row instead of two.
These are the template columns that are created in the user profile table.
These are the user profile columns being passed through and set to fill your yes/no columns.
If you ever had a situation where you didn’t have a user profile sheet, then you could instead place the template columns in the same table you are editing or in the table that drive a form (not the destination table of the form). Then you can pass the template values through the Screen Column values.
So yes, I would say that this is a bug, or at least not working as one would expect it to, but at least there are alternatives to keep you moving.