Database Generation Failure Due to Column Data Type Mismatch

Database generation can fail with a type mismatch error when a column is defined with different data types across related tables. This commonly occurs when the same field exists in both a source domain table and a database table but is configured with inconsistent data types.

Common Error Message

Failure binding configured inputs to resolved state:
type mismatch for field <column_name>
(config: <type>, state: <type>)

Root Cause

This error occurs when a column’s data type in a source domain table does not match the data type defined in the corresponding database table. During database generation, the system validates that schemas align across all inputs. If a mismatch is detected (for example, a column defined as INTEGER in the source and STRING in the database), the generation process fails.

Resolution

• Identify the column listed in the error message.

• Compare the data type of that column in:

  • The source domain table

  • The database table

• Update the schema so the column data types match across all related tables.

• If the table causing the conflict is no longer required, removing it from the sandbox or workflow can also resolve the issue.

Once schemas are aligned or unnecessary tables are removed, database generation should complete successfully.

Best Practices

• Keep column data types consistent across source domain and database tables.

• Review schema changes carefully before running database generation.

• Remove unused or obsolete tables from sandboxes to avoid validation conflicts.

• Re-run database generation after any schema updates to confirm success.