This technical note outlines a known issue related to running reports combining SQL and MDX objects as users with security filters unmapped to MDX attributes.
Users may experience an issue when trying to run reports as Strategy users with security filters. If a user with a security filter on a SQL attribute unrelated to any SQL attributes mapped to MDX attributes tries to run a report, the following error will occur:
"No MDX cubes found to support MDX Metric "XXX" at level {<Report Attribute>, <Unrelated Security Filter Attribute>}"1. Add any MDX cube with Year-level data to the Tutorial project.
2. Map one of the MDX Year attributes to the Tutorial Year attribute.
3. Create a report with the Blank Report template and add the Tutorial Year attribute and an MDX metric into the template.
4. Run the report as the administrator with no security filter and data is returned.
5. Run the report as Paula Roe (user with security filter on Manager, disabled by default) and the report will return the error mentioned above.
This is a known issue in Strategy Engine 9.x. The MDX engine sees the security filter associated with the user and tries to apply it but cannot.
Upgrade to Strategy 10.x. In 10 multisourcing is used to allow the filter to apply even if unrelated to avoid the error and permit reports to run.
Map the security filter attribute(s) to MDX attributes in the cube to potentially bypass the issue.