Again to reiterate, retrieving all users in this way, especially if you then page results of your new sorted list, is going to be quite expensive. At that point it might be better to set up a custom data store (i.e., your own database table) that keeps your custom fields referenced by userid, and then use the user list API and provide a list of ids via the ContentIds option with SortBy=ContentIdsOrder. Then you can return that pre-paged, pre-sorted list via your widget extension.
Hi Stephen,
Could you please explain this procedure a bit more. What would I pass into my widget extension method, and what would I pass out? What would be the pseudocode for the procedure?
You need a custom table to store whatever you want to sort y and the contentId and any associated code to make your call. That list of Ids can be passed to the User list and be returned in the same order.
