I'm using UPDATE CUBE statements but I need to protect against upper level
updates. Querying the cube for each member is too costly so I'm looking for
an MDX option (or a cube setting to ignore all upper level updates). Right
now I'm wrapping each member name in:

StrToMember(Iif(IsLeaf([membername]), "membername", "[$$NOT_LEAF$$]"))

Obviously $$NOT_LEAF$$ is a valid member in the cube and the update will
fail.

Exceptions as flow control isn't very elegant so I'm looking for a better
option. Thoughts?

-zoltan

You could use cell-level write security, but I'm sure it's worth the hassle.

Who/what are you trying to protect against? Your own actions, users'
mistakes or intentional malicious changes?

--
Hope this helps

Marius


"Zoltan Grose" <zgrose (AT) mac (DOT) com> wrote

My company's application drops a CellSet into Excel and/or allows the user
to simply enter member names into a spreadsheet cell. So when the
application goes to upload data, there is no metadata associated with the
text, for example, "Financial Services". Is that a leaf? Is it a parent? Who
knows. What we *don't* want is a value to be allocated to its children. The
end user may see a entire hierarchy, but we only want leaf-level updates to
apply.

Complicating the matter is we usually have ragged dimensions so level based
security doesn't really work too well whereas it is fairly elegant in other
dimension types.
-z


"Marius Dumitru" <mariusd (AT) online (DOT) microsoft.com> wrote