We sync data from multiple tenant databases and combine it in downstream dbt models, which expect corresponding tables to have the same columns.

A new column can exist in the source schema for all tenants, but have no non-NULL values for some tenants yet. In those cases, the column may not appear in the destination until data is available, causing schema differences and downstream dbt failures.

Please add an option to create destination columns based on the source schema, even when the column has no values yet. The column could remain NULL until data arrives.