Hi, thanks for replies.
Why not just change the sorting order of the source so that when you build the hierarchy it is sorted in the order you want?
seems like the DIMENSIONSORTORDER would sort byinput but as soon as I hierachizes it returns to the original way I loaded it (not ASC for description ALIAS -which is what the input order is), cant see why it should do this, maybe because the data was in this order prior (I do a DimensionDeleteAllElements evenand it still returns to original order in Heirachize). Might be because the sort I want is on an alias.Gave up on that one.
Are you saying that the TM1Sort breaks the hierarchy and you are trying to preserve it or are you saying that what does get ordered is incorrect.
If you want to preserve the hierarchy you can use Hierarchize
no, trying to get the Nth leaf elements in ASC order based on a Alias name, so TM1DRilldownMEMBER does not help either as it doesnt allow not in Nth leaf level sort
I tried
Code: Select all
{ORDER( {FILTER( {TM1SUBSETALL( [Employee] )},[Employee].[Existing] = "Y")}, [Employee].[Description], ASC )}
but didnt seem to order by Description (the Alias). Where as below did sort
Code: Select all
{TM1SORT({FILTER( {TM1SUBSETALL( [Employee] )},[Employee].[Existing] = "Y")}, ASC)})}
I think I may have to stick with the original UNION method....