It turns out this is a known issue: In Rlabkey version 3.0, we started encoding the parameters to executeSql to avoid WAF rejection, and this is not compatible with versions of LabKey Server prior to 23.9. You can restore the prior behavior by including this before the call to executeSql:

labkey.setWafEncoding(FALSE)

Upgrading to 23.11 will also address this issue, and is still the recommended overall plan to remain current with all fixes and upgrades.

My apologies for missing this the first time as it is included in the Rlabkey release notes, which are now linked from our documentation as well:

• Rlabkey Release Notes

--Molly