LookML validation error breaks dashboard: field not found in view troubleshooting

TL;DR

Run the Content Validator and the LookML Validator together, then fix the reference at its source. Either restore the renamed field in the view, add the view to the explore join so the field is reachable, or update the dashboard element to the new field name. Deploy the model change and revalidate before telling viewers the dashboard is fixed.

LookML validation error breaks dashboard: field not found in view troubleshooting

Use this when

• The LookML Validator or Content Validator lists a dashboard with a field not found error.
• A view refactor or rename landed and several dashboards broke at once.
• The field exists in the view file but the dashboard still reports it missing.

Not for this skill when

• The dashboard loads but returns no rows. That is a filter or data problem, not a validation error.
• Git conflicts block the model deploy itself. Resolve the branch problem before validating content.

Steps

1. Run the Content Validator, filter to the broken dashboard, and record the explore, view and field named in the error. Verify: each broken element maps to one named field reference
2. Search the project for that field definition and confirm whether it was renamed, removed, or moved to another view. Verify: you find either the old definition history or the new field name
3. Open the explore definition and confirm the view is joined and that any fields parameter on the join does not exclude the field. Verify: the field appears in the explore field picker in development mode
4. Apply the smallest correction, restoring the field with its original name, updating the dashboard element to the new name, or adding the missing join, then run the LookML Validator. Verify: the validator reports no errors for the model
5. Use the Content Validator fix action or edit the dashboard elements that still point at the old reference, then save the dashboard. Verify: the validator no longer lists the dashboard as broken
6. Merge and deploy the model change, clear the dashboard cache, and open the dashboard as a viewer. Verify: every tile renders data and no validation banner appears

Why it happens

Field resolution in Looker is explore scoped, not project scoped. Refactors that look safe inside one view file break dashboards when the explore join set, a fields restriction, or a rename is not carried through to saved content. Content validation exists precisely because the LookML Validator alone cannot see dashboard references. Running both validators after any view rename is what prevents the break from reaching viewers.

Looker resolves every dashboard element field against the explore and its joined views at load time. A field can exist in a view file and still be reported as not found if the view is not joined into that explore, if the field was renamed or hidden with a fields restriction, or if the dashboard was built against a personal branch version of the model. The validator output names the explore, the view and the field, which narrows the fix to one of those three places.

Variants and edge cases

Looker field not found in view dashboard broken

The viewer-reported phrasing for the same validation failure.

LookML validation error unknown field explore join

The join-focused variant when the field exists but is unreachable.

Looker content validator broken dashboard field removed

The validator-tool phrasing analysts search after a refactor.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_ymhwZv3tC8hMhQKU5z9JdQ