We use custom views as security filters on a Transformer cube. If the logged on user only has access to the children of one member, it removes the parent member and just shows the children. This is not just a display issue - it actually logically removes it whenever Cognos resolves a MUN. This results in broken reports because the report author, who has access to everything, sees the longer 'true' MUN but the report viewing user has a shortened MUN. Let me try to provide an example (fictitious). Assume a company has the following organizational dim.
Business Units
-- Construction
---- Residential
---- Commercial
---- Highways
-- Retail
---- Clothing
---- Gifts
---- Arts
-- Dining
---- Casual
---- Gourmet
---- Catering
Assume a viewer is apexed to just Retail. Such a viewer will only see:
Business Units
-- Clothing
-- Gifts
-- Arts
But the report author sees the entire hierarchy. As a result, the full MUN is recorded in the report, but the viewer cannot resolve it because they are "missing" a level. Something like the following.
Report Author => [cubename].[Business Units].[Business Units].[Retail]->:[PC].[@MEMBER].[Clothing]
Report Viewer => [cubename].[Business Units].[Business Units]->:[PC].[@MEMBER].[Clothing]
At first I thought this had to do with Transformer level properties of inclusion, but I set all levels to "Always include" but it made no difference. Is there a setting somewhere that changes this behavior? I just want Cognos to recognize that "missing" level so the reports run regardless of the viewers breadth of access.
I hope that conveys the problem. I made this up in my head so my notation could be slightly off, but I am hoping you get the general idea of the problem.
Problem is you are dragging and dropping the categories instead of using MDX functions.