The Microsoft Dynamics CRM Team Blog
News and views from the Microsoft Dynamics CRM Team
Applies to: CRM 2013 and CRM Online Fall ‘13
Auto save enables automatic save of records at fixed short interval for update without the need for you to explicitly click on “Save” button every time. Now you don’t need to worry about saving record when you are working on a record for a long time. In this blog we are going to discuss more about this.
Auto save of records not only saves an extra click but also reduces chances of data loss in case of any connectivity issues because now all changes in form will be automatically saved in every 30 seconds. If no changes are made on form than automatic save will not occur.
The field that someone is currently editing isn’t included in an auto-save. If someone else has updated the same record while you’re editing it, those changes will be retrieved and displayed in the form when auto-save occurs.
During the save, if there are any validation failures, such as invalid data, or missing required fields, etc. that prevent the save, then an error message will show at footer panel below and the auto save will not proceed.
In CRM by default this feature is turned on for all new and updated organizations. Please note that this is applicable only when updating records. If you are creating a new record then you must explicitly save the record. It will not be auto saved. Auto save capability is not applicable to Quick Create forms or Mobile forms. Also, auto save only applies to the Main form. It is also important to note that this feature is only enabled for entities with the updated user experience forms.
How to turn auto save on or off
There may be situations where you want to disable this capability. Because auto save call goes through normal save pipeline. This means all events associated with the form on-save event will be triggered for auto save as well. Server-side plugins and workflows associated with save actions will also be executed.
You may have a scenario where you don’t want save to be triggered automatically at a fixed regular interval. For example, if you have plugins o workflows triggered on the save of a form that have complex business logic associated with them, you might not want them to be called with each auto save. In this case you might want to turn off this setting. In CRM there is an option to turn off this setting which is available in “System settings”.
This is a new field in the organization entity called “IsAutoSaveEnabled” and can be set using the SDK Update method as well. See the CRM 2013 SDK for information on using the Update method.
Please note that this feature can only be controlled at organization level. The feature will be turned on or off for all updated entities. In our next blog we will discuss on how to control on-save for specific entities or forms.
Please note that this setting only turn-off the auto save on form which happens at every regular interval if changes are made on form. Whether you have auto-save enabled or not, whenever you navigate away from a record or close a separate window displaying a record, the record will be saved.
For more information, search for “auto save” in the Customization Guide (within the Implementation Guide).
Thanks,Niraj YadavMicrosoft Dynamics CRM
This article needs to make it clear that only the regular saves that occur every 30 seconds are disabled by this setting. Press backspace, navigate with browser controls, navigate with the NAV Bar, press certain buttons on the Command Bar, "Pop-out" the record or close the browser tab/window even and your changes are saved.
Once a field that has changed has lost focus that's it - there is no cancel or undo (before it's lost focus you can press ESC).
Thanks for the feedback Simon.
Does this differentiation still apply? I've tried turning off auto-save in my CRM 2013 sp1 (on-permises) environment, and found that browsing away from a form *does not* trigger an autosave. The only way to save is to explicitly click the save button. I was looking for a way to disable just the 30 second auto save, as this makes any workflows that trigger on save execute multiple times.
This is in response to TOM.
I am in the same position in terms of having workflows that are affected by the auto save feature. I'd like to turn it off, but then navigating away frm the page negates changes which is frustrating. Is there a resolution to this at all?