The requested object with id XXXX and type 12 (Attribute) does not exist in the object context.
As a result, the Intelligent cube cannot be migrated to the destination project.
STEPS TO REPRODUCE:These are the steps to reproduce the issue, using
ProjectA and
ProjectB as the source and destination projects respectively.
1. Assuming that
ProjectA and
ProjectB are in the same metadata, create a Database Instance to connect to an OLAP data source.
2. Log into
ProjectA in Strategy Web. Select "Add External Data" and connect to an OLAP data source with the Live Connect option.
3. Save the Intelligent Cube generated. There is no need to further create a dashboard or document.
4. Log into
ProjectB in Strategy Developer. Open the MDX Cube Catalog and connect to the MDX Database Instance created in Step 1. Import the same MDX cube used in Data Import in Step2.
5. In Strategy Object Manager, migrate the Intelligent Cube created in Step2 from ProjectA to ProjectB; the error will appear.
CAUSE:This issue occurs because the same database instance is being used for Data Import and the MDX Cube Catalog. When migrating the cube, Object Manager will look for the cube components in the schema created when accessing the MDX Cube Catalog, throwing an error because the components from the MDX Cube Catalog schema and the ones in the Object Manager package have the same technical names but different unique identifiers.
ACTION:This issue has been addressed in Strategy 10.8 and 10.4 HF4.
WORKAROUND:This issue will not occur if different database instances are used for Data Import and MDX Cube Catalog.
If the issue is already present, contact Strategy Technical Support for further assistance.
The Internal Reference Number for the issue described in this technical note is DE55343.
