I've run in to a strange problem that seems like a bug:
I have a Place-dimension with two hierarchies like this (simplified):

H1:
Lvl1 (key: lvl1_id, name: lvl1_name)
Lvl2 (key: lvl1_id + '.' + lvl2_id, name: lvl2_name)
Lvl3 (key: lvl1_id + '.' + lvl2_id + '.' lvl3.id, name: lvl3_name)

H2:
Lvl1 (key: lvl1_id, name: lvl1_name)
Lvl3 (key: lvl1_id + '.' + lvl2_id + '.' lvl3.id, name: lvl3_name)


I have to use unique keys, and to do that, i have to combine the id:s from
each level.
To reference a member I use for instance: [Place.H1].&[123.345.678]
But suddenly, at the production server, the expression above returns a
completely different member.
A reference to a member on Lvl3 returns one member at Lvl1. It's really
strange, because it has worked fine until now, and it still works fine at
our development server which uses exactly the same datasource and an exact
copy of the cube. And it seems related to that I have two hieararchies,
because when I remove the H2, it works fine again. But as soon as I add it
again, the problem comes back.

Regards
/Magnus

Just want to say I found the problem. Lvl3 is a quite large level (~2000
members), and when I increased the Large level setting, things work as
supposed again. I still find it a bit strange that no error msg was
displayed like "member not found", but instead an other member was returned.

Also if i specicy the member name by [Place.H1].[Lvl3].&[123.345.678], it
finds the member even without changing the large level property. Maybe
that's a more efficient solution, but then I have to rewrite some
application logic for constructing the MDX-statements, so that will have to
wait.

/Magnus


"Magnus" <knutsture (AT) hotmail (DOT) com> wrote