Some MDX functions not allowed in Workspace?

Post Reply
User avatar
PavoGa
Community Contributor
Posts: 264
Joined: Thu Apr 18, 2013 6:59 pm
OLAP Product: TM1
Version: 10.2.2 FP7, PA2.0
Excel Version: 2013
Location: Cleveland, Tennessee

Some MDX functions not allowed in Workspace?

Post by PavoGa » Thu Oct 25, 2018 9:07 pm

This MDX subset errors in Workspace:

Code: Select all

{StrToMember("[Version].["+[}elementAttributes_sys.Clients].(StrToMember("[sys.Clients].["+username+"]"), [}elementAttributes_sys.Clients].[Default Version])+"]")}
We've used this for years to default the Version dimension's title element in our views. Works in web sheets, but returns an error for a view in Workspace. Is there another method for achieving the same thing?
Ty
Cleveland, TN

User avatar
PavoGa
Community Contributor
Posts: 264
Joined: Thu Apr 18, 2013 6:59 pm
OLAP Product: TM1
Version: 10.2.2 FP7, PA2.0
Excel Version: 2013
Location: Cleveland, Tennessee

Re: Some MDX functions not allowed in Workspace?

Post by PavoGa » Wed Nov 21, 2018 6:19 pm

Forgot to include the error message:
Failed to Filter members.
Could not execute MDX expression.
Unknown error.
What we are doing is using a version dimension where some versions are "active" and the rules calculate on those versions and other versions that are static. For the active versions, different user bases working in, so the users select which version they wish to default work in and all their views, and some TI's, automatically use that default version.

But PAW does not like the subset MDX we are using. Just wondered if anyone else has run into this and worked out a solution?
Ty
Cleveland, TN

User avatar
PavoGa
Community Contributor
Posts: 264
Joined: Thu Apr 18, 2013 6:59 pm
OLAP Product: TM1
Version: 10.2.2 FP7, PA2.0
Excel Version: 2013
Location: Cleveland, Tennessee

Re: Some MDX functions not allowed in Workspace?

Post by PavoGa » Wed Nov 21, 2018 6:48 pm

Finally did a little work instead of just assuming something was wrong with the MDX.

PAW appears to, for lack of better of description, "lose" one's user identity. What was happening below is that username was returning "admin", not the actual user's name. Logged out of PAW, logged back in and the subset works fine (admin did not have a default version assigned).

Has that feature been documented by anyone? Anyway to prevent it?
Ty
Cleveland, TN

Post Reply