KB18680: When updating the table structure in the Warehouse Catalog, two columns of the identical name but different data type are designated as the same data type in MicroStrategy Architect

SYMPTOM:
When two or more columns exist in the warehouse with the same name but different data type, those two columns may become designated as the same data type when viewing them from the Strategy Warehouse Catalog.
As shown in the picture below, two columns of the same name exist in two different warehouse tables but are designated as different data types; Text and Number. Both columns also contain different data.
 

After bringing the new table that contains one of these columns into the project or updating its table structure, the data types of both columns are designated the same.
 
The column in the LU_INCOME table is designated incorrectly as a VarChar, as shown here:
 

CAUSE:
Without using the 'Do not merge' option in the read settings, Strategy will treat same name columns as if they were the same object and will overwrite its data type with either the most recent or the maximum denominator column.
 
ACTION:
Choose the Warehouse Catalog read option to `DO NOT MERGE` by following these steps:
 

• Open the Warehouse Catalog and click the `Options` button in the tool bar.
• Click `Read Settings` under the Catalog section.
• In the `Column Merging Options`, click on `Do Not Merge` as shown below:
  

• Then perform an update structure on all the tables that have this same name column.

After these steps, the same name columns will be treated as different column objects and will have their respective data types, as shown below:
 
RELATED TECHNOTE:

• KB18133: Automatic mapping does not recognize a source table with the same column name in Strategy Architect