I have taken a quick look and it looks like this is down to a change we made when we introduced a fix to help prevent sql injections. I will get a dev ticket created shortly to resolve this.
@priority1it is it safe to assume that your issue is exactly the same because you work for the same company?
Excellent (I guess). I have created a ticket for it and I can see there are multiple operations that would be impacted but I don’t know when this will be fixed.