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 server aspect actually. So why is this very important to upgrade?

Well, you could argue that this is nothing at all to get worried about since this behavior corresponds to how some users are actually conserving multiple times in fear of losing their improvements, but it is currently done automatically. I tend to trust that however in reality some developers do not consider those kind of users when making plugins or workflows. You need to make sure that your plugins and workflows won’t break because of auto-save; one typical recommendation is to limit the “triggering attributes” of the update plugin to only those fields that when changed should certainly trigger the plugin. This is more of a review exercise and you will possibly not need to make any visible changes.

  1. Use all the money on business expenses
  2. 3 Demerits of Line and Staff Organisation
  3. Earn 2 miles per dollar spent on tickets purchased from United
  4. Evaluate Quality Of The Leads
  5. May be unable to make decisions that would suit the neighborhood area

On your client side each time auto-save occurs, the fields that changed in the server will be refreshed in the form, however the OnLoad event will not be brought about because the form will never be refreshed. You will need to ensure that your form scripts will not break due to this new behavior and if required you might need to use the new GetSaveMode() method on your OnSave scripts to recognize the way the save originated. You should use this same solution to prevent auto-save from happening by intercepting the OnSave and discarding any save from auto-save. In conditions of sitemap, it’s likely you have observed how different it is to navigate different parts of the software.

For the most part according to feedback from the community, it is becoming harder to be efficient when navigating between different modules of the application. Consider the scenario of a ongoing service representative talking to a client and then producing a lead from the conversation. While you might make sure that your customizations shall continue to work after the upgrade, it might be great to consider whether you can “un-customize” the system and migrate some of those customization to use built-in features that are configurable.

This will of course boost the amount of effort for the migration but will simplify your deployment and make it more maintainable later on, it will always be an “easy” sell for customers because the advantage is very evident. As an example, you might have multiple javascripts that perform conditional actions on forms and perhaps most of these can be re-written using Business Rules.