Month: February 2014
When accessing Microsoft Dynamics CRM records within the Microsoft Dynamics CRM for Microsoft Office Outlook client, a user may experience intermittent prompts for credentials.
The issue is due to an Internet Explorer problem which caused session cookies to be cleared out and require users to log in again.
The Internet Explorer team has addressed this issue as a hotfix which can be found in KB 2926827:
This issue affects Internet Explorer 10 and 11.
You can configure a quick create form so that users are presented with fewer fields to complete when they first create a record. Doing this helps users to create records more quickly, by leaving some information to be completed later. A quick create form can only contain a single tab that contains three columns with one single-column section in each column. The three sections can only contain fields and spacers (or be left empty).
A user can access a quick create form to create a new record in four ways:
• Click the Create (+) button on the navigation bar, then click the entity that you want to create a record for, as shown in the “Create Records From the Navigation Bar” figure. This “global create” feature is always available so that a user can create a record quickly and then return to his or her work. For example, a user can create a Case to deal with an incoming support issue, and then return to an Opportunity record that he or she is working with.
• At the bottom of a lookup field drop-down list, click the New button to create a new record instead of selecting an existing record. When the record is saved, the new record link will already be completed in the lookup field.
• In a sub-grid, click New (+), click the lookup icon, and then click New instead of selecting an existing record.
• In an Associated View, click Add New <Entity>.
To create a quick create form, follow these steps.
1. Navigate to Settings > Solutions, and then double-click to open the Solution that you want to customize.
2. Expand the entity for which a quick create form is required.
3. Click Forms.
4. Click New.
5. Select Quick Create Form.
6. Modify the quick create form by using the form editor in the way you would configure any other form. Make sure that you remain within the limitations of a quick create form.
7. On the ribbon, click Save and Close.
8. In the solution, click the entity.
9. In the Data Services section, check the box next to Allow quick create.
10. On the ribbon, click Save.
11. On the ribbon, click Publish.
Note: An entity will not use quick create forms unless you also enable the entity property Allow quick create. You can enable the property first, or create the form first. However, you must perform both tasks and the entity must be published before the users can create records using the quick create form. You might have to refresh the Microsoft Dynamics CRM page in the browser for the entity to be displayed in the global create area.
A Bing Map can be added to a form to display the location of the address of the record. Bing Maps can only be added to the forms of system entities that have a composite address field. The system entities that can display Bing Maps on forms, include the following:
When you add a Bing Map component, you must select the address field that will be displayed, for example Address 1 for an Account, or the Ship-To Address for an Order. The Bing Maps feature uses the API of the Bing Maps service to fetch location and mapping information to display in the form.
For customers who use Microsoft Dynamics CRM Online, a connection to this service is included in the User Subscription License (USL) and no configuration is required to use the feature.
For on-premises deployments, you must sign in to the Bing Maps Portal and create an API key. Depending on the size of the deployment, the type of organization that you work for (private sector, education, or government, for example), and whether you have other license agreements with Microsoft that include your use of the service, there might be an additional cost for this service.
Bing Maps Portal URL – http://go.microsoft.com/fwlink/?LinkID=187187
To enable this feature in an on-premises deployment, you must follow these steps.
1. Obtain a Bing Maps API key from the Bing Maps Portal.
2. Open Microsoft Dynamics CRM.
3. In the navigation bar, click Microsoft Dynamics CRM > Settings > Administration.
4. Click System Settings.
5. On the General tab, scroll to the Enable Bing Maps section.
6. In the Show Bing Maps on forms section, click Yes.
7. In the Please enter Bing Maps key field, enter your Bing Maps API key.
8. Click OK.
Bing Maps can now be added to forms for the enabled system entities.
Microsoft Dynamics CRM 2013 introduces a new predefined field type for some system entities that is known as a composite field. You cannot modify the behavior of a composite field or add a new composite field. However, you can select whether to use a composite field in your forms or views.
A composite field concatenates the values of multiple text fields together as one text field in the database. You can add a composite field to a form as you would add any other field. The composite field is displayed on the form as a single control that shows the primary fields in a flyout when it is clicked. Many composite fields are already included on the forms for their entities.
For example, the Contact Full Name field appears on a form as a single field. However, when the user clicks the field, a flyout appears next to the field that asks the user for the First Name, Middle Name and Last Name fields separately. When these fields are completed, the user clicks Done and the completed field is displayed as a single control again. In another example, the Account Address 1 field can be displayed as a single field that will ask the user for seven separate fields from Street 1 through Country/Region when the user clicks the Address 1 field.
This approach uses much less space on a form than separate fields and can be easier to read as one item. You can add composite fields to views and forms.
If one or more of the fields that are used in a composite field is set to a field requirement level of Business Required, the composite field will be displayed as required on a record form (using a red asterisk to remind the user). This forces the user to provide a value for the composite field, and when the user clicks the composite field, the flyout will indicate the individual fields that are required.
Composite address fields always have a name with the suffix “_composite”, for example address1_composite or shipto_composite. The fullname composite field on Contact, Lead and User has no suffix in the field name.
Update Rollup 1 for Microsoft Dynamics CRM 2013 is available. This article describes the hotfixes and updates that are included in this update rollup.
This rollup is available for all languages that are supported by Microsoft Dynamics CRM 2013.
Note Update Rollup 1 contains stability and memory-consumption improvements.
Build number and file names for this update rollup
|Rollup package||Build number||File name (32-bit editions)||File name (64-bit editions)|
|Microsoft Dynamics CRM 2013 Server||6.0.0001.0061||Not applicable||CRM2013-Server-KB2891271-LangID-amd64.exe|
|Microsoft Dynamics CRM 2013 for Microsoft Office Outlook||6.0.0001.0061||CRM2013-Client-KB2891271-ENU-LangID-i386.exe||CRM2013-Client-KB2891271-ENU-LangID-amd64.exe|
|Microsoft Dynamics CRM 2013 E-mail Router||6.0.0001.0061||CRM2013-Router-KB2891271-LangID-i386.exe||CRM2013-Router-KB2891271-LangID-amd64.exe|
|Microsoft Dynamics CRM 2013 Language Pack||6.0.0001.0061||CRM2013-Mui-KB2891271-LangID-i386.exe||CRM2013-Mui-KB2891271-LangID-amd64.exe|
|Microsoft Dynamics CRM 2013 Reporting Extensions||6.0.0001.0061||Not applicable||CRM2013-Srs-KB2891271-LangID-amd64.exe|
Update rollup information
Update Rollup 1 for Microsoft Dynamics CRM 2013 is available for on-premises customers.
The following file is available for download from the Microsoft Download Center: