Lessons Learned from Working with CRM 2013

I’m currently involved in a number of CRM Online upgrade projects (from CRM 2011 to CRM 2013), and discovering the obvious (or not) about CRM 2013 and the new CRM App for tablets.

If you haven’t already, I highly recommend downloading and reading the implementation guide published by Microsoft for CRM Online and CRM 2013.

“This guide contains comprehensive information about how to plan, install, configure, customize, and maintain Microsoft Dynamics CRM 2013 and Microsoft Dynamics CRM Online.”

http://www.microsoft.com/en-au/download/details.aspx?id=40322

CRM 2013

  1. Auto-save can only be turned off at the system level.
  2. You can use the vertical scroll of your mouse to scroll the CRM menu items horizontally.
  3. Server-side sync only works between CRM Online and Exchange Online, and CRM On-premises and Exchange On-premises. However, currently CRM Online and Exchange Online isn’t yet working and is at the top of Microsoft’s priorities.
  4. So, if you’re currently using CRM Online, stick with the E-mail Router for now. Don’t forget to change the system settings to use CRM E-mail Router and not Server-side Sync
  5. You must upgrade your CRM E-mail Router component to the latest version to work with CRM2013, the older version doesn’t work.
  6. You can control access to entities for tablets and phones separately.
  7. You should merge the old Information forms into the entity-specific forms – e.g. Account, Contact, Lead and Opportunity forms, and deactivate the Information forms.
  8. I still haven’t figured out how to force the welcome/splash screen to permanently disappear and not appear every time I logon to CRM Online.
  9. Bookmark the Default Solution page so you can open it quickly without having to navigate to Settings > Customizations.
  10. Just as with the previous version, for CRM Online the ExecuteMultiple is limited to 1000, and concurrent run of 2.
  11. Just as with the previous version, for CRM Online there is a limit of 50,000 records for aggregation functions, and 5,000 record limit to be returned.
  12. Microsoft is currently experiencing high volume of cases right now, possibly due to everyone doing upgrade before the due date and asking support questions.

For a list of known issues for CRM 2013 as at September 2013, please refer to http://www.microsoft.com/en-us/dynamics/crm-customer-center/readme.htm

CRM App for tablets

Below findings are primarily based on the CRM app for iPad version 1.0.4.5, released October 8th 2013.

  1. Entity form supports only showing the first 75 fields (including those in the header) or 5 tabs.
  2. Entity form supports only showing the first 6 relationships.
  3. To connect to a different instance, you have to remove (uninstall) and re-download the app.
  4. When you’re prompted to sign in, and you tap on the sign-in email address (e.g. someone@example.com), the cursor will focus on the email address field for one second, and then move focus to the password field.
  5. You can tick the box “Keep me signed in” so you don’t have to login every time. However, to “forget me”, you have to remove, and re-download the app.
  6. To force the app to download new customizations, you have to force the application to close (e.g. on iPad – double click the home button and delete/swipe up the app), and start again twice – the first restart doesn’t seem to download all customizations.
  7. Access Teams and record sharing aren’t yet functional on tablets. Access Team grid (Associated Record Team Members) will show all users in the instance and no ability to add/remove users.
  8. The context menu located at the bottom of the screen, conflicts with iPad’s Control Centre.
  9. JavaScript works on tablets.
  10. You cannot create recurring appointments with the app, but you can do so in the web version (e.g. on Safari). Use the context menu and then choose “Open in browser”.
  11. When you’re in the middle of editing a record, when you go back or navigate away from the form, your changes will be saved. There is no way to cancel/discard the changes and business rules (PBLs) don’t fire.
  12. Plugin errors are displayed as just “Error” and not the actual, more meaningful message.
  13. Don’t forget to assign “Use CRM for tablets” to users Security Roles, also “System Application Metadata” and “User Application Metadata”.
  14. You can enable tracing to help troubleshoot issues encountered by the app. See here for more details: http://www.microsoft.com/en-us/dynamics/crm-customer-center/enable-tracing-in-crm-for-tablets.aspx.

Up-to-date list of known issues for CRM for tablets and phones maintained by Microsoft can be found here: http://www.microsoft.com/en-us/dynamics/crm-customer-center/known-issues-for-crm-for-tablets-and-phones.aspx

The learning continues …

Advertisements

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