Signals Notebook : During SNB Material Library import the Renamed fields create new columns and hide originals

Description

When transferring configuration between tenants, renaming fields in Material Library tables does not update existing columns. The import process adds new columns with the new names and hides the old columns to preserve data integrity and avoid type conflicts. This is expected behavior by design.

In Signals, the configuration transfer/import logic for table columns is not a “rename-in-place” operation. It reconciles columns between the source (DEV) and destination (TEST) using presence/type matching rules—so a “rename” can be interpreted as (a) a new column + (b) hiding the old one rather than updating the existing column.

Why this can look “allowed in the UI but different on export/import”: The UI lets you rename a column label in the table configuration, but during configuration transfer, Signals One uses the column identity/type reconciliation rules rather than your “intent” to rename.

Understand behavior:

During configuration transfer, Signals handles Table Configuration columns with rules like these:

• Columns that exist in the source but not in the destination will be added.

• Existing columns in the destination but not in the source will be hidden.

• For columns that exist in both source and destination:

  • If same type → the destination column is updated with the source property settings.

  • If different types → the system will add a new column and hide the existing one.