Script errors when adding documents via the SharePoint integration CRM UR12+

As you may know, Dynamics CRM 2011 has the ability to embed a SharePoint document library within certain record types.  After applying update rollup 12 most of us will likely want to take advantage of the ability to turn off HTC’s and tell Internet Explorer to use a standards based browser mode (look for an article coming soon on turning off HTC’s and IE’s compatibility mode).  However, once you do this you may notice JavaScript errors when interacting with the SharePoint document library integration.  The error I’ve seen so far is: ‘action’ is undefined and will have a URL of: http://servername/org/crmgrid/crmgridpage.aspx

If you’re going to update or already have updated to UR12 or higher, don’t forget to update your SharePoint list components to avoid this issue – for reference here’s how to install this update:

Important note before starting:

  • You must be a SharePoint site collection administrator to be able to install the Microsoft Dynamics CRM List component on Microsoft SharePoint Server.
  • If you’re installing to SharePoint 2013 or SharePoint Online make sure you’re on the latest SharePoint update before adding the new list components.
  • (For SharePoint On-Premises only) The Microsoft Dynamics CRM List component is a site collection-level solution. If you want to enable the Microsoft Dynamics CRM List component at the farm level, you must write a script that does the following:
    • Retrieves all SharePoint site collections from SharePoint server.
    • Installs and activates the List component on each of these site collections.

To install the Microsoft Dynamics CRM List component:

  1. Download the latest SharePoint list component update from the download center: or search for it here
  2. Navigate to the folder where you downloaded CRM2011-SharePointList-ENU-amd64.exe or CRM2011-SharePointList2013-ENU-amd64.exe, and double-click it.
  3. In the Open File - Security Warning dialog box, click Run.
  4. To accept the license agreement, click Yes.
  5. Select a folder to store the extracted files, and click OK.
    • If you downloaded CRM2011-SharePointList-ENU-amd64.exe, the following files are extracted:
      • AllowHtcExtn.ps1
      • crmlistcomponent.wsp
    • If you downloaded CRM2011-SharePointList2013-ENU-amd64.exe, the following files are exstracted:
      • crmlistcomponent.wsp
  6. Open your web browser
  7. In the address bar, type the URL of the site collection on which you want to install the Microsoft Dynamics CRM List component, and press Enter
  8. Navigate to SharePoint’s Solutions Gallery
    • If you are using SharePoint 2010: click Site Actions, and then click Site Settings, under Galleries, click Solutions
    • If you are using SharePoint 2013:  click the Settings icon in the top-right corner, then click Site Settings, under Web Designer Galleries, click Solutions
  9. On the Solutions tab, in the New group, click Upload Solution.
  10. Click Browse, locate the crmlistcomponent.wsp file, and then click OK.
  11. On the Solutions tab, in the Commands group, click Activate.

Special thanks to Chris Donlan, another Dynamics CRM/SharePoint PFE, who helped document this when customers started to update and find this issue. Feel free to ping us via the “Email Blog Author” link to the right or comment and we’ll get back to you as soon as we can.  If you’re a Premier customer talk to your TAM about working with a Dynamics CRM PFE (remote or onsite), and if you already have a Dedicated Dynamics PFE make sure to reach out.  If you don’t have Premier and are interested in working with us – please reach out and let us know.  Thanks for reading!

Sean McNellis
Premier Field Engineer

Comments (0)

Skip to main content