KB4587: 'Column %1's data type %2 with precision %3 scale %4 is not supported' error message appears when running a report in MicroStrategy Architect 9.x

SYMPTOM:
The following error is received in Strategy Architect 9.x when opening an attribute to view the attribute elements or when running a report in Strategy Desktop 9.x:
sqlengine got an exception dfc:{dfcengine}engine logic:the column %1's data type %2 with precision %3 scale %4 is not supported error in process method Error in process method of component: sqlengineserver, project 3, job539, error code equals -2147212800
 
CAUSE:
This error may occur when there is an inconsistency between how the attribute is defined in Strategy Architect 9.x and the data warehouse.
 
ACTION:
Change the datatype in Strategy Architect 9.x so that it is consistent with the definition in the warehouse.
 
To change the attribute datatype definition, please execute the following:

• Open Strategy Architect 9.x and go to Schema Objects > Attributes > 'Attribute Name'.
• Right-click on the attribute name and select 'edit'.
• A new window with the attribute definition, shown below, appears.
   
  

• There are two datatype settings that must be defined. In the figure shown below, the data format on 'Country' must closely match the datatype defined in the database. In this example, Country’s ID form is defined as a 'Number', and in the database it is defined as an integer. This is expected to be a valid data type match, since ‘Number’ is the correct Strategy logical data type corresponding to the Integer physical data type.
  

• Click on the 'Column Alias' tab at the top of this window. This datatype is used in the SQL generation of temporary tables and must match the datatype defined in the data warehouse.
   
  

• After changing the datatypes in the schema, go to Schema > Update Schema for the appropriate changes to take effect.

 
Notes:

• This issue may also result from an inconsistency in the column alias object. If it is a custom column alias created by the user, it may be sufficient to edit the column alias, save the change, and update schema. If this does not resolve the issue, it might be necessary to create a new custom column alias for the attribute form.
• Column aliases created by Strategy when importing tables from the warehouse in the Warehouse Catalog cannot be edited by the user. If this issue occurs with an imported column alias, creating a custom column alias with the correct properties can often resolve this issue.