SYMPTOM:
Consider that a new table 'NEW_TABLE' is to be added to a project through Warehouse Catalog in Strategy Developer 9.4.1. This table contains two columns: SID_ID and NEW_COL, as shown:
Additionally, a table 'LU_STORE' which is already part of the same project, also has this identical column 'NEW_COL' added to it. Hence, the structure of this table is updated by right-clicking it in Warehouse Catalog and selecting 'Update structure' as shown:
This adds the column to the 'LU_STORE' table as shown:
Now, 'NEW_TABLE' is added to the project and Warehouse Catalog is saved and closed:
Next, consider that an attribute form mapping to the 'NEW_COL' column is to be created, and the mapping method is set to be Automatic, as shown:
Automatic mapping does not recognize 'LU_STORE' to be a source table, even though the table contains the 'NEW_COL' column as described before:
CAUSE:
When the table is added to the project, and the existing table containing the column also present in the new table is updated, duplicate columns are created in the project. Although these columns appear with the same name from Strategy Developer 9.4.1, they are distinct in the metadata, which is why automatic mapping does not recognize all source tables.
This is a known metadata inconsistency in Strategy 9.4.1.
ACTION:
Strategy will continue to investigate and post updates as soon as they are available.
WORKAROUND:
In the scenario described above, perform the following steps to workaround the issue:
This process creates the column 'NEW_COL' in the first step, and the same column is re-used when updating structure of the existing table in the fourth step.
