Using the standard syntax to filter on an attribute returns the context error as the MDX is ambiguous.
Using the following code does not work as the value being evaluated seems to be something other than 1:
Code: Select all
{FILTER(
{TM1FILTERBYLEVEL( {TM1SUBSETALL( [<dim>] )}, 0)},
[<dim>].CurrentMember.Properties("<attr>")="1")}
Getting a bit more creative, the following does seem to work:
Code: Select all
{FILTER(
{TM1FILTERBYLEVEL( {TM1SUBSETALL( [<dim>] )}, 0)},
INSTR(1,[<dim>].CurrentMember.Properties("<attr>"),"<value>",0)>0
)}
-Any better ideas to get the MDX more simple for future reviewers/maintainers?
-Anyone know what is returned by [<dim>].CurrentMember.Properties("<attr>") other than a plain old 1?
-Any way to TRIM the result - tried trim, rtrim, ltrim?
-Is there a way to fully qualify the attribute within the MDX, similar to how you would need to address ambiguous elements in Rules?
And lastly, yes, I could have changed the name of the attribute as an easy way out but where's the challenge then?