Microsoft Dynamics CRM 2011 Readme

January 2012

2012 Microsoft Corporation. All rights reserved.


This document provides important, late-breaking information about Microsoft Dynamics CRM 2011, including Microsoft Dynamics CRM 2011 Update Rollup 5. You will also find information about known issues. Where possible, workarounds are provided for the known issues.

This is version 5.0.7 of this readme, published January 18, 2012.

If you do not find what you are looking for, try the Microsoft Dynamics CRM Forums.

Contents

Setup and Deployment Known Issues

Feature Area Known Issues

Document Management Known Issues

Copyright

Setup and Deployment Known Issues

Prerequisites for Microsoft SharePoint and Windows SharePoint Services

  1. Microsoft SharePoint Server 2010 must be installed before installing the Microsoft Dynamics CRM List component.
  2. The Microsoft Dynamics CRM List component must be installed on the server that is running Microsoft SharePoint Server 2010 by a Microsoft Dynamics CRM administrator who has permissions for site collection administration on the SharePoint server. The administrator must uninstall the old version of the Microsoft Dynamics CRM List component and install the new component because component upgrade is not supported.

    To install the Microsoft Dynamics CRM List component:

    1. Go to the Microsoft Dynamics CRM List Component for SharePoint Download page.
    2. Click Download, and save the file to the desired location.
    3. Open your browser.
    4. In the address bar, type the URL of the site collection on which you want to install the Microsoft Dynamics CRM List component.
    5. Click Site Actions, and then click Site Settings.
    6. Under Galleries, click Solutions.
    7. On the Solutions tab, in the New group, click Upload Solution.
    8. Click Browse, locate the crmlistcomponent.wsp file, and then click OK.
    9. On the Solutions tab, in the Commands group, click Activate.

    If you are using Microsoft SharePoint Server 2010 (On-Premises), you must add .htc extensions to the list of allowed file types:

    1. Copy the AllowHtcExtn.ps1 script file to the server that is running Microsoft SharePoint Server 2010.
    2. In the Windows PowerShell window or in the SharePoint Management Console, run the command: AllowHtcExtn.ps1 <Web Application URL>.

      Example: AllowHtcExtn.ps1 http://servername

      For more information, see the Microsoft Dynamics CRM List Component for Microsoft SharePoint Server 2010 Download page.

Feature Area Known Issues

Importing multiple values to a field of PartyList type is not supported

Data can be imported to a PartyList type of field only if there exists a single party for a record. If a record has multiple parties involved, such data cannot be imported. For example, in your source file, if there is a column that contains data of PartyList type and if it includes multiple parties, such data will not be imported.

Out-of-box data maps are available only in English

In Microsoft Dynamics CRM, the out-of-box data maps for Salesforce.com are not localized and hence are available only in the English language. Because of this, if your source data is localized (in other languages), you will need to manually map your data during import. To change the transformation mappings, export the data map, edit it, import it, and then use it to map the data.

Opening a Data Import template or XML Spreadsheet 2003 files for reimport fails with Microsoft Excel 2010

The Data Import templates and files configured for reimport (by using Export to Excel) are in XML Spreadsheet 2003 format. Opening an XML Spreadsheet 2003 file that has data validation fails with Excel 2010. This is a known issue with Excel 2010. The issue will be addressed in the Excel 2010 Service Pack 1 release in February 2011. To work around this issue, save the file before you open it.

Incorrect data could be imported if the Number format of numeric data cells is changed to "Text" in XML Spreadsheet 2003 files

When you create records through import by using an XML Spreadsheet 2003 file, make sure that all cells that contain numeric data have the Number format set to Number. If the format of a cell that contains numeric data is changed to Text, it could lead to import failure or incorrect data being imported. This is because the numeric data in the cells is always converted and internally stored in English regardless of the operating system’s number format. However, if the cell type is Text, the data is internally stored as plain text.

For example, suppose the Number format of your operating system is German (Germany), and the cell format in the XML Spreadsheet 2003 file is Number. If you specify "1.234" (intended as one-thousand, two-hundred and thirty-four in German), the XML Spreadsheet 2003 internally converts it in English number format and stores it as "1,234" because in German, "." is a Thousand separator. This is imported correctly in Microsoft Dynamics CRM.

