SYMPTOM:
In Strategy Desktop, user may find the attribute parent/child relationship does not appear in Attribute Editor when the two attributes are truly related by parent/child relationship. For example, when editing AttributeC, AttributeP shows up as its parent. However, when editing AttributeP, AttributeC does not show up as a child.
CAUSE:
One possible cause of this issue is a metadata inconsistency. For example, in the above example, AttributeP was not part of the Schema's Attributes Collection. In order to track down the cause of the inconsistency, customers encountering this issue should make note of Schema-related changes, Object Migrations, or error messages prior to experiencing the problem. Change Journaling, if it has been enabled, can help in preserving this information.
ACTION:
Please refer to the following Tech Note to run ScanMD schema collection verification test to resolve the issue.
KB35809: Using ScanMD to fix known logical metadata inconsistencies in the MicroStrategy Product Suite 9.4.x - 10.2 Hotfix1
KB295369: Using ScanMD to fix known logical metadata inconsistencies in the MicroStrategy Product Suite 10.3 and later