CRM 3.0 Service Pack 14 Release Notes

For information about all of the new features released in CRM 3.0, see the CRM 3.0 New Features page. For information about new features from CRM 3.0 Service Packs, including Services Packs prior to this one, see the Service Pack New Features chapter in the CRM 3.0 New Features Guide.

Improved Matching in the Incremental Constituent Duplicate Search Process (505263)

With this enhancement, we have improved the "Incremental Constituent Duplicate Search Process" located in Duplicates which you access from Constituents. Previously, two constituents with addresses that were almost identical were sometimes not seen as duplicates by the process. The issue occurred when one address included a five-character postal code and the other included the ZIP+4 postal code with all other address information matching exactly.

To correct this issue, we added a new field to the "Custom settings" tab of the "Edit incremental duplicate constituent search process" screen. The Number of characters to use for matching field allows you to specify how many characters of the postal code to compare for the match criteria. The default for the new field is 12 but you can change it to suit the needs of your organization. If the value of this field is set to five, for example, the five-character postal code and the ZIP+4 postal code will now be seen as exact matches since only the first five characters are compared. A higher number represents a more stringent match criteria.

PhoneFinder and Do Not Mail Addresses (502441)

The PhoneFinder process in the Data Tune-up section of Administration now has an Include addresses marked as Do Not Mail checkbox on the "Edit PhoneFinder submit process" screen. This gives you the flexibility to choose whether or not to include those records. If you have many constituents who do not receive mail from your organization, you may still want to use addresses that are marked as "Do not mail" to help locate new or updated phone numbers for those constituents. However, if you use "Do not mail" to also indicate invalid or out-of-date addresses, you may not want to use those in the PhoneFinder process.

By default, this checkbox is marked to match existing behavior. In order to omit these addresses from the PhoneFinder process, you must edit existing PhoneFinder submit processes and unmark the Include addresses marked as Do Not Mail checkbox.

Sort Order for Reciprocal Relationship Types (481896)

We have added a new sort order for use when editing the relationship types between two constituents. Previously, when a constituent had a relationship with a commonly used relationship pair (such as employee and employer) and you tried to edit the relationship, the “Edit relationship” screen could take a long time to load in databases with extremely large numbers of relationships between constituents, as the program was trying to calculate which relationship pairs were the most common between your constituents.

To improve performance, we have added the ability to change the functionality so that the sort order for relationships in those relationship fields is alphabetical instead of being sorted with the most commonly used relationship pair at the top of the list. However, when you change the sort order to alphabetical instead of "Most frequently used pairing," the reciprocal relationship will not default automatically to the reciprocal relationship field. The new Sort method for reciprocal relationships setting is on the Relationship Types tab of the Relationship Settings page which you access from the Relationship settings configuration task in Constituents.

Note: After you upgrade, the new setting will be set to “Most frequently used pairing” to match the current behavior. In order to see the performance improvements, you must change this setting to “Alphabetical” instead.