View the original community article here
Last tested: Sep 6, 2018
You may see an error that says something like Column 'id' in field list is ambiguous. This error means that there is a field name that is present in more than one table, so it needs to be scoped with the table name to avoid ambiguity: using orders.id instead of just id will resolve the issue.
Proper LookML references should always avoid these errors, so if you are seeing this, you are most likely doing something like using just field_name instead of ${field_name} or ${TABLE}.field_name. Check out this help center article: https://help.looker.com/hc/en-us/articles/360001298768-How-to-reference-views-and-fields-in-LookML
This content is subject to limited support.