On the contrary, if you change the cell type to Text, the data "1.234" is not converted and is stored in English as-is, that is "1.234". In English, "." is a decimal separator, so the data is imported as "1.234" (one point two three four), which is incorrect.

To avoid this, do not change the Number format of cells that contain numeric data.

Charts loading icon shows indefinitely in dashboards

If you try to create or edit a dashboard when the charts on the dashboard are still loading, the charts loading icon may show indefinitely. To work around this, on the Dashboards tab, in the Actions group, click Refresh All.

Top X or Bottom X charts show an error when they use more than 50,000 records

If a chart uses a view that has more than 50,000 records, an error message is displayed. To work around this, filter the view to show fewer than 50,000 records.

JAWS reads the multi-line audit history of individual records in a way that is not comprehensible by customers who are blind

If you are using JAWS reader to read the audit history of an individual record, and if the audit history has a single row containing multi-line data for all fields that changed, JAWS reads the data in a way that is incomprehensible for customers who are blind.

For example, say that you added values to two different fields, such as Account Name and Account Number, in one single event and saved the form. The audit history will show the following:

Event

Changed Field

Old Value

New Value

Create

Account Name

 

Contoso, Ltd

Account Number

 

C12O34

For the single row of the "Create" event, JAWS reads all the fields in the Changed Field column first, and then it reads all the values in the Old Value column, and then the New Value column. So, in the above example, when JAWS reaches the Changed Field column, it reads the following in the same sequence:

Account Name, Account Number, Contoso, Ltd, C12O34

This makes it difficult for the customers who are blind to understand which field the old/new value corresponds to. The workaround is to drill down in the event and read the contents field by field.

An updated time in a Date and Time field cannot be saved in the Create Record step of a workflow

Note: This item refers to an issue that is in Microsoft Dynamics CRM 2011 Update Rollup 5.

If you set a value for a Date and Time field in a record form in the Create Record step and save and close it, and then open the properties of the Create Record step and select a different value for this Date and Time field, the changed value for Time is not saved.

For example, your workflow includes a Create Record step for creating a Task record. While setting the properties of this step, in the Due field of the Task record form, you set the value for the date and time to 10/10/2011 and 4:00 PM, and save and close it. Now, if you open the Create Record step properties again, and select the date and time for the Due field as 10/12/2011 and 6:00 PM (instead of typing the value), and save and close the form, the changed value for time is not saved.

When you open the newly created Task record, the Due field shows the date and time as 10/12/2011 and 4:00 PM instead of the updated 10/12/2011 and 6:00 PM.

There are two ways to work around this:

Microsoft SQL Server 2005 Reporting Services Reporting Services reports may fail to publish on Microsoft SQL Server 2008 Reporting Services due to incompatibility

There are some reports that are supported by Microsoft SQL Server 2005 Reporting Services, but not by Microsoft SQL Server 2008 Reporting Services. Such reports will fail to publish on Microsoft SQL Server 2008 Reporting Services.

Reports may not be published during Microsoft Dynamics CRM Reporting Extensions Setup

Reports may not be published during Microsoft Dynamics CRM Reporting Extensions Setup if the user running the Setup does not have the administrative privileges on the organization database. To work around this, grant the user running Microsoft Dynamics CRM Reporting Extensions Setup the db_owner privilege on the organization database, and repair the Microsoft Dynamics CRM Reporting Extensions installation.

Import of Microsoft Dynamics CRM 2011 organization database to a Microsoft Dynamics CRM 2011 Update Rollup 5 deployment may fail while publishing reports from database

Note: This item refers to an issue that is in Microsoft Dynamics CRM 2011 Update Rollup 5.

If you have deployed custom assemblies on a SQL Server Reporting Services server, and then upgrade to Microsoft Dynamics CRM 2011 Update Rollup 5, when you import an organization from this server to a deployment that uses another SQL Server Reporting Services server that does not have these custom assemblies, the import of Microsoft Dynamics CRM 2011 organization may fail while publishing reports from the database.

To work around this, deploy and register the custom assemblies on the other SQL Server Reporting Services server and then try again.

When you add two or more sub-grids to a section in a form, or if you add a chart after a sub-grid, the form displays with incorrect formatting and white space

The workaround to get a sub-grid or chart to display correctly is to not select the "Automatically expand to use available space" property.

Using a dynamic value for the Default Value field of a Prompt and Response step causes dialog failure if the dynamic value is evaluated as null or empty at run time

Note: This item applies if:

If a Prompt and Response step in a dialog has the data type for a response type set to Text, Integer, or Float, and if the Default Value field of such step is set to a dynamic value (slug), the dialog fails at run time if the dynamic value is evaluated as null or empty.

To work around this:

  1. After you upgrade to Microsoft Dynamics CRM 2011 Update Rollup 6, deactivate each dialog that contains a Prompt and Response step like these.
  2. Open the Prompt and Response step and click Save and Close without making any changes.
  3. Click Activate to activate the dialog.

Dialog fails at runtime with a FormatException error if the dialog contains a Query step with conditions for comparing Whole Number, Float, or Option Set fields

Note: This item refers to an issue that is in Microsoft Dynamics CRM 2011 Update Rollup 5.

If a dialog contains a Query step that includes conditions for comparing Whole Number, Float, or Option Set fields and if while running the dialog a user specifies an Integer value of four or more digits, for example, 2000, the dialog fails with a FormatException error.

To work around this:

  1. After you upgrade to Microsoft Dynamics CRM 2011 Update Rollup 5, deactivate the dialogs that contain query steps like these.
  2. Open each query step that includes conditions to compare Whole Number, Float, or Option Set fields.
  3. Click Save and Close without making any changes.

Dialog displays an Unexpected Error message when attempting to assign a null value

If an Assign Value step in a dialog attempts to assign a null value to a variable or input argument, you will see the following error message:

Unexpected Error

An error has occurred.

Try this action again. If the problem continues, check the Microsoft Dynamics CRM Community for solutions or contact your organization's Microsoft Dynamics CRM Administrator. Finally, you can contact Microsoft Support.

Error code: 0x80040216

The error occurs because the dynamic value selected from the record is empty and cannot return a value. To work around this, add a condition step that checks if the value selected from the record is null, and if the condition returns False (that is, the value is not null), add the Assign Value step.

While doing a bulk edit of records, if you select the option "False" or you select the default value in an option set, records are not changed

There currently isn't a workaround for this issue. Avoid selecting False or selecting the default value in an option set when you bulk edit records.

Action buttons for doing bulk editing, such as Add Note, Set Regarding, Cancel, and Mark Complete, are not available on the toolbar in the Activities list, or in Advanced Find search results for a specific activity type

The workaround is to use Advanced Find, but instead of selecting the specific activity type, such as Task, select Activity Entity. Then, further refine the search filter to find the specific activity type. In the list of activities that are returned, all bulk edit action buttons are available.

After you have deleted the Activities or the Closed Activities navigation link from an entity form, you are unable to add it back using the form editor

The Activities and Closed Activities form navigation links use the same underlying relationship between the parent entity and activity entity. If you remove one or both of these links, you can add only one of them back by using the form editor. If you want to re-add both of them, you have to export the FormXML, re-add the links in that file, and then import it back in Microsoft Dynamics CRM.

Default solution export fails with an error that the system administrator does not have the correct privilege

A user who gets the default solution error during export is not assigned to the correct access mode. When a user is created in Microsoft Dynamics CRM, there are three access mode options: Read-Write, Administrative,and Read. If the access mode Administrative was selected, then the privileges of the user are restricted. To enable a successful export, change the access type of this user to Read-Write.

Web resources can be deleted even if they are linked to in the form navigation

Web resources can be deleted because they are not specified as dependent components for form navigation. If this happens, either re-add the Web resource, or point the link to a different Web resource. Also, when you export a form, any Web resource associated with the form navigation is not automatically exported. You have to add any associated Web resources to the solution manually for them to be exported.

Behavior of a dynamic marketing list that has no query

If a distribution job, such as a quick campaign, is run on a dynamic marketing list that does not have a query specified, the job creates activities for all records of the member type that is specified in the marketing list. For example, if the member type selected in the marketing list is Account, the distribution job creates activities for all account records that the current user has access to.

This behavior applies to the following distribution jobs:

