
Dynamics CRM: March 2019
This is part 2 of my earlier post which helps identify tips and gotchas of CRM 2013 update. What is the impact? What do I need to do to ensure my organization shall continue to work in CRM 2013? What are the tricks and tips for upgrading to CRM 2013? How can I estimate the effort to upgrade? THEREFORE I will try to provide a checklist of the very best 10 most common areas of the update that you should keep in consideration. Because of the limited mobile efficiency of CRM 2011 (mobile express) it is easy to assume that there surely is no effort necessary to migrate your mobile express application to CRM 2013 except perhaps some tests effort.
If you have used the new forms of CRM 2013 it’s likely you have observed the new Auto-save feature. By default, users aren’t required to click “Save” when upgrading a record. Every 30 mere seconds after editing a field, the form will automatically submit a save demand in the background. Clicking some commands such as “new”, “qualify” or closing the proper execution will also issue a save request to the server (note: it does not connect with the create form).
The impact of auto-save is that every auto-save is an update procedure in the database so plugins and workflows will result in and auditing will occur. You need to consider that if an individual requires 2 minutes to upgrade a form, then at least 4 improvements will occur on the …