Just giving the names of the authors doesn't tell us which method goes with which. I know of two methods:
- Sort on an unstored calculation field that copies values from different fields in order to enable dynamic sorting.
- Put two different portals on different panels of the same slide or tab control--each with a different sort order specified in portal set up. You "sort" the portal by selecting the different tab or slide control panel.
The second option is simpler for the "newbie" to set up, but results in a more complex layout to update and maintain over time--especially if you want to enable a lot of different sorting options on different fields. Also, method 1 sorts on an unstored calculation field. This can lead to delays getting it to update if you have large numbers of related records in your portal.
can you post links to the two examples you have tested?
Which one was easier for you to test?
I see that I have provided you with a third option. My comments about "option 1" in my previous post apply equally to both methods described in the links you've now provided as they both have the same unavoidable "flaw", they sort on an unstored field so you need consider and test performance issues if you use them.
If you are always sorting on the same field, but in either ascending or descending order, I'd use method 2 from my earlier post and would only consider these other options if I need a more complex list of possible sorting options. Note that Method 2 can be set up with a bit of layout sleight of hand to make it appear to the user that there is only one portal and not two portals in different tab or slide control panels. I suppose that you could also use the Hide Object When option to control which sorted portal is visible as yet another way to "select" for a particular copy of the portal.