I was hoping to get some clarification on using Custom Attributes for security per this article:
https://www.dundas.com/support/learning/documentation/administration-configuration-customization/how-to/using-a-security-hierarchy-to-filter-data-by-user
Here is the scenario:
2 data cubes, SalesHeaders and SalesDetails, both with a Company dimension containing CompanyA, CompanyB and so on.
I set up a Custom Attribute called Company and changed the Company dimension in each data cube to use this Custom Attribute as a security hierarchy.
I create a dashboard that has two metric sets, one from each data cube, that both are filtered by the same view parameter vpCompany based on this company dimension.
I go into a user account and add Custom Attribute Company and add the SalesHeaders Data Cube, setting only to value Company A.
This works correctly: in my dashboard metric set linked to SalesHeaders, I can only see Company A.
I go back into user account and edit the Custom Attribute Company and add the SalesDetails Data Cube, setting only to value Company A.
This does not work and I can no longer see CompanyA in my SalesHeaders metric set anymore.
It appears that each data cube must use a different Custom Attribute, ie: CompanyForSalesHeaders, CompanyForSalesDetails, and that I must add each of these Custom Attributes to my user account and within each, set only the corresponding Data Cube.
That’s fine, but then why does the Custom Attribute allow you to add more than one data cube if it isn’t going to work? Is it because I’m not using a shared hierarchy between these two data cubes?
