Yeah, that's what I figured.
But all good, thanks for trying and sending some solution to test. At least I will save the XFMemberProperty reference for the future, as I think I will need it in another scenario.
I am suggesting a differente solution to the client, i.e. showing the property in a data column (using UD8) - it won't be in the exact right order but at least they will get the right information.
Thanks
It wouldn't be quite as elegant, but if you don't have a lot of entities, you could create a literal param like...
E#Entity1:U3#WBSDim.Base.Where(Text2 = Entity1), E#Entity2:U3#WBSDim.Base.Where(Text2 = Entity2), etc...
Then on your CV set Use Default Row Headers to False and make Header 1 Entity and Header 2 UD3.
That should give you the report in the style you are looking for, but it would require maintenance as entities are created.
2000+ entities 🙂
But it gives me an idea - I may be able to write a rule to return the member selection as you suggested. If the client did not change their mind I will try this.
thank you
