Skip to main content

Error: Invalid Identifier

Error​

If you receive an invalid identifier error when running or creating a Node in Coalesce, this typically means your Node is referencing a column or table that doesn't exist in your data platform. The error message will usually indicate which line in the generated SQL is causing the issue.

Possible Causes​

  • Wrong identifier quoting for your Project platform: Coalesce generates double-quoted identifiers on Snowflake Projects and backtick-quoted identifiers on Databricks and BigQuery Projects. Hand-written identifiers that use the wrong style, or Snowflake examples copied into a Databricks or BigQuery Project without updating quotes, often cause this error. See Quoted Identifiers in Coalesce.
  • Case sensitivity issues: Mixed-case column names must match the quoting style for your platform. On Snowflake, wrap identifiers in double quotes or use uppercase unquoted names. On Databricks and BigQuery, wrap identifiers in backticks when case matters.
  • Column doesn't exist in source table: The column you're referencing may have been removed, renamed, or never existed in the upstream source table.
  • Source table changes: The upstream source table structure may have changed since you last synced columns in Coalesce.
  • Missing or incorrect table aliases: If you're using aliases in joins or references, make sure they match exactly what you've defined in your SQL.
  • Upstream dependency issues: The table or Node you're referencing may not have been created successfully in your data platform yet.

How to Troubleshoot​

  • Check the SQL tab: Look at the generated SQL to see exactly which column or identifier is causing the issue. The error message will provide a line number to help you locate the problem.
  • Match platform quoting: Confirm hand-written identifiers in Transforms and the Join tab use double quotes on Snowflake and backticks on Databricks or BigQuery. Verify that helper tokens and ref functions expanded with the expected quoting style.
  • Resync columns: Go to your source Node and click Resync Columns to refresh the column metadata from your data platform. This ensures Coalesce has the latest column information.
  • Verify column names: Double-check that the column names in your mapping match exactly what exists in the source table, including case sensitivity.
  • Check upstream dependencies: Make sure any upstream Nodes have been created successfully before trying to reference them. Run the Create operation on upstream Nodes if needed.
  • Review table aliases: If using aliases in your SQL, verify they match exactly what you've defined and are used consistently throughout your query.