@lubos I know this has previously been requested in several posts (linked below) and most recently as just a couple of months ago without an answer.
Having been using this software now (for only) six months, about my greatest challenge is navigation. Because I have made mistakes, or need to change/review past invoices, receipts, or whatever element of the view, I find that I am constantly navigating down to a result and then clicking in, (review/editing as appropriate), clicking back, scrolling back to where I was (I REALLY wish it would maintain the position in the list in some way, or even highlighting where we came from), making sure I’m on the right item and then selecting the next or previous one manually and repeating as necessary.
It is very tedious, cumbersome and time consuming and I would personally be indebted to you eternally if it could be incorporated.
From recent to oldest:
Although the above request pertains to invoices, it could be of benefit in more “end screens” where a single item is shown, whether it be a purchase or sales invoice, a payslip, delivery docket, emplyee, inventory item, or search result for any and all and more than the above.
I note your reply says you won’t be incorporating previous/next buttons (I hope that decision isn’t final) but will be working on “breadcrumbs” instead. I don’t see what benefit breadcrumbs could provide that the back button already doesn’t.
In two posts of 2014
It seemed to fall back on “ambiguity” and I would agree with @Brucanna’s proposal of “up and down the ladder”.
I ass.u.me that you are using database and select/queries to arrive at a recordset to display a list of results within which the user clicks into a transaction/record. Whether you are viewing a complete list like “Sales invoices”, or a search result of “Cash Accounts” where Field contains “Direct Debit” (this could easily have been: a complete list of “Cash Account” transactions, or a search of “Sales Invoices” where Field contains “Jones”, or any other results screen within manager), the natural progression of bringing up such a list would be to provide a “◄ / ►” to go to the previous or next within the same record set. It would be unreasonable to expect that if in a view of sales invoices a user explicitly would want to go to the next within only a particular customer. If that would be the case, the user would/could/should drill down through customers THEN sales invoices by customers (UNLESS the search result within sales invoices resulted in a list from said customer only, but you are still progressing through the list by sales invoices meeting a search criteria).
Unless someone else could comment on what other dataset should be traversed with a specific use/case example, the previous/next record in the current recordset would be my obvious (and hopefully soon implemented) choice.