TeamDesk Knowledge Base & Support

   Home      FAQ      Forum      Idea Exchange      Ask a Question      My Stuff      Help   
Add a "Next" Button to the detail view
Wouldn't it make sense to add a 5th button next to the existin ones, allowing you to jump forward to the next entry (...without having to go "back" and select the next entry?


Date Created
7/21/2007 1:07:06 PM
Date Updated
3/10/2011 3:33:37 PM
New Idea
Promoted By
Desmond Beatty (Conc)Megan PillsburyTon Jense
Michael Ver DuinLiquid RapidRick Cogley
Philipp Matuschka (MMB)Nelson LiDonJ-Adi Marketing Expert
Matthew PorterAndrew WintersAnatoliy Zachynskiy
Damar ChristopherMatan BarneaAndrew Newton
Anthony CarterAdministrator
Anatoliy Zachynskiy 4/21/2008 11:52:16 AM
Fro example, view has 3000 records.
How to look record #300?
NOW I have to load 3000 records (only button "Click here to show all" is available).
Kirill Bondar  Staff  4/22/2008 3:54:13 AM
I hardly imagine the situation when the user needs to look at the particular record number. When users searches for the data they usually have some criteria in mind. I guess that would be enough to include the view or the set of views with <ask the user> options to allow users to find the record(s) by typing criteria.
Matthew Porter 4/26/2009 9:44:58 PM
Record paging would be a better solution. I agree that an "all or nothing" approach is inadequate. What we need is the ability to show "n" records at a time (configured with "Ask the user", and the default set in the View itself), with page navigation. This might also include the ability to Jump to record number (n) via a text box. So: <Prev 1 2 3 4 ... 10 Next > or Jump To [ ] could appear at the bottom of the list, with the "Show []" records at a time at the top as a drop down with 10, 20, 50, 100, 1000 as options (for example).

And Kirill, just because you can't imagine such a situation, doesn't mean that nobody needs it. :) I have been a database developer for over 15 years, and there are many applications where this kind of feature is important.
Kirill Bondar  Staff  4/27/2009 10:37:15 AM

The only advantage of pagination I see is decreased page loading time. The same we achieve with restriction to first 200 records.

But I still can not imaging why one would need 3000 records in result, even with pagination?.. Display the list of all customers in 60 pages, 50 records per page, alphabetically sorted, and having in mind that names are almost equally distributed look for "Matthew" on a page 30? Why won't let users search for name then?

If we would speak of pre-built systems, well, pagination can be used as a workaround to quickly find the result in a list of all records. But since TeamDesk is customizable, the administrator can always change the system to reflect users' experience.
Rick Cogley 3/1/2011 6:22:39 PM
Every time I do back then pick the next entry, I think this same thing.
Liquid Rapid 3/10/2011 3:28:51 PM
I can see where this would be useful, but it might not be straightforward logically. When you have a record open and click Next - which view will the system use to find the "next" record?

Suppose you have a view sorted differently than the default when you're looking at it. You might expect the Next button to take you to the next record according to the sorting you've specified. But I think that's done on the client side - the server doesn't know about your special sorting.

Maybe a combined view of a list of records at the top, plus a form immediately below on the same page would allow easy navigation across a list of records.
Kirill Bondar  Staff  3/10/2011 3:33:37 PM
Merged with:
202 - "Next" and "Previuos" (records) BUTTONs in views with many records
Back to Search Results