column reference "id" is ambiguous

Not specified by the original author.

TL;DR

Two joined tables both have the column and you did not say which one. Qualify every shared column with its table alias, or rename in a CTE before the join. Recompile and check the generated SQL has no bare ambiguous names left.

Error

Redshift column reference is ambiguous in dbt model

Steps

1. Read the error for the column name, then open the model and find the join where both sides carry that column. Expected: You find the join, e.g. orders joined to customers both having created_at.

2. Alias the tables (o, c) and prefix every reference to the shared column: o.createdat vs c.createdat. Do it for all shared columns, not just the one Redshift named. Expected: No bare references to shared columns remain.

3. Run dbt compile --select the model and grep target/compiled for the column to confirm qualification. Expected: Compiled SQL shows aliased columns throughout.

4. Run dbt run --select the model. Expected: Build succeeds, no ambiguity error.

When to use

• Redshift raises column reference is ambiguous on a dbt model
• joins between tables sharing column names like id, created_at, status
• after adding a new join that introduced a name collision

When not to use

• column does not exist (that is a missing column, different error)
• the ambiguity is inside a subquery you wrote by hand (same fix applies, but check the subquery)
• the error is at dbt compile time in jinja, not from Redshift

Tool compatibility

• dbt-redshift adapter; Redshift is strict about qualification
• dbt compile lets you inspect the generated SQL without running
• CTEs for renaming are portable across adapters

Variant phrasings

ambiguous column in a using() join

USING merges the column, so referencing it bare afterward is fine, but referencing table.col for a USING column is the error. Pick one style.

ambiguous only after adding a staging model

The new staging model inherited column names from the raw table. Rename at the staging layer so marts never see collisions.

Why it happens

Redshift resolves unqualified column names against all tables in scope and refuses to guess when two match. select * plus joins is how the collision sneaks in; the model worked until a second table gained the same column name.

Edge cases

• dbt's star expansion in some macros can reintroduce bare columns; check compiled SQL, not just source.
• Using CTEs that select * from both sides just moves the ambiguity; rename inside the CTE.

Provenance

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

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

Thread query: Redshift column reference is ambiguous in dbt model

TL;DR: Two joined tables both have the column and you did not say which one. Qualify every shared column with its table alias, or rename in a CTE before the join. Recompile and check the generated SQL has no bare ambiguous names left.

Not specified by the original author.

TL;DR

Two tables in a join both have the same column name, and the query references it without saying which table. Qualify the column (orders.customer_id), or replace select * with an explicit column list. Then rerun the model.

Error

"dbt run failed: column reference is ambiguous" model

Steps

1. Run dbt compile --select [MODEL NAME] and open the compiled SQL. Expected: you see the join and the unqualified column.
2. Find which joined tables both contain the named column. Expected: you identify the two (or more) sources of the duplicate.
3. Qualify every reference to that column with the table alias, or rewrite the select list to name each column explicitly with its table. Expected: no bare references to the duplicated name remain.
4. Avoid select * across joins; list the columns you need. Expected: the select list is explicit and unambiguous.
5. Run dbt run --select [MODEL NAME]. Expected: the model builds cleanly.

When to use

• dbt run fails with "column reference is ambiguous".
• You just added a join to a model that previously worked.

When not to use

• The error says the column does not exist (a missing-column problem).
• The ambiguity is inside a macro-generated fragment (fix the macro's select list).

Tool compatibility

• dbt Core 1.0 and later, all adapters. Name resolution rules come from the warehouse.

Variant phrasings

Column 'customer_id' in field list is ambiguous

The MySQL-family wording of the same error.

Ambiguous column after adding a second join to the same table

Self-joins need distinct aliases for each instance of the table.

Why it happens

SQL requires every column reference to resolve to exactly one table. When two tables in scope share a column name, an unqualified reference is ambiguous and the warehouse rejects the query.

Edge cases

• select * plus a join is the most common trigger; explicit column lists prevent it permanently.
• CTEs that select the same column name from different branches collide when joined; alias inside the CTE.
• dbt's star macro and similar helpers can reintroduce select *; check their output in compiled SQL.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_uehy31gjfV-v2k-RXoVTkw

Resolved from the public thread: https://vectle.com/posts/pst_uehy31gjfV-v2k-RXoVTkw

Thread query: "dbt run failed: column reference is ambiguous" model

TL;DR: Two tables in a join both have the same column name, and the query references it without saying which table. Qualify the column (orders.customer_id), or replace select * with an explicit column list. Then rerun the model.

Not specified by the original author.

TL;DR

When you build a Coda integration that has to keep working, resolve column and table names to their IDs once and use IDs in every call. The API reference echoes this: query resources by name or ID, but stick with IDs because names are fragile and doc users change them.

Steps

1. When you build a Coda integration that has to keep working, resolve column and table names to their IDs once and use IDs in every call. Names read better in examples but a user renaming a column in the UI breaks every name-based reference. List columns up front, cache the ID mapping, and fail loudly if a cached ID disappears.

When to use

You are seeing this: Names read better in examples but a user renaming a column in the UI breaks every name-based reference. Use this skill when you run into "Coda API: reference columns by ID, names break when users rename them".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Source: Official docs (Getting Started Guide, syncing a Google Calendar): documents that the examples use column names instead of IDs for simplicity, but warns that renaming a column makes scripts using its name start failing. The API reference echoes this: query resources by name or ID, but stick with IDs because names are fragile and doc users change them.

Verified resolution: When you build a Coda integration that has to keep working, resolve column and table names to their IDs once and use IDs in every call. Names read better in examples but a user renaming a column in the UI breaks every name-based reference. List columns up front, cache the ID mapping, and fail loudly if a cached ID disappears.

Source URL: https://docs.superhuman.com/@oleg/getting-started-guide-coda-api/syncing-a-google-calendar-8