Variable not found (?).

• The Liquid for variable reference, {{}}, is nested within Liquid for logic, {% %}.
• A templated filter references a table that is not joined into a derived table.
• A field referenced in Liquid is not fully scoped with a view name (view_name.field_name).
• A filter’s value is referenced inside another LookML dashboard filter.
• A parameter parameter’s value is not compatible with the corresponding type. For example: {% if parameters.change_value._parameter_value == "'AA'" %}. Review the parameter type to ensure that the value evaluates correctly (type: string versus type: unquoted).
• A field is referenced correctly in Liquid as view_name.field_name, but field_name is not defined in the scoped view view_name, or the view is aliased with from in an Explore.
• A Liquid reference to a variable is not defined, or the reference includes a typo.
• A Liquid reference includes a dimension group of type: time, but not the specific timeframe. For example, instead of
  {{ view_name.creation_date }}, the reference should use
  {{ view_name.creation_date_year }}.
• A field is using Liquid with LookML substitution operator syntax, ${view_name.field_name}, instead of without, as view_name.field_name.

• Liquid variable reference
• Templated filters and derived tables (Help Center article)
• from (for Explores)
• from (for joins)
• Dimension groups must be referenced by their individual dimensions

Inaccessible view (?). (?) is not accessible in explore (?). Check for missing joins in explore (?).

• The referenced view doesn’t exist.
• A join is missing, making the view inaccessible to some Explores.
• The view is renamed with a from parameter in an Explore.

• Error: Unknown or inaccessible field (Help Center article)
• from (for Explores)
• from (for joins)

Unknown or inaccessible field (?). Check for typos or append a timeframe to the name if the field is type time.

• There is a typo in a field name or in a reference to the field.
• The field is excluded from an Explore by the fields parameter.
• The reference is to a dimension_group without a timeframe specified.

• fields (for Explores)
• fields (for joins)
Dimension groups must be referenced by their individual dimensions

Unknown view (?).

• A view is not included in the model file.
• An explore is extending a base explore that is missing a view_name parameter.
• An Explore name defined in the explore parameter is based on a misspelled or nonexistent view name.
• A model-based SQL Runner query is running with the incorrect model selected.

• include model parameter reference
• extends (for Explores)
• explore parameter
• Running a query against a LookML model in SQL Runner

Unknown view (?). View does not exist in model (?). Check for typos or missing include statements.

• An explore is extending a base explore that is missing a view_name parameter, and fields from any of the joined views reference the base explore name.
• A field references a view that is misspelled, nonexistent, or not joined to applicable Explores.

• extends (for Explores)
• Scoping and naming LookML objects

Unknown field (?) in filter

• A native derived table (NDT) definition includes a bind_all_filters parameter on a custom field that is not defined in LookML.
• A LookML filter references a LookML field that is commented out or that does not exist.
• A LookML filter references a LookML field from a different view, and the field is not fully scoped nor joined into all relevant explore parameters.

• Native derived table explore_source reference
• filters for LookML dashboards
• always_filter reference
• access_filter reference
• filters for measures

Measures with Looker aggregations (sum, average, min, max, list types) may not reference other measures.

• Measure type category reference
• Error: Measures with Looker aggregations (sum, average, min, max, list types) may not reference other measures (Help Center article)
• How to dimensionalize a measure in Looker (Help Center article)

Unknown view (?). View (?) does not exist in model (?). Check for typos or missing include statements in (?).

• Trouble getting started with model/view/Explore (Community post)
• include model parameter reference

Can't construct persistent derived table (?), connection (?) could not be registered

• Any dependencies for an existing PDT have failed to build.
• There is an issue with the connection, which needs to be diagnosed by testing the connection (for example, testing the connection may reveal that the Looker user may not have sufficient own or write access to the database).
• Imported project files, such as a view that defines the failing PDT, or a view that is referenced by the failing PDT, are not included in the importing project.
• The database connection does not have the Persistent Derived Tables setting enabled.
• A Looker Block’s code has not been updated to the connection’s SQL dialect, if different from the dialect for which the block was written.
• OAuth is enabled for a Snowflake or BigQuery connection.
• A value other than the default value, TRUE, has been set for the Snowflake database AUTOCOMMIT parameter.

• Testing database connections in Looker
• Including files from an imported project
• Persistent Derived Tables connection setting
• OAuth for BigQuery connections
• OAuth for Snowflake connections

Unknown or excluded suggest_dimension (?) in field (?)

