Gareth Prisk

In CRM 2013, an issue has been noted when attempting to search the results of a Marketing List using the associated record view.

The Marketing List is dynamic and the query includes an associated record that has an ampersand (&) in the name field (i.e. Account Name). The query will execute and return the correct members for the Marketing List. However, when toggling to the associated view to search within the list of members, a non-verbose error occurs. This also occurs if a lookup on the returned entity type (i.e. Contact) includes a value with an ampersand in the name.

This issue was discovered in a client's environment (online UR2), and replicated in an internal, non-customized environment (UR1).

To replicate in non-customized environment:

1. Install the CRM sample data
2. Create a new dynamic marketing list, targeted at Contact
3. In the query, select 'City Power & Light (sample)' as the Company Name value
4. Alternatively, select 'City Power & Light (sample)' as the Account value for a related Company Name (Account) record
5. Attempt to search within the associated view of Marketing List Members (Contact associated view)

The current workaround is as follows:

1. Update the associated record name to exclude the ampersand
2. Update the query; specifically, you have to unselect and then reselect the same value ** (see below) **
3. Save the Marketing List and attempt to search the Marketing List Members

** Marketing List Query Quirks **

- The name used when the query was created maintains the ampersand until explicitly changed, and does not appear to update when the name is updated. In other words, the query also has to be manually updated to resolve this issue, and not just the name of the associated record.
- Once the query value has been set with the associated record (which excludes the ampersand), the actual associated record name can be reverted back to include the ampersand and the Marketing List Members are still searchable