KB323289: Duplicate columns are created if Warehouse Catalog is not saved between updating table structure and importing a new table in MicroStrategy Developer 10.x

SUMMARY:
This document shows one known issue that duplicate columns would be created if Warehouse Catalog is not saved between updating table structure and importing a new table. This is a known issue in Strategy Developer 10.x. The workaround is to always save and close Warehouse Catalog between updating table structure and importing a new table. 
 
SYMPTOM:
Duplicate columns are created if Warehouse Catalog is not saved between updating table structure and importing a new table in Strategy Developer 10.x
 
STEPS TO REPRODUCE:
1. Suppose table A has been imported into Strategy project and there are some attributes and facts mapping to table A.
2. In Warehouse, alter table A and add a new column Col1 into table structure of A. Create a new table B with same column Col1.
3. In Strategy Warehouse Catalog, update table structure of A to bring column Col1 into project.
4. Do not save and close Warehouse Catalog. Continue importing table B into project. 
5. Save and close Warehouse Catalog. Two column objects called same name Col1 were created in the project. 
 
ACTION:
This is a known issue in Strategy Developer 10.x which will be fixed in Strategy 10.8.
 
WORKAROUND:
Duplicate columns are created only when Warehouse Catalog is not saved between the following two actions:

• Update table structure to bring a new column into project.
• Import new tables to bring same new column into project.

 
One workaround is to always save and close Warehouse Catalog between updating table structure and importing new tables. 
 
Note: Duplicate columns are not created in the following two scenarios:

• Case 1:

1. Update table structure of one table to bring a new column into project.
2. Do not save and close Warehouse Catalog.
3. Update table structure of another table to bring same new column into project.

• Case 2:

1. Import one table to bring a new column into project.
2. Do not save and close Warehouse Catalog.
3. Import another table to bring same new column into project.