Solved: Locate bugs in lookml

ginandtobby

Hi Community.

When an error occurs in the Explore UI while running a query, the error message often indicates a line number, such as [100:10]. However, there’s no visible line number marker in the error message box or in the SQL Runner. If my query is very long, how can I easily locate the problematic line? Is there a feature that allows me to jump directly to that line?

Thanks!

GavinW

The error in the explore UI tells you where the error is in the generated SQL rather than in the LookML code.

When troubleshooting, if you are struggling to match the error message related to the generated SQL to a specific field as the source of the error, you can strip out fields until the error goes away, allowing you to identify the LookML field that is causing the issue. Also bear in mind that filters can cause or be related to errors, so don't forget to add/remove them too!

View solution in original post

GavinW

The error in the explore UI tells you where the error is in the generated SQL rather than in the LookML code.

When troubleshooting, if you are struggling to match the error message related to the generated SQL to a specific field as the source of the error, you can strip out fields until the error goes away, allowing you to identify the LookML field that is causing the issue. Also bear in mind that filters can cause or be related to errors, so don't forget to add/remove them too!