When upgrading Elementary from one minor version to another (like v0.16.0 to v0.18.0), you need to run

dbt run --select elementary

to update the Elementary tables with any new columns that were added in the newer version. This is a common issue when upgrading Elementary, as new features often require schema changes. Running this command will preserve your historical data while adding the new columns required by the latest version. This is because Elementary models are mostly incremental, so they'll only update the schema without overwriting existing data. Based on the knowledge sources, many users have encountered similar "column does not exist" errors after upgrading Elementary. For example, one user reported an error about a missing

unique_key

column after upgrading to v0.16.4 [in this Slack thread](https://slack.com/archives/C02CTC89LAX/p1739809646764679), and another user reported a missing

PATCH_PATH

column [in another thread](https://slack.com/archives/C02CTC89LAX/p1739912065757689). The solution in all these cases was to run

dbt run --select elementary

after upgrading the package version. This is also mentioned in Elementary's [upgrading documentation](https://docs.elementary-data.com/release-notes/upgrading-elementary) as noted in one of the responses. To summarize the steps: 1. You've already updated the Elementary dbt package version in your packages.yml 2. Run

dbt deps

(which you've likely already done) 3. Run

dbt run --select elementary

to update the schema of Elementary tables 4. Now you should be able to run

edr report

without the column error This approach will preserve your historical data while adding the new columns required by v0.18.0.