What causes dbt Source Override Error (Packages)?

The `overrides` property in the project's sources.yml references a package name that does not match the installed package's declared name. The `overrides` was deprecated in dbt 1.10 and the project has not migrated to the new source disabling pattern. The source schema or table name in the override does not match the actual table in the warehouse. Multiple packages define sources with the same name and the override is ambiguous

How do I fix dbt Source Override Error (Packages)?

Verify the package name in `overrides` exactly matches the package's `name` field in its `dbt_project.yml`.. For dbt 1.10+: migrate from `overrides` to the recommended approach of disabling the package source and defining a new source in your project.. Run `dbt ls --resource-types source` to see all resolved sources and confirm the override is applying correctly.. Check that the overriding source's schema and table names match the actual warehouse objects.. Review the dbt deprecation notice for `overrides` in your dbt version's release notes.

Medium severitydbt

Power BI Refresh Error:
dbt Source Override Error (Packages)

What does this error mean?

A dbt project attempted to override a source defined in an installed package, but the override was rejected or produced an unexpected schema conflict. Source overrides in packages allow projects to point package sources to local tables, but misconfiguration causes compilation failure.

Common causes

1The `overrides` property in the project's sources.yml references a package name that does not match the installed package's declared name
2The `overrides` was deprecated in dbt 1.10 and the project has not migrated to the new source disabling pattern
3The source schema or table name in the override does not match the actual table in the warehouse
4Multiple packages define sources with the same name and the override is ambiguous

How to fix it

1Verify the package name in `overrides` exactly matches the package's `name` field in its `dbt_project.yml`.
2For dbt 1.10+: migrate from `overrides` to the recommended approach of disabling the package source and defining a new source in your project.
3Run `dbt ls --resource-types source` to see all resolved sources and confirm the override is applying correctly.
4Check that the overriding source's schema and table names match the actual warehouse objects.
5Review the dbt deprecation notice for `overrides` in your dbt version's release notes.

Frequently asked questions

What replaced `overrides` in dbt 1.10+?

Set `config: enabled: false` on the package source in your project's sources.yml to disable it, then define a new source pointing to your actual table. This is more explicit and less error-prone than the `overrides` property.