2013 Microsoft Corporation. All rights reserved.
This document provides important, late-breaking information about Microsoft Dynamics CRM Online Fall '13, Microsoft Dynamics CRM Online Fall ‘13 Service Update, Microsoft Dynamics CRM 2013, and Microsoft Dynamics CRM 2013 Update Rollup 1 (UR1). You will also find information about known issues. Where possible, workarounds are provided for the known issues.
This is version 1.2 of this readme, published December 6, 2013.
This section is for general issues that occur in Microsoft Dynamics CRM Online Fall '13, Microsoft Dynamics CRM Online Fall ‘13 Service Update, Microsoft Dynamics CRM 2013, and Microsoft Dynamics CRM 2013 UR1.
If the default for Revenue is System Calculated, then the Est.Revenue field must be removed from the quick create form. Otherwise, its data will not be saved in the system.
You might notice that a blank notification is shown on the message bar at the top of the Quick Create form when the preventDefault() API is used.
You might notice that red squares on the background image do not match the text location in the CRM Navigation Tour in Right-To-Left languages (like Hebrew and Arabic). This could cause difficulties reading the text and completing the Navigation Tour.
Although customizers are allowed to define a quick create form for the Activity type, clicking the Quick Create option always takes the user to the full create experience. There is not known workaround for this issue in this release.
When you navigate through a process by creating a new record, links to the older record are lost in the business process flow, thereby leaving it orphaned and disabling navigation.
For example, consider a process that moves through Campaign to Email to Campaign Response to Lead to Opportunity entities. Using this process, the user creates a record for email (E1), campaign response (CR1), lead (L1), and opportunity (O1). Now, the user navigates back to a stage on the campaign and creates a new flow E2 > CR2 > L2 > O2. The user then goes back to a stage on the campaign, selects the old record E1 and navigates through CR1 and L1.
At this point, the user is unable to navigate any further to the ‘old' opportunity O1, since as soon as the user navigated to E2 from a stage in the campaign, the previously navigated path from L1 to O1 was lost.
When you click a valid email address in a recipient field in an email that is in read-only mode, you won't be notified of the need to create a record for this email address.
To, CC, and BCC fields in an Email activity form can contain unknown email addresses. In CRM 2011, if you clicked such an email address, a dialog box opened that asked you to resolve the issue by choosing an existing record or manually creating a new record for it.
In CRM 2013 and CRM Online Fall ‘13, these unknown email addresses will not appear in read-only email forms, such as in sent email or incoming email. However, if the email form is in an editable state, like when you are replying to an incoming email, these email addresses will appear properly. This issue is just visual. Email will be properly sent to unknown email addresses.
Also, these unknown email addresses will be shown properly in grids and on the Activity wall on the form.
The generic error is caused because Safari on MAC times out for long-running synchronous operations and Microsoft Dynamics CRM captures the time out and displays a generic error. These are typically administrator run operations, such as creating entities, importing/exporting translations, and publishing customizations. Note that some operations might still complete in spite of the error. The server still completes processing the request in some cases and a refresh on the page would show the results. The workaround is to use a Windows operating system to perform these operations.
Microsoft Lync presence icons work only in Internet Explorer and do not work in other browsers.
Upload of files in iPad to a CRM on-premises instance does not work (256736)
This is due to a bug in how iOS 6.0 handles Windows NT Authorization. The work around is to use a non-iOS device to upload documents (like images).
Read-optimized forms do not appear in CRM 2013 or CRM Fall ‘13 for entities that are still displayed in the classic view (entities that have not been refreshed and are using the old UI, such as Territory). The settings for read optimization are removed from the Options menu in the UI and the classic view is always displayed. Refreshed entities, such as Account, Contact, and custom entities, are not impacted by this and will continue to have the new UI.
Composite control like Contact's full name in a business process defined in the Microsoft Dynamics CRM December 2012 Service Update or Microsoft Dynamics CRM 2011 Update Rollup 12 release will no longer appear in the processes. As a workaround, individual contributing fields can be added to the process definition.
Due to certain IE constraints, pressing “back” may reload the current page or may skip a previous page. When these situations occur, use the Nav Bar or in-page links for further navigation. Some example areas where this may happen:
- Navigating from a form to an associated grid, then pressing back
- Creating an email record and then trying to press back
Saving the Account created by clicking the + New button for the Parent Account Lookup in an Account form displays an error.
Create an account by using Quick Create or the New action on Accounts grid and then choose it as the Parent Account in the account form.
There are certain cases when the navigation history of the user may be disturbed, or the app could have failed to capture an event. This may happen to call browsers. In these cases, multiple backs may be required to return to the previous page, or the user may need to use on-page links to navigate including the Nav Bar.
With the Workspace removed in Orion, upgrading organizations will still maintain their sitemap, but Workspace will just be another area like others, treated with no special capabilities. For new organizations that are looking for the things that used be in the Workspace, like Calendar and Reports, will find these items under the Tools section of the Sales, Marketing, and Service areas.
If a user signs out, only that user may sign back in.
If a user must change the server or organization, they must uninstall the application and reinstall it to get back to the Welcome screen in which they can enter a different server/organization.
It is not possible to change the signed-in user once the app is configured to a server and a user has signed in. Even uninstalling the app and re-installing it will still show an error indicating that the app is set up only for a specific user.
To completely clear the app, after you uninstall the app, you must clear the Indexed DB folder (C:\Users\%USERNAME%\AppData\Local\Microsoft\Internet Explorer\Indexed DB).
You may have to sign in as a different user and use the command prompt as an administrator to clear the Indexed DB folder, because some files in this folder can be held by the Host Process for Windows Tasks.
When users try to connect to Microsoft Dynamics CRM Server
2013 (on-premises) configured for Internet Facing Deployment (IFD) server on a
Windows device, they will be prompted at an Active Directory authentication
screen, which overlays and hides the proper authentication screen that is
intended for the user. Users may attempt to enter credentials on this
authentication screen which will not work and repeatedly prompt for logon
This issue occurs when the server running IIS where the Microsoft Dynamics CRM web application is installed has Negotiate and NTLM Windows authentication providers enabled on certain Microsoft Dynamics CRM website features.
The local workaround is to click or tap Cancel on the Active Directory authentication screen to reveal the proper IFD authentication screen behind it.
To resolve the issue, run a Repair of Microsoft Dynamics CRM Server on the server running IIS where the Web Application Server role is installed. To resolve this issue by running Repair, the Microsoft Dynamics CRM deployment must already be configured for claims-based authentication and IFD.
The Windows 8 version of the Microsoft Dynamics CRM app requires an Internet connection for on-premises deployments. CRM Online deployments will be able to use the app in read-only mode while disconnected from the Internet. If an on-premises user attempts to use the app while not connected to the Internet, the user will see an error message. After dismissing this recurring error message, the app will simply show a blank screen. To work around this problem, after you connect to the Internet, completely close the app (swipe/drag from the top of the screen to the bottom) and reopen the app.
If you do want Alert() blocking and confirm() to work, you can use Xrm.Utility.Alert() and Xrm.utility.confirm(), which works across both CRM for web browser and tablets. These APIs have call backs that will wait for user input before running the next line of code.
When you connect with the iPad app by using the Microsoft
online services environment or IFD authentication channels, the app will stop
responding on the loading screen if the connecting user is a disabled CRM user
The workaround is to repair Microsoft Dynamics CRM 2013 Server after IFD has been configured.
On edit forms in Microsoft Dynamics CRM for tablets, users cannot edit the Owner field. This means that after a Create form is saved, this information is not editable. To work around this, the user can use Assign on the command bar to assign the record to a new user.
If a user does not have any of these read privileges, they will get an error message about Insufficient Privileges.
CRM for tablets does not support activities like Fax and Letter. These activity types are returned by the search results and shown to the user.
The workaround is to change the search entities. To do this, follow these steps:
1. Under Settings > Administration > System Settings > Select entities for search on CRM for tablets, click Select.
2. Remove the Activity entity that you don't want in search, by selecting it in the Selected Entities column and clicking Remove.
3. Add the child activity entities, like Phone Call, Task, and Appointment, which are supported in the CRM for Tablet app by selecting them in the Available Entities column and clicking Add.
4. Click Save and Close.
The default value should be Existing for the Select Product field. But it may select Write-In as the field default.
You can save appointments that conflict with other calendar entries. CRM for tablets does not check for these conflicts and you are not informed.
CRM for tablets shows only the system view as the default view.
If you re-start the app after 10 seconds or save the record (by navigating away or clicking Save), then there will be no data loss.
While a form is loading, if you try to edit a field, you will get a read-only view of that field and its data. After the form has completed loading, if this field is still in an expanded state, it will still be read-only.
The workaround is to click or tap outside the field and then try to edit it again. The field should change to edit mode.
During first time configuration of a CRM for tablets application, a large amount of operations and UI definitions are generated. If verbose logging is turned on for CRM server, the volume operations that are logged prevent the definition generation from succeeding.
The workaround is to turn off verbose logging and connect to the organization with CRM for tablets. Then turn logging back on. The definition generation happens only the first time after you publish customizations.
When you use the command to close a custom activity, there will be no confirmation dialog box, as is present in the web client; instead, the record will be completed automatically.
If a field on a form is given an invalid value (or is required, but not complete) and becomes hidden through form logic (before or after it becomes an error), and you try to save the form, the field is not made visible. You are told there is an error somewhere on the page. The only workaround is to navigate away from the page, which means you will lose your changes and need to start over.
If you make a personal view, and share that view with another user, the other user will not be able to use this view in CRM for tablets. However, it will be available to them on the web client.
Regardless whether the 12-hour or 24-hour setting is selected at either the Administrator or User level, CRM for tablets displays only a 12-hour time format.
You can rearrange pinned tiles on the dashboard. However, it is difficult to get some tiles to relocate to certain positions.
If you pin a record to the start screen, and then the record set navigation to move to another record that has not yet been pinned to the start screen, the command for that record will say Unpin from Start rather than Pin to Start.
The workaround is to manually refresh the page.
Tiles on entity forms do not automatically update when the corresponding information is changed on the form.
The workaround is to manually refresh the page.
If you use the Start screen menu to unpin a secondary tile for CRM for tablets and then return to the app the command for that item, it will still say Unpin from start. However, the command button will still perform the correct action (pin).
The workaround is to manually refresh the page.
If user is on an entity form when auto save occurs, the Owner field will appear to become blank. The data is not lost; this is an issue only of how the field value appears in the UI.
When a customizer tries to customize the Campaign Response entity, he or she will receive an error message upon saving the changes. The customization will not be saved.
While the correct behavior should be that the Campaign Response entity can be customized regardless of the state of the Allow Quick Create check box, the following workaround is necessary in order to allow customization of the Campaign Response entity.
1. You should already be in the customizations area, editing the Campaign Response entity.
2. Notice that the Allow Quick Create check box is selected and is in a disabled state.
Now follow the remaining steps for the browser you are using:
3. While you are on the page, press F12 to open the Internet Explorer Developer Tools.
4. Allow a couple of minutes to load the toolbar completely, and then click the Arrow button (the first button that is used for selection) from the tool bar and point with the mouse to the disabled Allow Quick Create check box. This will highlight the HTML code snippet for the check box.
5. To remove the disabled attribute, click the word disabled and press Delete. This will enable the check box.
6. To close the Developer Tools window, click the close box (X) in the upper right corner of the developer tools pane.
7. Clear the Allow Quick Create check box and click Save. You can now customize the entity.
3. While you are on the page, press Ctrl+Shift+I to open the Chrome Developer Tools.
4. Allow a couple of minutes to load the tools completely, and then click the Magnifying Glass button (the third button at the bottom) from the tool bar and point with the mouse to the disabled Allow Quick Create check box. This will highlight the HTML code snippet for the check box.
5. To remove the disabled attribute, click the word disabled and press Delete. This will enable the check box.
6. Clear the Allow Quick Create check box and click Save. You can now customize the entity.
3. While you are on the page, click Ctrl+Shift+I to open the native Firefox Developer Tools (or Firebug if you have the Firebug extension installed).
4. Allow a couple of minutes to load the toolbar completely, and then click the Inspect button (the second button at the top) from the toolbar and point with the mouse to the disabled Allow Quick Create check box. This will highlight the HTML code snippet for the check box.
5. To remove the disabled attribute, select disabled=”” and press Delete. This will enable the check box.
6. Clear the Allow Quick Create check box and click Save. You can now customize the entity.
CRM 2013 uses the webkit scrolling cascading style sheets (css). However, Chrome seems to have discontinued the support of –webkit-overflow-scrolling, which in turn led to various scroll issues reported by the following bug:
The Chrome Beta released recently claims to fix the scrolling and performance issues. We recommend upgrading to the Chrome Beta.
The workaround is to open the lookup control and delete by removing the value in the dialog box.
The contextual menu for grids, which you can view by right-clicking a record on the grid, will not be displayed on an iPad browser. Instead, the default Safari browser menu will be displayed. This is because the contextual Safari browser menu cannot be overridden in iOS devices.
When the focus is on an input text field like the Post field on the Activity Feeds wall, the keyboard comes up for a brief second and the entire page reloads. This happens only in the dashboard page. To work around this issue, please go to the “What's new” tab to create a post on the Activity Feeds wall.
This happens when attempting to sign in to a CRM 2013 on-premises environment. After every 5 to 10 operations, it prompts you to sign in again. The workaround is to:
1. Provide the fully qualified name of the server, followed by the organization name:
of server>/<org-name> >
2. Provide the IP-Address, followed by the organization name:
When you are using the Chrome 29 browser, and you start scrolling on the CRM forms that have the Bing maps control, the browser freezes. This happens when the Bing map tries to zoom in and plot the address.
The workaround is to disable Bing maps functionality on these forms or use Chrome 28.
CRM for Outlook is not backward compatible with any version of Microsoft Dynamics CRM 2011. This means that it is not possible to configure a CRM 2011 organization from CRM 2013 for Outlook. This also means that a CRM 2011 for Outlook client that is configured against a CRM 2011 organization will no longer work with the existing CRM 2011 organization after you upgrade it to CRM 2013 for Outlook.
In the CRM Online Fall '13 and CRM 2013 releases, CRM for Outlook is not supported in the Citrix environment.
When you use CRM for Outlook in offline mode, actions that change the state of an entity might not be synchronized when you go back online. A data synchronization error message might appear in this case.
For example, if you convert a task to an opportunity offline, the opportunity will not be synchronized when you go back online.
The workaround is to perform these types of actions only in online mode in CRM for Outlook.
We do not support upgrading from the Early Access prerelease of CRM for Outlook to the final release of it. You must uninstall the Early Access build of the client and install the release build.
If you have an Early Access server and upgrade to the final release, we do not support the Early Access CRM for Outlook client against a final release server. If you have this scenario, you must make sure that if your end-users are offline, they must go back online before you upgrade the server to the final release. After the server is upgraded, they should upgrade all clients to the final release build.
When you use CRM for Outlook in offline mode, any action that tries to open a Mailbox record will display an error.
The Mailbox entity's form is not supported in offline mode. Please do not click links to Mailbox records. If you do, simply navigate to other records or close the form.
Sometimes after installation of CRM for Outlook 2013, the loading splash screen doesn't always close automatically even though Outlook and finished loading in the background. This loading screen may show for upto 10 minutes even though loading of CRM for Outlook has completed.
CRM 2013 supports server-side synchronization capability for Microsoft Dynamics CRM on-premises customers who are using Microsoft Exchange on-premises or POP3/SMTP supported mail servers (Outlook.com, Windows Live Mail, Gmail, Hotmail, Yahoo! Mail, and MSN). This capability works with users, queues, and forward mailboxes.
However, the capability is not available for CRM Online customers in Microsoft Dynamics CRM Online Fall ‘13.
To enable server-side synchronization, you must install both the Asynchronous Processing Service server role and the Email Integration Service server role.
The server-side synchronization may show failures because of potential deadlocks in recurring appointment synchronization. In most cases those failures will be successfully retried in next run of server-side synchronization. However, these deadlocks may impact server performance.
In Outlook with server-side synchronization, in a rare case where you change a field of a synchronized item that is not synced with CRM, the icon of that item does not change back to CRM icon. This is due to server-side synchronization does not detect any changes.
The workaround is to modify some other fields of the item that will be synchronized with CRM. Once the synchronization happens the CRM icon will appear again.
If Federal Information Processing Standard (FIPS) is enabled on Microsoft Dynamics CRM, you cannot use server-side synchronization to send emails through Hotmail, Outlook, Live, and MSN email systems.
The workaround is to not enable FIPS on Microsoft Dynamics CRM if you want to configure server-side synchronization by using SMTP to send emails through Hotmail, Outlook, Live, or MSN email systems. For more information about FIPS, go to FIPS 140-2 Compliancy with Microsoft Dynamics CRM.
If you use Microsoft Dynamics CRM Language Packs for additional languages in your system, you will notice that on update from Microsoft Dynamics CRM December 2012 Service Update to Microsoft Dynamics CRM Online Fall ‘13 Service Update, the base language translations are preserved but, some of the localized labels for the business process flows are not carried over. Instead, they are shown in the base language in the CRM web application or CRM for Outlook.
The missing translations belong to the objects that were added or modified in the business process flow before you updated your system to Microsoft Dynamics CRM Online Fall ‘13. For example, if you modified a stage or added new steps in the stage of the out-of-the-box business process flow, the Language Pack label translations for these objects are missing in the updated CRM system. The translations for the labels of the unchanged out-of-the-box objects are displayed in the correct non-base languages.
You can easily restore the missing translations, if you follow the following procedure. Make sure that you have the System Administrator or System Customizer security role or equivalent permissions.
· If using the CRM web application, on the nav bar, click or tap Microsoft Dynamics CRM > Settings. Settings appears on the nav bar. Click or tap Settings > Customizations > Customize the System.
· If using CRM for Outlook, in the Navigation Pane, expand your organization if necessary, and then click or tap Settings > System > Customizations > Customize the System.
In web application or Outlook, continue:
1. In Customize the System , click or tap Export Translations to export the labels and their corresponding translations. Save the exported translations .zip file on your local disk.
2. Open the translations .zip file with Windows Explorer. Copy the CrmTranslations.xml file to another folder on your local disk and edit with Microsoft Office Excel, as a workbook.
3. In the CrmTranslations.xml file, in the Localized Labels worksheet, find the rows for the Workflow Categories entities that represent the business process flow labels in Microsoft Dynamics CRM Online Fall ‘13. In the Workflow Categories row, the columns that hold the label values use the language codes for column names. For example, for the English language, a column name is “1033”. Notice that, the cells for the non-base languages labels are blank, but the base language label contains the correct value.
4. In the same Localized Labels worksheet, find the rows for the ComplexControl entities that represented the business process flow labels in Microsoft Dynamics CRM December 2012 Service Update. Use the base language label in the Workflow Categories row to find the matching ComplexControl row. For example, if the Workflow Categories row has an English base-language label called “New custom step”, then the ComplexControl row that has the same label is a match.
5. Copy and paste the values for non-base language labels from the ComplexControl row to the corresponding cells in the matching Workflow Categories row. Repeat this for all Workflow Categories rows.
6. Save the CrmTranslations.xml file and copy it back into the exported translations .zip file.
7. Reimport the translations .zip. In the CRM Web app, click or tap Settings > Customizations > Customize the System and click or tap Import Translations. If you use CRM for Outlook, click or tap or tap Settings > System > Customizations > Customize the System and then click or tap Import Translations.
8. In Import Translations, select the updated translations zip file and import.
9. In Customize the System, click or tap Publish All Customizations, to publish the customizations.
10. To verify that the label translations are imported correctly for the non-base languages, switch your user language (a user language is one of the languages available in your CRM organization that you select as your preferred language) to a language for which the translations were updated. For example, if you updated the labels for German language, switch the user language to German (1031) and open an entity form that contains the business process flow with the updated translations. You will see the correct translations in the labels that previously were shown in the base language.
User interface-based automations
of CRM may not work for Internet Explorer 8 (272798)
Customer Care Accelerator (CCA) Reference Implementation, which is a sample application, has not been updated for CRM 2013 and CRM Online Fall ‘13. The SDK examples of CCA have not been updated for CRM 2013 and CRM Online Fall ‘13 and hence it will not work as expected. Customers who want to use UI-based automations are advised to use Internet Explorer 9.
The UII documentation has the following inaccuracies:
· UII Documentation indicates that for the Framework and Java DDA, Windows XP is supported.
This is an error; we do not support Windows XP for UII.
· UII Documentation indicates that the developer is responsible for Creating the WPF Cab Component.
This is no longer required. This component is integrated to the UII framework.
· UII Documentation mentions CRM 2011 in numerous places.
This should be read as CRM 2013.
The UII Hosted Application Toolkit is not in the Beta SDK distribution.
The workaround is to use the HAT Toolkit from the currently released system to author Automations and update them to CRM. You can find the current release here: http://dynamics.pinpoint.microsoft.com/en-US/applications/Customer-Care-Accelerator-for-Microsoft-Dynamics-CRM-2011-12884949176
UII now includes WPFCAB as part of the distribution. For any asset that contains a reference to Microsoft.Practices.CompositeUI.Windows.dll, you must remove that and replace it with Microsoft.Uii.Practices.CompositeUI.Windows.dll from the UII\<buildtype>\Framework directory.
Several tools in the SDK are still using older icons and images, and the occasional reference to CRM 2011.
CRM 2013 will ship Yomi fields on the form by default for Japanese organizations. However, the mobile forms (used when accessing CRM through a smartphone's browser or Microsoft Dynamics CRM for phones) will not include Yomi fields by default. A system customizer must go to Settings >Customizations > Customize the System to add Yomi fields to the relevant forms as needed.
When tracing is enabled, an error similar to the following appears:
Crm Exception: Message: Cannot create custom attribute <ENTITYNAME>' of type '<ENTITYTYPE>'.
This is a side effect of some additional logging we have added recently. This error can be ignored if the entity in question is properly created.
In an on-premises installation, when an organization is imported from CRM 2011 into a CRM 2013 deployment, such an organization will not be checked by the Legacy Feature Check tool for usage of server extensions that use the 2007 endpoint and other legacy Microsoft Dynamics CRM 4.0 features. So usage of such features will fail at runtime in CRM 2013. The 2007 endpoint is no longer supported and has been removed. The workaround is to run the tool manually from http://msdn.microsoft.com/en-us/library/dn281891.aspx
The workaround is to customize the form to have Account or Contact on the mobile form. Otherwise, you can still use the out-of-the-box forms and manually fill in the Customer field.
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.
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.
© 2013 Microsoft Corporation. All rights reserved.
Microsoft, Active Directory, Hotmail, Internet Explorer, Microsoft Dynamics, MSN, Outlook, and Windows are trademarks of the Microsoft group of companies.
All other trademarks are property of their respective owners.
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.