Limitations of the new Updated Forms (process flow) – Top 10!

So Polaris is live, and the new process forms now known technically as the updated forms look good, but what are the limitations of their use, what does this mean for my CRM instance? I have listed below some of the limitations of these forms so that you are all aware on when to use and when not to use!

  1. Only one Updated form can exist for any of the COLAC entities (Contact, Opportunity, Lead, Account and Case entities), multiple forms still exist for the Classic forms [Steven Foster Update] You can create multiple forms in the new mode, and visibility of these can be controlled by security roles, but only one form can be the default and there is no easy way to switch between the different updated form types other than switching to classic, changing to the different form and then closing the record and re-opening the record.
  2. No Javascript event handlers on On load, On change or On save, if included the form will return to Classic
  3. Only Web Resources can be added to the forms, which can interact with the fields on the form but they load asynchronously  which means there will be a delay
  4. Left hand navigation – you can view related records but cannot add new ones, so if you want to create an opportunity against an account then you will need to either add the opportunity as a sub grid or switch to classic forms
  5. You can only add Phone calls and tasks to the record, so as above if you want to create an appointment then you will need to add a subgrid or switch to classic
  6. The command bar cannot be changed in anyway, unlike the ribbon
  7. If you switch to Classic forms then these will become the default, and to enable the Updated form you will first need to open the record again and switch the form to the updated form, close and then reopen
  8. Cannot change the bing maps integration if you wanted to show a different address or different address fields
  9. Only one process form can exist for Opportunity, Case and Lead, so if you have different sales processes then you will either need to simplify to one or switch to classic
  10. You cannot change any of the locked components, which is a shame as the Case presents some core fields from the Account or Contact associated to the Case, but you can not change this if for example you wanted to add the Customer Pin to the form for validation purposes

The list could go on but that is a good start, so before you use the new forms, think about the impact! To turn off the new Updated Forms see my blog post https://nakedcrm.wordpress.com/2013/01/17/how-do-i-enable-for-some-users-by-default-the-classic-ui-forms-rather-than-the-new-process-ui-forms/

Updated office 365 Dynamics CRM Experience

With the latest rollup applied to Dynamics CRM Online, a whole of new capability has been added to the office 365 management of CRM instances. These improvements are some of the highlights of the Update Rollup 12 release for Online customers. Here is a list of some of those improvements and what they mean to you:

  • Multiple Instances under one Office 365 account – Buy one CRM licence access multiple instances, controled by group security (previously you would of had to have multiple Office 365 accounts), now you can have UAT and Prod in one instance with one username and password.
  • Single sign on across multiple instances – One user can log into multiple instances with the same username and password.
  • Share storage – You can now share the storage across the multiple instances i.e. majority goes to Prod, a little goes to UAT and DEV, any purchased storage can be shared as well
  • Group Security – Easy control of who can access which instance of CRM

So lots of new features and this is coupled with the potential power of Office 365 enabling online exhange, SharePoint and team collaboration.