To work around this, do the following:

  1. In the campaign record, under Marketing, click Target Marketing Lists, and identify the dynamic marketing list that does not have a query specified.
  2. Remove this marketing list from the list of target marketing lists or specify a query in the dynamic marketing list to retrieve the required records.

You cannot resolve or cancel a case that has an associated recurring appointment that is still open

You have to cancel or close any recurring appointments that are associated with the case.

Solution import fails when you import custom Appointment, RecurringAppointmentMaster, and KBArticle forms

Delete the custom forms before exporting the solution.

Microsoft Dynamics CRM 2011 Beta allowed customization for these forms. Although the custom forms will continue to work with an upgraded system, you cannot export a solution that contains these custom forms and then import the solution into another system.

When you try to import a solution with a Recurrence Appointment entity, you get an error message that the solution XSD is invalid

Note: This item refers to an issue that is in Microsoft Dynamics CRM 2011 Update Rollup 5.

This happens if you export a solution from a Microsoft Dynamics CRM 2011 Update Rollup 5 organization and import it into a Microsoft Dynamics CRM 2011 organization, and you have a custom lookup field from the Recurrence Appointment entity mapped to a lookup field on the Appointment entity. The workaround is to remove the mapping between the two lookup fields, recreate the solution, and then try to import again. After you remove the mapping, Microsoft Dynamics CRM 2011 will behave as expected.

Enabling a second language after Activity Feeds is installed results in multiple languages displaying at the same time

Note: This item refers to an issue that is in Microsoft Dynamics CRM 2011 Update Rollup 5.

Multiple languages being displayed at the same time can occur if you enable a second language after creating any Post-configuration entities, such as accounts, leads, and contacts. You may see some views of Activity Feeds display the first language that you chose mixed with the new, second language. If this happens, you have to delete Activity Feeds and install it again. Before you can uninstall Activity Feeds, you must delete all Post-configuration entities and publish all customizations. Then you can uninstall Activity Feeds and reinstall it.

When you create a dialog, you receive the error message "Unexpected error" or "Invalid argument"

Note: This item refers to an issue that is in Microsoft Dynamics CRM 2011 Update Rollup 5.

An error is generated when the dynamic value for Process Execution Time is used in the following conditions:

The workaround is to set the Before or After operand for the Execution Time variable to one minute (or a similar short time period) such as "{1 Minute After Execution Time(Process)}".

Document Management Known Issues

User code service does not work correctly if SharePoint is installed on an Active Directory service domain controller

If SharePoint Server is installed on an Active Directory Service domain controller, the User code service does not work correctly. To work around this, run the following Windows PowerShell script:

$acl = Get-Acl HKLM:\System\CurrentControlSet\Control\ComputerName

$person = [System.Security.Principal.NTAccount]"Users"

$access = [System.Security.AccessControl.RegistryRights]::FullControl

$inheritance = [System.Security.AccessControl.InheritanceFlags]"ContainerInherit, ObjectInherit"

$propagation = [System.Security.AccessControl.PropagationFlags]::None

$type = [System.Security.AccessControl.AccessControlType]::Allow

$rule = New-Object System.Security.AccessControl.RegistryAccessRule($person, $access, $inheritance, $propagation, $type)

$acl.AddAccessRule($rule)

Set-Acl HKLM:\System\CurrentControlSet\Control\ComputerName $acl

Limitations while accessing sites or document libraries on SharePoint Online through Outlook

Note: This item refers to an issue that is in Microsoft Dynamics CRM 2011 Update Rollup 5.

Documents will not be rendered inside Microsoft Dynamics CRM if you are using external SharePoint URLs that are not accessible from the corporate network

The documents stored on SharePoint will not be available in Microsoft Dynamics CRM if you are using external SharePoint URLs that are not accessible from the corporate network. The workaround is to create two different document location records for the internal and external SharePoint URLs.

New Document action does not save the document

The New Document action saves the document locally and not on SharePoint server if the operating system is Windows Vista or Windows Server 2008.

Limitations in performing actions related to SharePoint Document Management in the Microsoft Dynamics CRM list

