When user navigates to "Project Tables View" tab in Strategy Architect 10.3 and click an attribute, no lines are being graphically displayed to reflect mapping to some tables. Furthermore, when editing attribute form in Strategy Architect, the editor reflects not all tables are being mapped.
When editing same attribute in Attribute Editor in Strategy Developer, all tables are displayed to be mapped.
STEPS TO REPRODUCE:
1. Access Strategy Architect.
2. Select attribute or fact impacted from "Project Tables View" tab.
3. Notice that when highlighting attribute/fact, its mapping to source tables is not being graphically displayed.
4. Edit attribute form/fact expression, to check what tables were mapped.
5. Add tables, highlight the attribute and observe that mapping is graphically reflected properly.
6. Save and update schema, close Strategy Architect and edit fact/attribute in fact or attribute editor to verify, that all selected tables are mapped.
7. Open Strategy Architect to discover that issue persists.
NOTE: Simply adding additional source tables to attribute form or fact expressions via Strategy Architect would not resolve graphical malfunction. Although once tables are mapped and Architect graphically reflects proper mapping to tables in Project Tables View tab, after saving and updating the schema, and re-opening Strategy Architect the issue persists. Furthermore, at the back end attribute or fact definitions are stored properly, which can be verified by reviewing object's definitions in attribute or fact editor.
CAUSE:
This is solely a graphical issue of Strategy Architect caused by one of metadata inconsistency types - duplicated columns. Report results or performance are not expected to be affected, as attribute or fact definitions are not impacted. It is Strategy Architet's GUI that malfunctions, as a side effect of duplicated columns.
ACTION:
Reach out to Strategy Support to assess metadata and detect columns that were duplicated.
For more information about how to prevent metadata from duplicate columns, refer to the following documentation
KB45179: Best practices for avoiding metadata issues that result from Duplicate Columns in MicroStrategy 9.4.x-10.x and how duplicate columns can be created.
Article Number: KB440045
