sbmantri
19th November 2013, 15:38
I am developing a display session to display fields in descending order of index.
for which i am using query.extend.order("index desc") for it
It working as usual except Previous Records(prev.set) command.
on selecting prev.set it goes to second last page instead of previous page.
Please help asap, its urgent.
Thanks :)
bhushanchanda
19th November 2013, 17:52
Hi,
Have you programmed anything in prev.set?
Also, what kind of index is it? string or integer?
sbmantri
19th November 2013, 18:27
Hi,
Have you programmed anything in prev.set?
Also, what kind of index is it? string or integer?
I haven't programed anything in prev.set,
index is on date field,integer,integer
bhushanchanda
19th November 2013, 19:09
Hi,
I am not sure about how it acts on your version. But, people have faced issue while using order in query extensions.
A similar Thread! (http://www.baanboard.com/baanboard/showthread.php?t=12905)
Try if it works for a single field. e.g. date
sbmantri
19th November 2013, 19:17
Hi,
I am not sure about how it acts on your version. But, people have faced issue while using order in query extensions.
A similar Thread! (http://www.baanboard.com/baanboard/showthread.php?t=12905)
Try if it works for a single field. e.g. date
Thanks for your reply Bhushan,
I am using Baan V and query.extension.order("") working with it.
Session is showing me data sorted in descending order on index I wanted to.
next.set, last.set and first.set also works fine but in prev.set it's displaying 2nd last page instead of previous page of current page.
bhushanchanda
19th November 2013, 19:25
Hi,
Check what it display under query tab, when you press Ctrl+Shift+* on your display session. Also, can you post your code, so that people may know what table is it and they can try on their environment.
bhushanchanda
19th November 2013, 19:43
Hi,
I just tried on one of my table having date as one of the field in the index and it showed inaccurate behavior for next.set and prev.set.
Then, I tried to add the index fields one by one separately and it worked perfectly. You can try it as well.
Here's my code snippet:-
before.program:
query.extend.select("whinr110.*")
query.extend.from("whinr110")
query.extend.order("whinr110.item desc, whinr110.cwar desc,whinr110.trdt desc,whinr110.seqn desc")
sbmantri
19th November 2013, 22:27
Hi,
I just tried on one of my table having date as one of the field in the index and it showed inaccurate behavior for next.set and prev.set.
Then, I tried to add the index fields one by one separately and it worked perfectly. You can try it as well.
Here's my code snippet:-
before.program:
query.extend.select("whinr110.*")
query.extend.from("whinr110")
query.extend.order("whinr110.item desc, whinr110.cwar desc,whinr110.trdt desc,whinr110.seqn desc")
Its working perfectly after adding index fields one by one.
Thank you Bhushan :)