You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the expected behavior when a dimension has multiple hierarchies, and one hierarchy has the defaultMember set? (or, similarly, hasAll=false).
In my case, that hierarchy works fine, but a drilldown on any other hierarchy in that dimension returns no values; inspecting the sql, it looks like the where clause includes a comparison for the defaultMember that was set manually. I don't expect that defaultMember to affect any drilldowns outside the hierarchy it's specified in, so this behavior seems strange to me.
It would be helpful if somebody could let me know if this is a bug, or if my mental model is incorrect.
The text was updated successfully, but these errors were encountered:
Hello,
What is the expected behavior when a dimension has multiple hierarchies, and one hierarchy has the defaultMember set? (or, similarly, hasAll=false).
In my case, that hierarchy works fine, but a drilldown on any other hierarchy in that dimension returns no values; inspecting the sql, it looks like the
where
clause includes a comparison for the defaultMember that was set manually. I don't expect that defaultMember to affect any drilldowns outside the hierarchy it's specified in, so this behavior seems strange to me.It would be helpful if somebody could let me know if this is a bug, or if my mental model is incorrect.
The text was updated successfully, but these errors were encountered: