[Feature] Navigating to previous and next Record

khushal_t · November 2, 2017, 11:26am

Hi,
I am working on new small feature navigating to previous or next record(specific doctype) for which I have placed two arrow head near a group of a button. Any suggestion from you guys is welcome, please let me know your reviews.
com-video-to-gif

Regards,
Khushal!

Onkar_Mirajkar · November 2, 2017, 12:31pm

Good one…!!!

olamide_shodunke · November 2, 2017, 12:33pm

I could kiss you!

This is sooo needed!!!

Olamide

Pawan · November 2, 2017, 1:37pm

Good thought…why not just have some standard keyboard shortcut for previous and next document

James_Robertson · November 2, 2017, 2:20pm

Is the pagination tied to the list and filters in any way? How does it “know” what is next? Ideally this would be derived from the list in some manner. So if I apply a filter and then open a record, the next/previous buttons would be linked to the filtered list.

olamide_shodunke · November 2, 2017, 5:27pm

Yes, that is the way it should work

khushal_t · November 3, 2017, 4:56am

@James_Robertson
Thanks for your views, workiing on that

gupteshwar · November 3, 2017, 5:31am

That’s good suggestion.
We can use keyboard Left and Right arrows as shortcut for navigation.

khushal_t · November 14, 2017, 12:09pm

Please refer [Feature] navigate to next or previous Doc(under development) by khushalti · Pull Request #4490 · frappe/frappe · GitHub
Please help to contribute this feature.

Thanks

aakvatech · December 19, 2018, 2:13pm

Did this progress further. It’s a great idea. Keyboard shortcuts would be great too.

How can i test this out? Is it just toolbar.js that is changed?

tmatteson · December 19, 2018, 11:30pm

form.js and toolbar.js in this PR, but I don’t think that all the logic is there; there should be a callback to the server to determine the next or previous document and the sort criteria. There are front end tests written, but it would be highly appropriate/ nearly required to write a new Cypress test for this.

dam_89 · June 16, 2019, 3:48am

@khushal_t, are you trying to improve this feature? Why GitHub PR is closed? I want to contribute in this feature

vrms · June 16, 2019, 11:35am

as mentioned on the PR

please send a complete PR and reopen / send a new PR
You can take help of someone in the community if you don’t know how to proceed.

I admit this comment is a bit foggy but I am guessing the code was not quite up the contribution guidelines yet.

karthikeyan5 · June 17, 2019, 4:57am

@vrms, the comment becomes less foggy if you also read the PR Description and Title, and look at the code changes. the PR was an incomplete one, there was only a UI added with no functionality.

I think @khushal_t was requesting some Help from the community regarding the PR. Hopefully, @dam_89 can collaborate and complete this feature. It would be a neat feature to have in ERPNext.

xickomesquita · June 17, 2019, 5:19am

If you can do it in the tab list, inside the docs…

khushal_t · June 17, 2019, 5:33am

yes it was just idea to put forth i did not make it complete PR, i shall be working on that

dam_89 · June 17, 2019, 3:41pm

ok thanks… I will try to do it… it seems very difficult because the feature is related with the list, filters, order, etc…

prssannad · July 9, 2019, 9:08am

This feature is now merged
https://github.com/frappe/frappe/pull/7777

dam_89 · July 9, 2019, 7:43pm

Hi, thanks for the feature…

I was testing it. When a list is ordered by “creation on” or “last modified on” it has a problem:

prssannad · July 11, 2019, 6:32am

Hi @dam_89!

I can’t reproduce this error, it works fine for me if the list is sorted by last modified on and created on. Is there any more information you can give me regarding this error? What is the error on the browser console?