Re sorting of hierarchical lists, I can understand that one might want to look at projects in sequence with the more critical ones first (i.e sort on calculated-score of the project), and then look for a next action for each one (based on calculated-score of active items within the project). But that can't be done in MLO, it seems the secondary sorting works after the Next Items are picked out, so there is nothing left to be sorted at that level. So we need to use work-arounds.
Laurence