© 2013 Microsoft Corporation. All rights reserved.
This document provides important, late-breaking information about Microsoft Dynamics CRM 2011, Microsoft Dynamics CRM 2011 Update Rollup 5, and Microsoft Dynamics CRM 2011 Update Rollup 12, Microsoft Dynamics CRM Online November 2011 Service Update, and Microsoft Dynamics CRM December 2012 Service Update. You will also find information about known issues. Where possible, workarounds are provided for the known issues.
This is version 5.0.10 of this readme, published February 18, 2013.
Document Management Known Issues
Microsoft Dynamics CRM for Outlook Known Issues
Browser Compatibility Known Issues
When you want to close the form on an iPad, we recommend that you use the close button from the command bar. Otherwise there is a possibility that any unsaved data may not be saved automatically.
The ability to create quotes from the opportunity process form is not enabled by default. However, if the system customizer modifies the opportunity form by using the form editor to enable the quotes sub-list, end users will encounter an error. When you create quotes from the sub-list, the opportunity products are not transferred from the opportunity to the quote. After you save the quote, the totals will reset and you must click Get Products to retrieve the product line items from the opportunity and update the quote accordingly.
In this situation, the sub-grid will not display all the available rows of data when you expand the tab. The workaround is to customize the form by using the form editor to change the following settings:
Change the tab properties to select the Expand this tab by default property.
Change the sub-grid properties to de-select the Automatically expand to use available space property.
Note: This item is for Microsoft Dynamics CRM December 2012 Service Update only.
The Case, Contact, Opportunity, Lead, and Account entities all have new form layouts in Polaris. These forms are titled <entity name> (i.e. “Case”). In addition to this, each of these entities has the previous form layout from Microsoft Dynamics CRM 2011 – titled “Information.” All of these forms are able to be rendered using the new Updated rendering mode.
The following issues occur when you add or edit slugs in workflows, dialogs, and email templates:
In Email Template editor, you cannot type text after inserting a slug in the email template body section. This issue happens only when you use a Chrome or Safari browser. The workaround is to type on the next line and use the Backspace key to align the text after the slug, or alternately to type text first and then insert the slug.
If you close an email template form without saving your changes to text or slugs, your changes will be lost. No warning message is displayed.
Slugs embedded in dialogs or workflows can be modified using Copy and Paste operations (available from the right-click context menu) in a Firefox or Chrome browser. Slug values are not changed, and reopening the dialog or workflow will show that the original slug value is still there. For example:
The original slug is <account name>. Paste text within that slug to make it <Account Descriptive Name>.
Now, save and close the dialog or workflow, and then reopen it. The slug will still be <Account Name>.
In a dialog or workflow, when you create a Send email step, and you add text and a slug with multiple values and a default value in the email body, the slugs will be shown in the beginning of the email body (before the text). Also, when you delete a slug and add a new one, the new slug will appear as if it is just regular text. For example: Account Name instead of <Account Name>. This issue happens only in Internet Explorer 7 or 8 browsers. The slug value is not compromised, it is the display text that is editable.
In an email template, using keyboard shortcuts like Cut (Ctrl+X), Copy(Ctrl+C), and Paste (Ctrl+V) to edit slugs do not work in Firefox and Chrome browsers. The workaround is to select the entire slug text, and then redo the edit operations.
Note: This item is for Microsoft Dynamics CRM December 2012 Service Update only.
The Duplicate Detection dialog box is not shown when you create records using the new process flow forms for the Lead, Account, Contact, and Case entity. This is only a limitation for the new process flow forms.
Note: This item is for Microsoft Dynamics CRM December 2012 Service Update only.
Bing Maps on Lead, Account, and Contact records may not be available in all countries and regions.
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.
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.
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. To work around this issue, save the file before you open it.
If the file still does not open, do the following:
Add the following Microsoft Dynamics CRM URLs to your browser’s Trusted site security zone: login.live.com and signin.crm.dynamics.com.
- OR -
Unblock the security in the downloaded Excel file:
Right-click the downloaded file, and then click Properties.
On the General tab, for Security, click Unblock.
- OR -
In Microsoft Excel 2010, enable Protected View for files originating from Internet:
Open Microsoft Excel 2010.
Click the File tab, and then click Options.
Click Trust Center, and then click Trust Center Settings.
Click Protected View, and then select the Enable Protected View for files originating from Internet check box.
This issue is not observed when the files are opened with Microsoft Office Excel 2007.
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.
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.
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.
If you are using JAWS reader to read the audit history of an individual record, and if the audit history has a single row that contains multiline 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 this 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.
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.
Note: This item refers to an issue that is in Microsoft Dynamics CRM 2011 Update Rollup 5 and Microsoft Dynamics CRM Update Rollup 12.
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.
Note: This item refers to an issue that is in Microsoft Dynamics CRM 2011 Update Rollup 5 and Microsoft Dynamics CRM Update Rollup 12.
If you have deployed custom assemblies on a SQL Server Reporting Services server, and then upgrade to Microsoft Dynamics CRM 2011 Update Rollup 5 or Microsoft Dynamics CRM Update Rollup 12, 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.
The workaround to get a sub-grid or chart to display correctly is to not select the "Automatically expand to use available space" property. Also, please note that charts are not supported in sub-grids in the new process flow forms.
Note: This item applies to all the existing dialogs in Microsoft Dynamics CRM Online November 2011 Service Update after you are upgraded from the Microsoft Dynamics CRM Online November 2011 Service Update to the next service update.
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:
After you upgrade to the next Service Update, deactivate each dialog that contains a Prompt and Response step like these.
Open the Prompt and Response step and click Save and Close without making any changes.
Click Activate to activate the dialog.
Note: This item refers to an issue that is in Microsoft Dynamics CRM Online November 2011 Service Update and Microsoft Dynamics December 2012 service updates.
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:
After you upgrade to a new service update, deactivate the dialogs that contain query steps like these.
Open each query step that includes conditions to compare Whole Number, Float, or Option Set fields.
Click Save and Close without making any changes.
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.
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.
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.
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.
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 two access mode options: Read-Write and Administrative. 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 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.
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:
Quick campaign
Mail Merge on a dynamic marketing list
Campaign activity with the channel Letter via Mail Merge, Fax via Mail Merge, or E-mail via Mail Merge. A campaign activity with channels other than these works fine.
To work around this, do the following:
In the campaign record, under Marketing, click Target Marketing Lists, and identify the dynamic marketing list that does not have a query specified.
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 have to cancel or close any recurring appointments that are associated with the case.
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.
This happens if you export a solution from an organization that was in a previous service update or update rollup 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.
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.
An error is generated when the dynamic value for Process Execution Time is used in the following conditions:
The Response Type field of a Prompt and Response step is set to Date and Time or Date Only, and the Default Value field for the step is set to the execution time of the process "{Execution Time(Process)}".
For a Date and Time or Date Only input argument or variable, the Value field of the Assign Value step is set to the execution time of the process "{Execution Time(Process)}".
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)}".
When you change the view or try to look into the default view of an entity, you get an unknown error. This can happen if you have columns of data types “Duration” or “Timezone” in your view. To work around this, do not have a view that has columns of data type “Duration” or “TimeZone” that needs to be opened by Mobile Express for Microsoft Dynamics CRM.
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
If the Access data sources across domains option is set to Disable
in the Internet zone on the Security Settings tab of Internet options,
and if you specify a SharePoint Online site while configuring Document Management
through Outlook, the site validation fails with the error "Validation could
not be completed because List Component could not be detected." To work around
this, click the SharePoint site link shown in the message, and then enter your sign-in
credentials to authenticate. You must also select the Remember me and Keep
me signed in check boxes to continue to work.
If the Access data sources across domains option is set to Enable,
the site validation fails with the error "The URL that you specified is not
a valid SharePoint URL. Specify a correct URL and then try again." To avoid
this, either set the Access data sources across domains option to Disable
or sign in to the SharePoint Online site before configuring Document Management.
If a SharePoint Online site is already configured in Microsoft Dynamics CRM and you try to create or access a document location on this site from the Web client or Outlook by clicking Documents under Related in a record, the error "This page cannot be displayed in IFrame" is displayed. This is because when you click Documents, you are directed to the sign-in page that cannot be viewed in an IFrame. To work around this, click the Open this content in a new window link shown in the message, and enter your sign-in credentials to authenticate. For Outlook, you must also select the Remember me and Keep me signed in check boxes to continue to work.
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.
The New Document action saves the document locally and not on SharePoint server if the operating system is Windows Vista or Windows Server 2008.
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:
Start Internet Explorer, and then open the SharePoint site collection.
Click Site Actions, and then click Site Settings.
Under Site Collection Administration, click Site Collection features.
For Open Documents in Client Application by Default, click Activate.
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 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.
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:
Open a Windows PowerShell window or the SharePoint Management console.
Navigate to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN.
Type the command: stsadm -o provisionservice -action start -servicetype Microsoft.SharePoint.Administration.SPUserCodeService -servicename SPUserCodeV4.
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:
stsadm -o provisionservice -action stop -servicetype Microsoft.SharePoint.Administration.SPUserCodeService -servicename SPUserCodeV4.
stsadm -o provisionservice -action start -servicetype Microsoft.SharePoint.Administration.SPUserCodeService -servicename SPUserCodeV4.
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.
Users who are manually installing the Microsoft Dynamics CRM December 2012 Service Update or Microsoft Dynamics CRM 2011 Update Rollup 12 and are not going through Windows Update or any other automated deployment methods must also install the appropriate Microsoft Dynamics CRM for Outlook language pack update in order to see the process flow forms rendered correctly while Microsoft Dynamics CRM for Outlook is in offline mode.
If you create a service activity and sync it with Microsoft Dynamics CRM for Outlook, you will see it is available on your Outlook calendar. If you share your calendar with another user, they can see your service activity, but they are unable to open the record. When they click it, it acts like it is opening, but nothing opens. There is no workaround.
When you permanently delete an appointment that is tracked in Microsoft Dynamics CRM for Outlook, the appointment is not deleted in Microsoft Dynamics CRM. You need to also delete the item from Microsoft Dynamics CRM.
When you switch your primary organization, the Delete button is not disabled and the organization can be deleted. After deletion, both the organizations are deleted.
The workaround for this issue is to reconfigure which organization is the primary organization.
When you install a Japanese language pack on the server and do not install the language pack on Microsoft Dynamics CRM for Outlook, when you go offline, forms will not appear correctly.
To work around this issue, install the appropriate client language pack before you go offline.
If you uninstall Update Rollup 12, you must reconfigure Microsoft Dynamics CRM for Outlook in order to successfully use it again.
Changes to application pages that enable multiple-browser compatibility have the potential to cause unsupported JavaScript customizations to break. There is always a risk that an unsupported script will break during an upgrade or update. The possibility that unsupported scripts will stop working or cause an error is substantially higher with Microsoft Dynamics CRM December 2012 Service Update and Microsoft Dynamics CRM 2011 Update Rollup 12 than other releases. For information about what you can do, see the Microsoft Dynamics CRM Team blog post titled: Resolve Breaking Script Issues When Upgrading to the Next Release of Microsoft Dynamics CRM
Keyboard shortcuts, also known as access keys, may be different, depending on the web browser that you use. Although some keyboard shortcuts in Microsoft Dynamics CRM are permanent, such as CTRL + S (Save), other key sequences are different across different web browsers. For example, the keyboard shortcut to create a new post is different, depending on the web browser that you use.
New post sequence:
Internet Explorer: Alt + P
Firefox: Alt + Shift + P
The keyboard shortcut is different because the web browser’s unique key modifier to start an operation is different, depending on the web browser that you use. For more information, see Access Key.
Microsoft Dynamics CRM is available in some languages that the iPad does not have keyboard support for, such as Basque, Galician, Kazakh, and Slovenian. Please find the right keyboard characters from one of the oneline keyboard sites and use that to enter data into Microsoft Dynamics CRM.
The generic errors are 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.
When you export a solution, a folder is downloaded instead of a .zip file. To work around this, you need to disable the setting under Safari -> Preferences -> General to Open 'Safe' files for viewing. If you disable this, the solution ZIP file is exported as expected. If you import the file again, that should also work.
Alternative text (alt text) is not displayed for images that do not load on Safari or Chrome web browsers. With Chrome, the alt text appears only if the text can be displayed within the size of image area. Alt text is not supported with Safari. More information:
http://code.google.com/p/chromium/issues/detail?id=773
http://code.google.com/p/chromium/issues/detail?id=16734
For non- Internet Explorer browsers, the Get CRM for Outlook notification bar is displayed even though Microsoft Dynamics CRM for Outlook is installed. Ignore the Microsoft Dynamics CRM for Outlook notification or close the Microsoft Dynamics CRM for Outlook notification window.
Microsoft Lync presence icons will work only in Internet Explorer and will not work in other browsers.
When you use Firefox or Chrome, and click Close on the File menu in the main page, it does not close the Microsoft Dynamics CRM window. This does work in the records.
The window.close( ) action is not supported by Firefox and Chrome. To work around this issue, close the browser window or tab directly. More information: https://bugzilla.mozilla.org/show_bug.cgi?id=190515#c70
When you open a dialog directly by using the URL (instead of starting the dialog from the application), and then click the Finish button, the dialog window does not close. Avoid opening a dialog from the URL directly. Instead, start the dialog from inside the application or from a JavaScript code. This is a known Firefox issue. More information: https://bugzilla.mozilla.org/show_bug.cgi?id=190515#c70
When you select a record in a list, and then click the Copy a Link button, the link is not added to the clipboard. This feature is unavailable for all non-Internet Explorer browsers.
When a client computer and SharePoint Server are in different domains and the client computer requires you to provide credentials to authenticate with SharePoint, Chrome blocks the basic http authentication pop-up window for iFrames. More information: http://blog.chromium.org/2011/06/new-chromium-security-features-june.html
Therefore, you cannot authenticate with the Microsoft Dynamics CRM site, the document list doesn’t load, and a blank page is displayed.
To work around this issue:
Open a separate Chrome tab and then open the SharePoint site from the new tab. The credential dialog will appear and you can enter your credentials.
After the first step, open the Microsoft Dynamics CRM form again, browse to the Document Associated tab and open the SharePoint site.
After you apply this workaround, the site will display in the document list.
Error messages occur with Safari on a Mac with MacOffice 2011, when you click Download after a mail merge. Alternatively, error messages occur when you click the Microsoft Dynamics CRM logo on a mail merge document. This issue occurs because mail merge with Safari on a Mac exports Letters and Email Messages in .xml instead of .doc. Mail merge with Microsoft Dynamics CRM is not supported on the Mac and there is currently no known workaround.
When you open an XML file that is downloaded after exporting to Excel via a Dynamic worksheet, you may receive an error that says “"Dashcode cannot be opened because of a problem”. The reason for this is, by default all XML files open with the Dashcode app. To work around this issue:
Right-click the xml file.
Select GetInfo, point to Open, click Open With, and select Microsoft Excel.
You can also click Change all so that all xml files open in Excel.
When you click any action that opens a modal dialog box, a new dialog box is displayed that should be modal. (For example, in Settings, click Administration, click Users, and then click New.) Subsequently, you can go back to the previous web browser window where Users are listed. Chrome does not support modal dialog boxes.
Multiple clicks on the Lookup button cause multiple lookups to open when you use Firefox. This how Firefox handles modal dialogs. Avoid multiple clicks on the Lookup button.
When you use a Chrome web browser to open a dialog box or any other child window in Microsoft Dynamics CRM that in most browsers would be modal, such as the Set Personal Options window, and then try to move to some other part of Microsoft Dynamics CRM with the dialog box open, the pages do not display. Instead, a green, spinning circle is displayed. When this happens, you can click different areas in Microsoft Dynamics CRM, but you cannot browse until you close the dialog that is causing the issue.
Check whether you have a dialog or any child windows for Microsoft Dynamics CRM open. Close the dialog or window one at a time until you find the window that causes the issue.
The focus shifts to a parent window instead of the immediate parent window on iOS Safari. This happens only when a nested dialog closes itself after opening the second nested dialog.
Areas affected:
Marketing -> Marketing Lists -> Open Record -> Manage Members
Marketing -> Marketing List -> Select Record -> Add to Campaign
Marketing -> Marketing List -> Select Record -> Copy Marketing List
Sales -> Accounts -> Select an Account -> Run Workflow
When the previous scenarios are experienced, the focus shifts to the parent tab instead of the Dialog tab. To work around this issue, click the Dialog tab. More information:
https://discussions.apple.com/thread/3820143?start=0&tstart=0
You cannot tab out of the address (URL) bar when you use a Chrome web browser. This happens when you start a dialog and then select tab until the focus reaches the address bar in the window. This is a known issue with Chrome. More information:
Issue 114063: Can't tab past URL on popup window (http://code.google.com/p/chromium/issues/detail?id=114063)
Issue 94214: Can't use tab key to switch to page control when focus is in the picker address bar (http://code.google.com/p/chromium/issues/detail?id=94214)
Clicking the New button in the Lookup dialog box opens a new window, but it does not have the focus with Safari on Mac. To work around this issue, we recommend that you set the Safari preferences for opening a new page to always use tabs. To do this in the Safari web browser:
Click Preferences, click Tabs, and select Open Pages in Tabs.
You cannot perform any operation on a Help page or any other page when it is opened from any modal wizard, until the wizard is closed with Safari on Mac. To work around this issue, we recommend that you set the Safari preferences for opening a new page to always use tabs. To do this in the Safari web browser:
Click Preferences, click Tabs, and select Open Pages in Tabs.
On Safari, when you try to sign up and enter a Windows Live ID, then click to accept the terms, there is an image character (captcha) that must be entered. However, the Windows Live ID system does not accept the entered characters. This issue occurs when the time is set incorrectly on the client computer. For example, when the time zone is set to London, and then the time is increased by two hours ahead of the actual time. This does not appear to be an issue with different time zones that have the correct time. This behavior is by design.
When you use a Chrome or Safari web browser running on Windows with an Arabic language environment, and you click any dashboard, the Scrollbar unexpectedly appears on the right side of dashboard instead of the left side. This is a known issue with the Chrome web browser where the show scrollbar appears on the left if the direction attribute is set to rtl (right to left).
When you use Arabic as the language (base or language pack) and try to create a new personal view, the Edit Columns window does not load. This issue occurs only with Arabic in Safari and Chrome browsers. This is an issue with Safari and Chrome when you use Arabic as the language and there is currently no known workaround.
The Japanese file name is corrupted with Safari after the Download template for Import is saved. This is an issue with Safari interpreting encoded strings correctly. More information: http://stackoverflow.com/questions/93551/how-to-encode-the-filename-parameter-of-content-disposition-header-in-http
When you click New in the Article Templates area of Microsoft Dynamics CRM by using the Safari web browser on a Mac, the new article template form does not load and stops responding. This is an issue with Safari and there is no known workaround.
When you sign in to Microsoft Dynamics CRM Online and go to the Administration area of Settings by using Safari on a Mac, the following icons are not displayed:
For Office 365 subscriptions, the Billing icon does not display.
For Microsoft Dynamics CRM Online subscriptions, the Subscription Management icon does not display.
To access these areas, use a different browser that is supported. For more information, see Microsoft Dynamics CRM web application and mobile device software requirements.
When you click an action in the Business Closures list using Firefox, Chrome, or Safari web browsers, you may have to click the action and then click the action again to complete the operation. For example, you must click the Export to Excel icon two times for the Export Data to Excel dialog box to appear. This is expected behavior when you use any of these web browsers.
The workaround is to use the Tab key to move to the desired position and the Esc key to close the menu.
The View related records area does not appear in the correct location and the icons that are next to the From and To fields are underlined.
If there are pending email notifications and the Microsoft Dynamics CRM URL is not added to the pop-up blocker exception, then in Chrome, the Microsoft Dynamics CRM page loads and hangs. The workaround is to add the Microsoft Dynamics CRM site to the exception list.
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.
© 2013 Microsoft Corporation. All rights reserved.
Microsoft, Excel, Internet Explorer, Microsoft Dynamics, Outlook, SharePoint, 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.
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.