You will not be able to perform any actions related to SharePoint Document Management in the Microsoft Dynamics CRM list if .htc extensions are not added to the list of allowed file types on SharePoint. To work around this, add .htc extensions to the list of allowed file types:

  1. Copy the AllowHtcExtn.ps1 script file to the server that is running Microsoft SharePoint Server 2010.
  2. In the Windows PowerShell window or in the SharePoint Management Console, run the command: AllowHtcExtn.ps1 <Web Application URL>.

    Example: AllowHtcExtn.ps1 http://servername

    Alternatively, in SharePoint, set Browser File Handling to Permissive.

Microsoft Dynamics CRM List component tries to open WAC even when WordViewer.aspx is not available

By default in SharePoint, the Document Open setting is set to Open in Browser, and if Office Web Application Companion (WAC) is not installed on the SharePoint server, SharePoint opens the documents in the Office clients. Even if WAC is not installed, the List component tries to open documents in WebViewer and fails. To work around this:

  1. Start Internet Explorer, and then open the SharePoint site collection.
  2. Click Site Actions, and then click Site Settings.
  3. Under Site Collection Administration, click Site Collection features.
  4. For Open Documents in Client Application by Default, click Activate.

Automatic creation always occurs in the document library with a name the same as the entity schema name

The automatic creation of the folders always occurs in the document library with the name the same as the schema name of the entity. For example, if the folder is being created for an account, the folder will always be created in the document library with the name account, which is the schema name of the Account entity in Microsoft Dynamics CRM. It is not possible to configure auto-creation of folders in another document library, such as customer. However, as a workaround, you can manually add a different document library from the SharePoint Document Locations (in the Navigation Pane, click Settings, click Document Management, click SharePoint Document Locations), and then select this document library in the Add Document Location dialog box.

An unhandled exception occurs when you try to enable Document Management if there are two entities with the same display name

An unhandled exception occurs when you try to enable document management from the Document Management area and if there are two entities with the same display name.

You will not be able to enable Document Management for other entities except for the selected default (out-of-box) entities. In this case, automatic creation of folders will also not occur because you will not be able to specify the SharePoint site URL in the Document Management Settings dialog box. To work around this issue, change the display name of the entities to make sure that no two entities have the same name. There is no workaround to enable automatic creation in this case.

The Activate button is disabled when you try to activate the Microsoft Dynamics CRM List component for SharePoint

Make sure you start the Web service "Microsoft SharePoint Foundation User Code Service" before you install the Microsoft Dynamics CRM List component.

To start the Web service:

  1. Open a Windows PowerShell window or the SharePoint Management console.
  2. Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN.
  3. Type the command: stsadm -o provisionservice -action start -servicetype Microsoft.SharePoint.Administration.SPUserCodeService -servicename SPUserCodeV4.

The "The Server is busy." error message appears when you try to activate the Microsoft Dynamics CRM List component on SharePoint

Restart the Web service and try again.

To restart the Web service, in the Windows PowerShell window or in the SharePoint Management console, run the following commands:

  1. stsadm -o provisionservice -action stop -servicetype Microsoft.SharePoint.Administration.SPUserCodeService -servicename SPUserCodeV4.
  2. stsadm -o provisionservice -action start -servicetype Microsoft.SharePoint.Administration.SPUserCodeService -servicename SPUserCodeV4.

Microsoft Dynamics CRM List component activation might fail for the root site collection if Microsoft SharePoint Foundation 2010 is installed on a Workgroup computer

If you install Microsoft SharePoint Foundation 2010 on a Workgroup computer, the activation of Microsoft Dynamics CRM List component for the root site collection might fail. To work around this, create a new Web application using SharePoint Central Administration, and then create a new site collection under it.

Copyright

This document is provided "as-is". Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.

Some examples depicted herein are provided for illustration only and are fictitious.  No real association or connection is intended or should be inferred.

This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.

© 2012 Microsoft Corporation. All rights reserved.

Microsoft, Excel, Internet Explorer, Microsoft Dynamics, Outlook, SharePoint, Silverlight, Windows, Windows PowerShell, Windows Server, and Windows Vista are trademarks of the Microsoft group of companies.

All other trademarks are property of their respective owners.

Third Party Notices (JQuery)

Documentation Feedback

The Microsoft Dynamics CRM Documentation Team welcomes your suggestions and comments about the documentation. You can quickly and directly send e-mail feedback to Documentation Feedback. All feedback must be in English. Your feedback will be used to make improvements to the content.