• A field referenced by a suggest_dimension parameter does not exist, has been commented out, or is excluded in an Explore by a fields parameter.
• A field referenced by a suggest_dimension parameter is defined in another view, but is not fully scoped as view_name.field_name in the reference.
• A suggest_dimension parameter references a field in a different view that is not joined into all relevant explore parameters, or a view that is aliased in an explore with a from parameter.

• Error: Unknown or inaccessible field (Help Center article)
• suggest_dimension parameter reference
• from (for Explores)
• from (for joins)
• fields (for Explores)
• fields (for joins)

A view named (?) has been defined multiple times. Each view in a model must have a unique name.

This include does not match any files

• A typo in the path to the file is causing en error.
• A folder reference is using incorrect syntax.
• A project import reference is using incorrect syntax.

• include model parameter reference
• Using include with IDE folders
• Including files from an imported project
• Referencing files from an imported project

SQL Dialect does not support Symmetric Aggregates with percentiles, field ignored.

• Not all database dialects support median or percentile measure types with symmetric aggregates
• A simple explanation of symmetric aggregates or “Why on Earth does my SQL look like that?” (Help Center article)

Using project_name or local_dependency in manifest.lkml without Local Project Import enabled is not supported. Params ignored.

• project_name parameter reference
• local_dependency parameter reference
• Local Project Import Labs feature

Cannot use native derived table (?) with bind_all_filters outside of its source explore (?)

Measures of type count do not use the sql parameter. Use count_distinct to count by something other than the primary key, or remove the sql parameter.

• count measure type reference
• The difference between count and count_distinct measure types (Help Center article)

An explore named (?) has been defined multiple times. Each explore in a model must have a unique name.

• An Explore name defined in the explore parameter of a model file is duplicating another existing Explore name. Explore names must be unique in a model.
• An imported project has an explore with the same name as an existing explore in the importing project.
• An included model file has an explore with the same name as an existing explore in the including project model file.*
• There is a circular reference in the code, referencing the explore (or model file) multiple times.

• explore parameter reference
• Including models in a model

Unknown view '(?)' --> Did you '- include: (?)' in (?).model.lookml?

• A model is including the view folder, but the specific view file is outside the folder.
• A model is including the name of the view, but not the view file, if named differently.
• A view is joined into an explore multiple times, but is missing the from parameter the second time it is joined.

• Using include with IDE folders
• include parameter reference
• You can join the same table more than once using from

Unknown field '(?)'

• The field you are trying to reference does not exist, has been misspelled, or has been commented out.
• A referenced field is defined in a different view, and is not scoped with its view name.
• A field is defined in a different view that is not joined into the necessary Explores, or the view is aliased in a join, making the field inaccessible by some Explores.
• A required_fields parameter references a field that is inaccessible, is misspelled, doesn’t exist, or is commented out.

• Error: Unknown or inaccessible field (Help Center article)
• from (for Explores)
• from (for joins)
• required_fields parameter reference

Cannot use (?) as access filter since any user can edit their own value.

• Creating user attributes
• Using user attributes in access filters
• access_filter parameter reference

label_from_parameter of (?) must refer to a parameter.

• A field referenced by a label_from_parameter parameter doesn’t exist, is misspelled, or is commented out.
• A field referenced by a label_from_parameter parameter exists, but is not a parameter type.

• label_from_parameter parameter reference
• parameter parameter reference

Cannot use user-editable attribute (?) for access_grant (?)

• Creating user attributes
• Controlling access with access grants
• access_grant parameter reference

datagroup (?) has a sql_trigger. This is not allowed in models with a parameterized connection.

• Using user attributes in database connections
• Configuring separate login credentials for PDT processes
• datagroup and sql_trigger parameter reference

relationship missing, assumed to be many_to_one.

No distribution_style specified in persistent derived table (?). Using default distribution style (?).

always_filter: unknown filter field '(?)'

• A field referenced by an always_filter parameter does not exist, is misspelled, or is commented out.
• A field referenced by an always_filter parameter is a dimension_group of type: time that does not have a timeframe appended.
• A field referenced by an always_filter parameter is a field that is defined in a view that is not joined into all relevant explore parameters, or the field is not scoped with its view name.

• Error: Unknown or inaccessible field (Help Center article)
• Dimension groups must be referenced by their individual dimensions
• always_filter parameter reference

The location field type requires both sql_latitude and sql_longitude.

Missing required sql_step in create_process of derived table '(?)'.

• There is no sql_step specified in the create_process, which requires one or more sql_step subparameters.
• A cached LookML validator error flagged a missing sql_step even though a sql_step was already added. Validate once more to resolve the error.

