维度下不可见的属性层次结构
以下是报告中使用的 mdx 查询的片段。
与成员[措施]。[借入硬币] ([机器尺寸].[租赁旗帜].&1,[措施].[投币])
现在，我的问题是： 在机器维度下的多维数据集中，没有名为租用标志的属性层次结构名称。 我查看了xmla脚本，没有这个名字。但是，mdx 查询会提取结果。
如果它是隐藏的，为什么它不会在 xmla 脚本中显示为隐藏/不可见或其他什么？
如果我遗漏了某些内容，那么我如何追踪它以找出它与机器尺寸的关系。
感谢您的帮助。
Below is the snippet of an mdx query used in a report.
with member [Measures].[Leased Coin In]
([Machine Dimension].[Leased Flag].&1 , [Measures].[Coin In])
Now, my question is:
In the cube under Machine Dimension, there is no attribute hierarchy name called Leased Flag.
I looked at in the xmla script, there is no such name. But, the mdx query pulls result out.
If it is hidden, why does not it appear in the xmla script as hidden/invisible or whatever it is?
If I m missing something, then how do I track it back to find out how it is related with the machine dimension.
Appreciate your help.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您是否尝试过在 SSMS 中运行查询？ &1 不是有效的标识符。标识符必须以字母字符开头或用方括号分隔。
可以编写引用不存在的层次结构或成员的计算度量，但它只会返回 null。然而，对 &1 的引用甚至不应该通过查询评估的解析阶段而不抛出错误。
Have you tried running the query in SSMS? The &1 is not a valid identifier. Identifiers must start with an alpha character or be delimited with square brackets.
It is possible to write a calculated measure that references a non-existant hierarchy or member, but it would just return null. However a reference to &1 should not even get past the parsing stage of the query evaluation without throwing an error.
旧消息，但对于那些谷歌搜索的人来说：
当您看到类似 [Dimension].[Hierarchy].&[1] （我假设输入消息时 1 周围的 [ ] 被省略）之类的内容时，它指的是属性中成员的键与成员的标题相反。
您看到此情况的典型位置是在使用 Dimension Security 并查看“高级”选项卡或选择“默认成员”时。这使您可以在不破坏多维数据集逻辑的情况下重命名成员。
Old message but for those googling:
When you see something like [Dimension].[Hierarchy].&[1] (I'm assuming the [ ] around the 1 were just left out when entering the message) that is referring to the key of the member in the attribute as opposed to the caption of the member.
The typical place you see this is when using Dimension Security and looking on the Advanced tab or when choosing a Default Member. This lets you rename a member without breaking your cube logic.