ApplyQuery Sort Order

Hi,I've found that when I use the LAPI ApplyQuery() function with the SORTBYREGION option, the results are returned in descending/reverse order. For example, if I search on the OTName region, the results are returned alphabetically from Z to A. Similarly, if I search on the OTCreateDate region, the results are returned newest to oldest. I need the search results to be returned in ascending order (A-Z), but I cannot figure out how to do this. Is there a setting somewhere that controls this behaviour? I was going to just traverse through the search results in reverse order (i.e. starting with the last record returned), but then I realized that that won't work if there are more matches than records returned (i.e. the "forhowmany" parameter). Does anyone have any other workarounds for this issue?I'd definitely appreciate any suggestions/tips!Thanks,AmyPS--I'm running Livelink 9.1 SP3 and am using java as my programming language

Find more posts tagged with

Comments

eLink User

Message from Michael Jory via eLinkThis is not currently possible. We are examining it as a feature request. Hope this helps! Mike> -----Original Message-----> From: eLink Discussion: LAPI Discussion> [mailto:lapi@elinkkc.opentext.com]> Sent: March 17, 2003 12:19 PM> To: eLink Recipient> Subject: ApplyQuery Sort Order> > > ApplyQuery Sort Order> Posted by agordon on 03/17/2003 12:07 PM> > Hi,> I've found that when I use the LAPI ApplyQuery() function with > the SORTBYREGION option, the results are returned in > descending/reverse order. For example, if I search on the OTName > region, the results are returned alphabetically from Z to A. > Similarly, if I search on the OTCreateDate region, the results > are returned newest to oldest. I need the search results to be > returned in ascending order (A-Z), but I cannot figure out how to > do this. Is there a setting somewhere that controls this behaviour? > I was going to just traverse through the search results in > reverse order (i.e. starting with the last record returned), but > then I realized that that won't work if there are more matches > than records returned (i.e. the "forhowmany" parameter). Does > anyone have any other workarounds for this issue?> I'd definitely appreciate any suggestions/tips!> Thanks,> Amy> > PS--I'm running Livelink 9.1 SP3 and am using java as my > programming language> > > [To reply to this thread, use your normal e-mail reply function.]> > ============================================================> > Discussion: LAPI Discussion> https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765428&objAction=viewLivelink Server:https://knowledge.opentext.com/knowledge/livelink.exe

Mario_Dzeba_(marshladmin_-_(deleted))

Dear eLinkI wonder if anyone can comment on the following. If you have a number of results dispayed in descending OTCreation Date sort order and you have a number of items say -1. Document A - Creation Date 16 October 20042. Document B - Creation Date 16 October 20043. Document C - Creation Date 16 October 2004but we know for a fact that1. Document A was created on 16 October 2004 14:252. Document B was created on 16 October 2004 14:453. Document C was created on 16 October 2004 12:40You can clearly see that time stamp is not used in primary search results display order criteria. Well as far as descending Creation Date order by is concerned considering the time aspect and not just DATE...Therefore I want to find out what is used as a Secondary display order when results are presented to a User?I would much appreciate if anyone can comment on this.Many thanks