Can't construct aggregate table (?), temporary schema for (?) is unset.

• Persistent Derived Tables connection setting reference
• Temp Database connection setting reference

Can't construct aggregate table (?), connection (?) could not be registered.

• Aggregate tables must be persisted
• Temp Database connection setting reference

Unknown view (?) referenced by explore (?)

• A view is included using the default include: "*.view.lkml", but the view is in a different folder.
• A view name or file path is misspelled in an include statement, or the include statement is including the name of the view, but not the view file, if named differently.
• There is an issue with special characters, such as _views, in a folder.
• An explore is extending another explore that is missing a view_name parameter that specifies the base view.

• include parameter reference
• Using include with IDE folders
• extends (for Explores)
• view_name parameter reference

The location field type does not use the sql parameter. Please use sql_latitude and sql_longitude instead.

A list_field must be defined for measures of type list.

Query failed with unexpected exception (?)

• A database other than the main connection database is specified in the PDT Overrides column on a connection’s Connection Settings page in the Admin panel.
• The per-user query limit has been exceeded and a queued query has hit the connection pool timeout.
• A JDBC connection has failed.
• An unexpected Looker application failure has occurred.

• Configuring separate login credentials for PDT processes
• Connection Pool Timeout
• Looker startup options
• Query timeouts and queueing (Help Center article)
• Connection settings additional params (including JDBC parameters)

Looker is having trouble connecting to your database.

• What does the “Looker is having trouble connecting to your database” error mean? (Community post)
• Max Connections connection setting reference
• Connection Pool connection setting reference

Missing dates/values for '(?)' were not filled.

• Dimension fill cannot be applied because more than one dimension was selected in an Explore.
• Dimension fill cannot be applied because one or more fields were pivoted in an Explore.
• Dimension fill cannot be applied because a field has distinct string values (for example, allowed_value or case parameters), and there is a filter applied to that field.

filters: ` is not supported for measures of non-aggregate type '(?)'

• filters parameter reference
• Creating filtered measures (Help Center article)

Unknown source explore (?) in lookml test (?) declaration.

• A misspelled, nonexistent, or commented-out Explore name is used in a data test’s explore_source subparameter.
• A data test is defined in a file that does not include or is not included in the file that contains the Explore’s explore_source definition.
• An Explore with the extension: required parameter specification is used as the explore_source of a data test.

• test parameter reference
• explore_source (for data tests)
• LookML data tests recommendations and best practices (Community post)

filter_expression: is not supported for measures of non-aggregate type '(?)'

• filter_expression LookML dashboard query parameter reference (for waterfall chart)
• LookML dashboard query parameter reference (for table chart)

Field references an aggregate but is specified as a dimension. If you want to use aggregations such as sum, average, count, use a measure type instead.

• Dimension and measure fields
• sql (for dimensions)

Cannot specify both sql_table_name and derived_table for view (?)

• view parameter reference
sql_table_name (for views)
• derived_table parameter reference

Persistent Native Derived Table for view (?) has an explore source (?) that has access filters. Persisting this table may result in unexpected behavior.

• Things to consider when deciding whether to persist a derived table
• access_filter parameter reference

Unknown or unexpected parameter "(?)" in (?).

• A distribution_style parameter is used for a dialect that does not support that parameter
• A cluster_keys parameter is used for a dialect that does not support that parameter
• A sql_always_where parameter is defined in a join instead of an explore.
• Timeframes defined in a dimension_group are not of type: time.
• A sql_distinct_key parameter is defined in a dimension instead of a measure.

• Dialect support for distribution_style
• Dialect support for cluster_keys
• dimension_group field type reference
• sql_distinct_key parameter reference

Could not find the constant `

Multiple primary key definitions for view '(?)': '(?)' and '(?)'

• primary_key parameter reference
• extends (for views)
• Reusing code with extends

Persistent Native Derived Table for view (?) references user attributes. Persisting this table may result in unexpected behavior.

• Things to consider when deciding whether to persist a derived table
• access_filter parameter reference
• sql_always_where parameter reference
• Creating native derived tables
• Aggregate awareness

No map layer named (?) is defined. Must be one of countries, uk_postcode_areas, us_counties_fips, us_states, us_zipcode_tabulation_areas

• map_layer parameter reference
• Built-in map layers for map_layer_name

Persistent derived table (?) should include at least one index

• indexes parameter reference
• Persistent derived tables reference
• aggregate_table parameter reference