Yes I fully agree. The sorting by dataform values in a ListPages module which was released recently is brilliant, but would be even more powerful if sorting on multiple columns was possible. I raised this in the wish related to dataform date fields at http://feedback.wikidot.com/wish:365/comments/show#post-1345343 but have not had any response yet from the developers

Any chance this can get some attention? I have a use case where I'm using data forms to track training status for employees who work at multiple restaurant locations. Ideally, i'd like to be able to sort like this:
_location
   _lastname
       _firstname

Code Example

[[module ListPages category="trainingchart" _shop="@URL" order="_shop, _lastname, _firstname" ...]]
<ListPages Output>
[[/module]]

The other option is to try and manage this via the API, but that is pretty cumbersome for something like this where having multiple sort levels would easily solve my problem.

would help to have a (hidden?) dataform "field type": "connected" fields=(…,…,…) .. but this is only a work around than to use such intermediate storage field..
perhaps this is easier to implement?

Using a data form field to specify the sort would work, but the users will think it's silly to enter the sort parameters, constructing it from data they have already entered. They would not understand why it's necessary. First, I ask them to fill in (among other things) the field data used for display proposes (shop, lastname, firstname). Then I'd have to provide a "sort field" and tell them to enter it as "shop[space]lastname[space]firstname" (or something similar) so I can use that field for sorting. Not really a solution for me. There would be too many opportunities for errors or non-compliance.

If we could sort by tags, I could use the set-tags to construct a "Confirm Sort Order" button and construct a tag from form data fields like "shop-lastname-firstname", but it doesn't help because ListPages doesn't have an option to sort by tags (and I'm don't think it's necessary unless a multilevel sort option is too hard to implement).

My current solution, which gets me 2 levels of sort, is to construct links with URL parameters and then use "@URL" in list pages. I can select by "_shop" and order by "_lastname". This is workable for me until this wish is granted. The only negative is when I want to list all shops. I have to order by "_shop" and let the rest of the sort fall where it may.

I have 21 shops and nearly 1000 employees that we are tracking training status for, so @URL works well for filtering and sorting the data for now.