Update, in case anyone else sees this problem. There was a string literal in a dependent query that needed to be cast to a VARCHAR.

We are considering SQL generation changes to reduce or eliminate the cases that need explicit CAST expressions for string literals.

Thanks,
Josh