listObj.setOrder with Date/Time

[nlk10010]

I am trying to sort, on the client side, the contents of a List object by a column containing a date/time field (and in descending order). The source of the list is an SQL data source. The field is in the format 'MM-dd-yyyy 0h:0m a' and displays in the correct order when it is returned by the SQL query. However, when the user edits a row and changes the date (I am using the "unbound model with a detail view") the setOrder doesn't seem to respect am/pm.

My javascript (in the Click event of the Save button after the data is posted) is simply

lObj.setOrder({'EventDateTime:date:MM-dd-yyyy 0h:0m a' : -1});

(lObj is previously set to the List control). The setOrder does execute but the reordered list will show, for example, 12-21-2020 12:01 am above 12-21-2020 1:00 pm (remember, this is a descending order sort). In the online help for setOrder it gives examples for a date, but not for a date/time. I have tried using :datetime: in place of :date: in the above code, also :time:, nothing seems to work. I SUPPOSE I could try sorting by a function but that seems overkill. As I say, the data is (of course) properly sorted when returned by the SQL query, is my only alternative then to do a "server-side" refresh after the Save.?

BTW, there doesn't seem to be any way to set a refresh to occur automatically through the standard Save button provided in the Detail view. I would probably need to add it in javascript (perhaps inside a "setTimeout") in the click handler.

Thanks in advance for any ideas.


Norman

[Al Buchholz]

Can you set the format of the sort data to a 24 hour clock?

[nlk10010]

I can, come to think of it that would work, it's just that I know my client is going to say something like: "WTF is this?". :0

For now I've set up a setTimeout with a function that does a List refresh, that seems to work. I don't think the delay in the callback will be noticed, certainly it won't be nearly as annoying to the client as the 24-hour format. Please don't misunderstand me, I appreciate your post and it would solve the problem in most circumstances. Besides, I'm curious if setOrder can be set to sort with 12-hour format, it's a much more "efficient" way to do it.

Thanks for posting and offering the help.

[hershybook]

Maybe you could sort on a hidden column that's 24 hour?

[nlk10010]

Hmmm, that's a possibility, a hidden, computed column in 24-hour format. In essence, it's what a client-side sort should be doing, and is probably "equivalent" to using a javascript function to sort with "setOrder". Perhaps if the time lost in making the callback becomes a problem I will consider it.

Thanks, that's certainly an idea to keep "in my back pocket".

[nlk10010]

Just for the benefit of others who MIGHT need it: I finally decided to "bite the bullet" and use a javascript function to sort on the client side. The code I'm using is

lObj.setOrder( function(a,b) {
return (new Date(b.EventDateTime) - new Date(a.EventDateTime));} )

where, of course, the Date/Time field is "EventDateTime".

Seems to be pretty speedy and I certainly didn't expend a lot of effort writing it.


Norman