Hi @fobispo,
I was able to reproduce this bug, and have filed an internal bug for the development teams to look at. We don’t have an ETA on the issue yet.
One workaround I can suggest is to instead use a customString instead and convert the string yes/no to boolean in your application, if possible.
Something like this -
Thanks for notifying us about this issue. We will try to get it resolved soon.
Hope this helps.