We have just ran into an odd one in the back office. We have a document type that has a toggle that for some reason had been set to mandatory. This was on a v13 site and we have had no issues with it, until now after upgrading the site to v17. When we try to set the toggle to false we get the validation error in the back office of “Value cannot be empty” if we try to publish the page.
I have tried this on a fresh v17 site and get the same issue. I know its a bit redundant having a toggle as mandatory as it has to be 1 of 2 states at any time. But I thought I would bring this up just in case this is something that had been missed in the back office. As I would have assumed that even if a toggle was set to mandatory it should never error as it either would be true or false so it would have a value either way?
Thanks for that, Yes I just removed the mandatory field as like I said it doesn’t really make sense on a toggle as its only a binary answer. I just found it odd that it would error as I assumed (wrongly) that both true and false would be values to validate against