Per this thread, I am requesting that you provide us a setting to turn off this feature. It would be ideal if we could turn this off at either at the individual user level or at the admin level. This autosave feature is extremely disruptive to our workflow.
Please add the ability to opt-out of the auto-save feature on record view.
How was a change to such a basic function implemented without foreseeing the implications it may have on erroneous workflow enrollments? not only in case of users mistakenly selecting the wrong dropdown options, but for cases where multiple properties need to be changed at once?
I understand some users requested this, but from messages I've seen today many users clearly don't want this. Auto-saving values in a database where some fields are dependant on others, makes it easier for a typo or erroneous click to become a critical problem. Nobody on our team finds this feature beneficial, its the opposite.
My instance now has auto-save of properties on record pages, including Contacts, Companies, and Custom Objects.
I have a non-tech savvy team and in both the app and on the desktop, I foresee having issues with my users updating properties by mistake and either not realizing, or not understanding how to undo their change.
As an HS admin and chronically online person, I understand that there is a small and quick popup that allows me the option to undo my action. I also understand that I can view property history and revert the change manually, if needed. My team, however, consists of people who regularly call me to ask their passwords or where their contact record "went," so they aren't going to be picking through property history when they mess up. I have also already encountered situations where the popups "closed too quickly," so I don't imagine things will be different for them with this.
I appreciate the the autosave feature was highly requested and the need for it, but I would like to have an option of whether of not to use this feature if it is going to continue to function as it does now. My team will not benefit from this and, as such, would like to opt-out of usage.
Otherwise, I can see the feature being helpful if it functioned similarly to forms or emails and had an autosave with a final "publish"-like confirmation button. Until that update comes, this feature is more harmful than helpful for my particular team and I would appreciate the ability to not use it for now.
We would like the option to turn this off as well. Auto-save forces confusing feedback when you have dependent properties on the contact page (ones that require others to be filled). For example, you make a change to the dependent property (change not saved), change one of the required properties (change saved), then change the final required property (2 changes save).
In this scenario without autoave, the user gets nice feedback when clicking save, but with autosave the feedback is in pieces and a bit confusing. You end up wondering if you've done it correctly and refresh the page to see if it's saved properly.
Not ideal when you accidentally select the wrong contact/company owner and it auto-saves and sends that person a notification before you get a chance to fix it.
When you have emails or workflows triggered based on properties, and they trigger early while you are still editing, it is highly disruptive. When checking the property audit trail, you also see sometimes dozens of changes from while someone was working on something completely muddying the waters.
Autosave really needs to be an option not a requirement. Or it needs to be tweaked to not be so aggressive in its triggering.
I've spent 20 hours over the last 2 days fixing errors that this has caused, and I only see it growing as more users get in here doing stuff. Everything is getting messed up, and I'm losing records because this saves SO fast that the records get removed from my filtered view. We don't need auto-save, this is not user friendly at ALL. Come on now.
100% agreed! I can appreciate the value of the feature and don't want it removed, but there must be more control for specific users or levels where we can turn this off. Some users love it, but others find it quite disruptive, depending on the nature of their role.
Another +1 to disable this feature. We require certain properties to be text heavy and this feature is autosaving them before the rep has finished typing which triggers automations to fire early and incorrectly.
Incredibly frustrating to see another half-baked feature released which causes us a big headache.
This was such an unnecessary feature that really messes up our workflows. 1000/10 hate it and there needs to be a feature to turn it off. Whoever requested this update is an **bleep**.
Giving us the option to at least choose whether or not we want this feature would be a great start. This is a significant issue for me personally, and to my knowledge, for my team as well.
