SYMPTOM:
A user or group of users with a security filter execute a report in Strategy Desktop and get the following error:
'Fact does not exist at a level that can support the requested analysis'
Users without any security filter can execute the report successfully. The attribute specified in the security filter is not present in the report template or in the metric definition.
CAUSE:
The fact used in the report is mapped to a table that contains a reference to the attribute used in the security filter. Strategy will detect if one of the tables used as source tables contains a reference to the attribute. If it finds that a table has a reference to the attribute, the security filter will be included in the SQL generation. If there is no table or join condition that supports a reference to both attributes at the same time the error appears.
In the example shown above, the fact is mapped to two different fact tables. Each fact table contains the fact at different levels, with no shared attributes. If a security filter is applied on top of any of the two attributes this filter will always be applied in the report.
This is working as designed, the security filter is intended to be the most restrictive form of filtering.
ACTION:
Create two facts each with its own logical table. Each fact table will have its own set of metrics. In the example shown above, instead of mapping the Dummy Fact to both logical tables, create a new fact and map one table to each fact. Changes in the data model might be needed to achieve the desired result, please contact Strategy Consulting Services if assistance is needed regarding changes to the data model.
