MSCRM v4.0's Automatic Mapping Feature

Ruston Eads — Wed, 26 Nov 2008 16:05:59 -0500

Microsoft CRM v4.0 has a nice Automatic Mapping feature that can be used when importing data using the Data Management Import feature. Note, Dear Reader, that Data Maps are not needed when using the Automatic Mapping feature. That's the nice thing about Automatic Mapping; just as the name suggests, CRM maps the data fields for you as long as the field titles in your source data match the CRM Display names in the entity in which you're importing.

Just as with Data Imports in MSCRM v3.0, you'll need your source data in a .csv or .txt format. There are 2 main items to consider when using Automatic Mapping, which are:

1) As stated above, ensure that the source data column headings are identical to those in the CRM entity's attribute display name. Note that the Attribute-level display name is what is needed and not (necessarily) the form-level display name, as it can be altered to display a different value than what is shown at the attribute level. Also make sure the case is the same, as the Automatic Mapping feature is case-sensitive.

2) View the List of attributes in the entity in question and ensure that all attribute Display names are unique. CRM itself allows duplicate Display names, but the Automatic Mapping/Import will not. If you have 2 or more that share a Display name, simply edit the Display name(s), save and publish, and then update your source data to reflect the changes in CRM.

You are now ready to import your records. You'll know if Automatic Mapping works or not after you upload your source file and select the CRM entity to import. An Automatic Mapping link will display in the Data Map field if all goes well. (as shown below) If not, the Data Map field stays blank and expects you to use an existing Data Map. Tips to correct are to cycle back through steps 1 & 2 above and ensure the source column headings are exactly the same as they appear in CRM. Remember, it's case-sensitive.

MSCRM Campaign Activities Will Not Distribute and Become Stuck "In Progress"

Ruston Eads — Fri, 31 Oct 2008 16:04:06 -0400

Issue: When distributing a Campaign Activity for a Marketing List (or Lists) that total 5000 records or more, the Activity becomes stuck in an "In Progress" state. The activities aren't created, but they don't fail either. They're just...stuck.

Cause: The high number of Contact, Account, and/or Lead records. 5000 is the number to use, though it's not exact. It is a good rule of thumb though. Note that is also the total amount no matter the type. (Contact, Account, or Lead)

Solution:
1. Click Start, click Run, type regedit in the Open box, and then click OK
2. Back-up your Registry by saving it to a secure location
3. Locate and then select the following registry subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\MSCRM
4. On the Edit menu, point to New, and then click DWORD Value
5. Type TurnOffFetchThrottling, and then press ENTER
6. Right-click TurnOffFetchThrottling, and then click Modify
7. Type a number other than 0 in the Value data box, and then click OK
8. Restart the CRM machine
9. Open the Campaign Activity in question and redistribute the Campaign Activity and the individual activities should be created.

Extremely Important Note: This can potentially cause performance issues. If it does, undo the steps above (or simply change the TurnOffFetchThrottling value to 0) and restart the CRM server again. Then make sure you're not distributing Campaign Activities for Marketing Lists of 5000 records or more. Instead, accomplish the same task by using multiple Marketing Lists made up of a lesser number of records.

Customer Effective Blog

MSCRM v4.0's Automatic Mapping Feature

MSCRM Campaign Activities Will Not Distribute and Become Stuck "In Progress"