KB204990: Linking a data import attribute to a project attribute resets the geographical role to none in MicroStrategy Web 9.4.1 HF3

SYMPTOM:
During the data import process in Strategy Web 9.4.1, a user can link an attribute to a project attribute, like shown below.

 
However, in Strategy Web 9.4.1 HF3, when the data import attribute is linked to a project attribute, the project attributes loses the geographical role and is reset to ‘None’ in the attribute editor, like shown below.

 
STEPS TO REPRODUCE:
In Strategy Tutorial:

• In the warehouse, create a LU table with Zip Code data.
• In Strategy Developer 9.4.1 HF 3, create an attribute from that LU table.
• In the attribute editor, set the geographical role to ‘Zip Code’, like shown below.

• Save and update the schema.
• Create an Excel file with the same Zip Code data as the LU table.
• In Strategy Web 9.4.1 HF 3, import the Excel file.
• Link the Zip Code attribute to the project attribute created in step 2.
• Save the data import cube.
• In Strategy Developer 9.4.1 HF 3, open the attribute editor.
• Notice the geographical role is set to ‘None’ instead of ‘Zip Code’.

 
CAUSE:
This is a known issue in Strategy Web 9.4.1 HF3, when linking a data import attribute to a project attribute with a geographical role.
 
ACTION:
Contact Strategy Technical Support for an update on the status of this issue.
 
WORKAROUND:
After mapping the import attribute to the project attribute, use Strategy Developer 9.4.1 HF 3 to manually set the geographical role back to its original state and update the schema.