SOLVED - It turns out, it's not the Or function that's causing the issue, it's that a bit column value that used to be evaluated correctly when standing by itself (e.g., If(IsActive, true, false)) now needs to be written with the '=' sign (e.g., IsActive = true).
I have an app that uses Filter statemements in the Items property of some dropdown controls. I have been using Or conditions in the Filter statement successfully for a number of months, but all of a sudden, the controls that had been working are throwing an error. This feels like a bug since it used to work and the MS documentation for using Or conditions in Filter statements hasn't changed recently. I've tried using both the Or function and the || syntax, and they both cause the error. the And function and the && syntax are still working as before.
Here's an example of a statment that was working for the past several months, but now throws an error.