Ryan Van Der Vorste 12/7/2007 11:54:21 AM
This is a simple concept. In order to view a record once in edit mode you either have had to 1-just create it or 2. first click on view, then edit, then save. If you don't do one of these two things then once you hit "save" the application goes back to the last screen you where looking at which may or may not contain that particular record.
Often times I want to VIEW a record once I edit it to see total calcuations, etc. before it goes back into the database. If I want to view it, i have to get out of the view I'm in and search it all over again.
My solution would be to have one button saying "Save & View" and another that says "Save" or "Save & Back" so the user can decide what he/she would like to do.
firstname.lastname@example.org 10/15/2008 11:24:44 AM
This would be huge! On a daily basis I'm editing and then going back to view to see that changes (formulas adding up, total price, etc.). If I don't hit "view" first before "edit" I can't see what changes took place and have to go back in and "view". having 2 options to either "save and view" or "save and back" would be an excellent implementation.
Annette Chamberlain 3/19/2009 1:57:55 PM
A 'save & new' button would make data entry much quicker for multiple entry items, such as new contacts or tasks. Currently it takes three steps to move from one new record to the next (Save, Back, New) as opposed to just one if there were a 'save & new' button. Any chance this is in the works? Thanks.
basenine 7/16/2009 6:40:35 PM
Yep - I agree... Is this an easy idea to implement? It would save us a heap of time and as we're in manufacturing, every second counts.
Michael Rennert 8/11/2009 12:36:48 AM
It's also important to have 'Save & Next' and plain 'Next' (or 'Skip') buttons so that you can move through existing records in a Table/View, without having to go back to the Table each time and click on each record individually to edit.
The 'Next' (or 'Skip') button moves to the next record in the Table/View without saving (since some records might not need editing).
Philipp Matuschka 2/8/2010 1:08:06 PM
I would encourage also
- Save & Similar
Take it even further. When viewing any item which came from list, NEXT and PREVIOUS buttons should be provided. Currently I have to go back to the list. Find where I was in the list and selct the next item.
Slava Shinderov 4/15/2010 8:12:45 AM
247 - 'Save & New' button
Rick Cogley 7/1/2010 9:23:12 AM
Yes, absolutely. Save and View Next, Save and Back, Save and New, Save and Similar buttons would be very useful. The fewer clicks the better.
By the same token, a column edit function would be nice too. You could click the field-header to open a menu, within which is Sort (the current function when you click the header) and Edit. When you click Edit, the interface lets you edit the column in line, so you can quickly update many similar entries. You can click the field-header again to choose Stop Editing.
THese kinds of small things are huge timesavers, and would make TeamDesk / dbFLEX all the more powerful.
basenine 6/21/2012 7:37:50 AM
Any movement on this idea?
It would Save so much time and make the Workflow so much more obvious.
basenine 9/25/2012 7:58:40 PM
Is this planned for release? It has many people excited about this functionality and is an obvious "makes sense" feature that will enhance, speed up and facilitate record entry.
Kind regards - Brett
Philipp Matuschka 11/11/2015 10:55:08 AM
In addition to the Save button on edit forms, provide a Save & New buttons. For example I am entering a whole sequence of payments. After each one I hit Save and the I have to hit New. Ergonomically it would be a big time saving if I could hit a Save & New button
Slava Shinderov 11/11/2015 11:05:44 AM
922 - Save & New
basenine 11/17/2015 6:43:51 PM
A drop list of "SAVE" options...like the new document generation and button category groupings.
basenine 11/17/2015 6:44:27 PM
Philipp Matuschka 11/18/2015 1:46:37 AM
I disagree with the drop list in this case. I am trying to reduce mouse clicks
Jeff Aibel 3/8/2017 7:54:28 AM
To facilitate faster data entry in high volume record environments, I suggest a "Save & New" button be available on all forms that would save the current record and immediately present a new blank form.
Today after saving, the form goes from data input to record review and its extra clicks to get back to the data entry screen for the form that is being used.
Philipp Matuschka 3/8/2017 4:21:16 PM
I'm pretty sure there is a similar idea in the system already. Definitely needed.
Jeff Aibel 6/27/2018 5:07:57 AM
A must have for high volume manual record data entry.
SYED DASTAGIR 5/12/2019 3:22:40 AM
A must-have feature which will definitely save end user's time when there are more transactions to be entered
Nick Ashcroft 5/15/2019 11:07:44 AM
this can be done already (but not optional) by adding a "Navigate" action to a "new record" attached to a workflow trigger when a record is created.
every time a record is saved, you will be navigated to a new record form.
Slava Shinderov 9/4/2019 6:18:27 AM
1083 - Save & New Button for Forms
180 - "Save & View" vs. "Save & Back"