KB485767: Missing dependency is reported when importing package contains dossier with MDX report as the dataset

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Symptom

When importing a package containing a dossier with MDX report as the dataset, you may encounter missing dependency errors like this:

source manipulator found a missing dependency. 
Object: Attribute id=0590602843C1EB2B826328B8C82B6956 is not found. A total of 2 object(s) need it, one of which is 2.Finance Report Definition id=D25959A1442E5F09758991A6309F10A0

Steps to reproduce

The problem usually happens with below steps:
1. End user exporting dossier with MDX report(s) as the dataset into a mstr package file, e.g. Dossier1.mmp, from Project A. The dossier should be exported with all dependencies.  In the dependency list,  the missing attribute (e.g.

0590602843C1EB2B826328B8C82B6956

mentioned in the above error message) could be observed. 
2. Importing the mstr package Dossier1.mmp into a new project , e.g. Project B.  In project B, the dossier could be executed successfully without any problem.  And the missing attribute (e.g.  

0590602843C1EB2B826328B8C82B6956

) could also be found in Project B. 
3. Re-export the same dossier again from Project B into mstr package file, e.g.  Dossier2.mmp. Even though “Add all dependencies“ is selected, the missing attribute (e.g.  

0590602843C1EB2B826328B8C82B6956

) could not be observed in the dependency list. 
4. Importing the mstr package Dossier2.mmp into another project, e.g. Project C. This time, the package importing process will be interrupted by error:
 

source manipulator found a missing dependency. 
Object: Attribute id=0590602843C1EB2B826328B8C82B6956 is not found. A total of 2 object(s) need it, one of which is 2.Finance Report Definition id=D25959A1442E5F09758991A6309F10A0

 

Cause

After investigation, the error starts from step1 when exporting the dossier from Project A.  
In step 1, during the package generation, MDX dimensions try to find the correct Schema, but failed due to the wrong search scope. Due to failure to find the right schema for MDX dimensions,  MDX dimensions are set to Relational type ( i.e.

DssXDATypeRelation

) instead of MDX ( i.e.

DssXDATypeMDX

).  
In step 2, since MDX dimensions are marked as

DssXDATypeRelation

, they are wrongly added into the project schema, instead of the right MDX schema, even though the MDX schema still has the right reference to those MDX dimensions. 
With the above error, it finally leads to the attribute missing error. ( More detailed analysis could be found in the defect discussion in DE192539. )
 

Action

We have provided the fix for the error in step 1 in Strategy 2021 Update 7 (M2021 U7). Since M2021 U7(Both Intelligence Server and ObjectManager/Workstation should be M2021 U7 or higher version), please re-export the dossier from the original project and import the package to the target again. 
 

Workaround

If you haven’t upgraded to Strategy 2021 Update 7 yet, please contact Strategy Support Team to apply a workaround for your metadata.