CurrentMember(MDX)忽略切片器尺寸 [英] CurrentMember (MDX) Ignores Slicer Dimension

查看:88
本文介绍了CurrentMember(MDX)忽略切片器尺寸的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我在角色的CellData表达式中使用CurrentMember函数来限制通过特定维度对多维数据集的访问.这是按预期方式工作,但有一个例外.即使使用切片器感知来过滤掉该角色无权查看的数据,字符串'#N/A'也会显示在所有单元格中.

I am using the CurrentMember function in a role's CellData expression to restrict access to a cube via a specific dimension. This is working as expected with one exception. Even if the slicer imension is used to filter out data that the role is not entitled to see, the string '#N/A' is displayed in all cells.

仅在轴中包含角色限制访问的维度之后,才按预期显示单元格的值.

Only after including the dimension to which the role has restricted access in an axis are the cell's values displayed as expected.

在我看来,CurrentMember函数似乎忽略了切片器的尺寸.是这样吗我应该如何解决这个问题?

It appears to me as if the CurrentMember function is ignoring the slicer dimension. Is this the case? How should I approach this problem?

推荐答案

我的建议是,严格地说,我要避免使用那些要求您使用多维数据集值限制访问的多维数据集.到那里去做,这样做浪费了太多时间,但最终还是得到了不稳定的解决方案.

My advice, in all seriousness, is to run away from cubes that require you to restrict access using cube values. Been there, done that, wasted too much time and still ended up with an unstable solution.

绝对不要在OLAP中使用角色".

DEFINATELY do NOT use 'Roles' in OLAP.

这篇关于CurrentMember(MDX)忽略切片器尺寸的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