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/

Advertisements

6 Responses

  1. Regarding limitation nr. 1, I haven’t actually run into this one myself. When you create a new form after Polaris, it will by default be of the “flow” type, including the new components. While you don’t have access to the form selector unless you navigate to the Classic mode first, multiple “flow” forms can still exist and be targeted to users based on security roles.

    Apart from that, all the limitations you listed are indeed something that any system customizer should be aware of before considering migrating to the new Polaris experience. There’s a lot to be loved about the refreshed UI, but until Orion arrives we’ll be quite limited with the actual customer use cases that fit this new UI unfortunately.

  2. Hi. Regarding Limitation 7:
    We are using CRM Online. One of our team members swiched the form to classic mode. We cannot find an option on form through which it can be swiched back to new form. Could you please help?
    Thanks in advance.

    • You have to switch the form selection back to the “Account” or “Contact” or “Opportunity” or “Lead” or “Case” form and then save and close the record and then re-open. You should now see the new polaris forms opening again. There is no button to switch back to the updated forms once you have opened the classic forms.

  3. Possibly the most annoying thing about this is that Microsoft think that switching to ‘classic view’ is a suitable response to anyone that wants to use basic features such as Dialogs, Workflows or adding a new related record. Seems like Windows 8 all over again. I’d very interested to know if these features could be added back into the new forms using the ‘Insert Navigation Link’ feature?

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: