CMSB v3.71 Released (Jun 18) -Help Tooltips & Upload Features

I'll second that!

~ Deborah

As in "auto-save" when pressing next? Good question. In Shopify, in a product's details, when you page "next" like this (or leave back to product list), it prompts you that you have unsaved changes and you have to press a save button before continuing with the next button again. I haven't made any mistakes nor have I been annoyed.

If pressing "next" saved and also went to the next record with that one click, it sounds convenient (I believe exiting without saving already causes a JS pop-up).

Can anyone think of any cons to this "save and next" button? I would think if you were pressing next, you are wanting to save every time. Otherwise, you cancel to revert?

Is that what you meant Dave? Sorry if I misunderstood. I'm fine with either way but more convenience is welcomed. I'm only experienced with Shopify which does work fine.

Thoughts anyone?

Initially I'm thinking when you click next record/prev record it should save the current one and then go to and open the chosen for editing.  As I mull it through my head, though, why not also incorporate an option that pops up when there is no more prev or next records (you've gone to one end or the other of the pile of records) that reads "There are no more (prev or next) records, do you wish to create a new one here?" 

Hi Rez, 

Let's go back to the original use-case, what kinds fo things are you updating?  Is it that you need to update a single value across many records?  Or different values for each record?  

IF there are cons to this...maybe as a feature programmed into the top and bottom menus in the editor, or as an "advanced" option, or a checkbox in the General Settings section - to toggle the option?

I apologize for the intrusion and digression from the original post.

Hi Codee, 

It's no problem at all and your comments are always welcome.  

We often explore many different ideas and then narrow them back down to the most essential features for the next step.  

That way we can develop/release something in a reasonable amount of time, while still being aware of where me might want to take in future.

Hi Dave,

In my cases, it's a different value for each record.

Example 1:
A restaurant with 100 items updates their pricing with increases. Usually, at the same time, they will throw in some description changes of ingredients and such, or I'll be swapping some photos as well. So it's not just always 1 field—price, description, and photo.

Example 2:
A taphouse decides they want to list ABV percentages for all of their beers, and there are 100 in the database. Different values for each record but all the same ABV field.

Example 3:
I'm not going to lie—sometimes it may only be 7 weekly specials, but it's still efficient if possible! ;)

Thank you for considering this and thanks to the other interested users.