Use User Null Assignment
Specifies whether all non-key columns should be set as nullable or if their nullability is determined by user-defined input. It's advised against setting columns as non-nullable, as this may result in data load failures.
When enabled, the generated tables take each column's nullability directly from the column metadata. When disabled, BimlFlex applies its standard rules: key columns (primary keys, Integration Keys, and staging source keys) are non-nullable, and other columns in the staging-layer tables (STG, PSA, EXT, LND) are nullable regardless of the metadata.
When to Change This Setting
Keep the default N — the standard rules keep the staging layers tolerant of incomplete source data. Enable it only when column nullability has been deliberately curated in the metadata and must be enforced as modeled, accepting that loads fail when the source delivers NULL into a non-nullable column.
Related Settings
| Setting | Interaction |
|---|---|
| Add SQL Defaults | The equivalent nullability control for the BimlFlex system columns |
Notes
- This setting is part of the Core settings category.
- The default value for this setting is
N.