Last Tested: Jan 21, 2019
In some instances, the same exact SQL will run perfectly fine in SQL Runner and also cause an error when run on the Explore page. This can happen where there is a conflict of field type definition.
For example, a user can define a field as 'string' and SQL Runner works fine but still causes an error on the Explore page. If you look at the raw field value in SQL Runner, you may find that this field is actually an 'array'. In that case the user would have to cast the field as a 'string' .
Be sure to check the raw values in SQL Runner to suss out any potential field type conflicts.
This content is subject to limited support.