What It Is
- In the Celigo Platform 2025.4.1 release, Celigo introduced a data-handling feature that automatically uses null as the default value for empty source fields in supported import applications. Previously, integrators had to manually configure default values for each field, which sometimes results in inconsistencies or unexpected data especially when source data was incomplete.
Need to Use
- Manually mapping defaults for empty fields not only increases the setup workload but also brings risk: inconsistent data processing, inaccurate records, or unintentional overwrites. With this new behavior:
- Setups become simpler — no default configuration necessary for frequent sources.
- Mapping consistency is increased across multiple import apps.
- The risk of data pollution or unintended updates due to unfilled fields is greatly reduced.
- It’s particularly valuable for users dealing with bulk data imports from file storages or databases, where empty fields are common.
Key Benefits
- Streamlined Configuration: Eliminates repetitive manual setup by defaulting all empty source fields to null. Support spans across a wide range of connectors: databases (like MariaDB, MySQL, Oracle, PostgreSQL), data warehouses (e.g., Snowflake, Redshift, BigQuery), and file storages (such as Google Drive,).
- Improved Data Integrity: Reduces the risk of unintended values creeping into your target systems, keeping your mappings clean and predictable.
- Enhanced Efficiency: Speeds up integration development and maintenance by adopting sane defaults that are widely applicable.