Categorized in: 

MEC Weekly Digest | September 20, 2019

September MEC Meeting

Individual vs. Standard Contact Duplicates

  • Issue: Duplicate management for individual and standard contacts is handled differently, and we want to be sure that the MEC group understands the difference between the processes. Note: this is a general description; more information will be provided soon as the COE continues its work on duplicates with UIS.
    • Individual contacts: Individual contacts in Salesforce are those generated by a source System, such as Advance. We've found that many duplicates on individual contacts are likely the result of matching rules in MDM that are allowing the duplicates to pass to Salesforce rather than being recognized as one contact.
      • The COE is working on a fix with UIS that will address duplicates for individual contacts. More information will be available soon.
    • Standard Contacts: Standard contacts in Salesforce are those created by MECs OR created through Cvent registrations. 
      • Standard contacts are generally addressed through an ongoing nightly merge job, so long as the email address on the standard contact matches one of the email addresses on an existing individual contact.
      • If a standard contact email address does not match any of the email addresses for an individual contact, then MECs should submit a DCR by adding it to the DCR spreadsheet (see Chatter for link).

New Wiki: Emailing Donors with eComm

  • Issue: Kate O'Connell from the Advancement Reporting team (and formerly with eComm) reached out to let us know that her team is often fielding requests to obtain email addresses for donors.
  • Impact: The Advancement Reporting team is having numerous conversations with communicators that demonstrate a lack of knowledge about using eComm tools for these types of communications. 
  • Solution: Caroline Kelly and Melanie Jones put together a wiki about the process for emailing donors as a resource for eComm and Advancement Reporting.

Cvent & TouchNet

  • Issue: There is some confusion about the role of TouchNet in relation to eComm.
  • eComm Impact: TouchNet is NOT designed to be a Cvent replacement for eComm users and will not integrate with Salesforce. It WILL streamline the credit card process in Cvent so that money collected will appear in speedtypes faster through an automated nightly process rather than requiring the Treasurer's Office to manually process transactions. We are working with the Treasurer's Office (at their request) on implementing TouchNet in the eComm environment.
  • Timeline: We will be rolling out the TouchNet integration with Cvent AFTER the CU Marketplace TouchNet rollout is complete. We do not have a target date yet, since we are still having conversations with both Cvent and TouchNet about the integration process, impact to Cvent users, and in particular the impacts of merchant account changes associated with the TouchNet product and how that will affect active events. We've had two calls so far, but TouchNet and Cvent have a lot to work out on their end, so we don't have any updates at this time but will keep you in the loop as things continue to develop.

Ongoing TaskRay Tasks

  • MECs can view ongoing progress on TaskRay tasks in Salesforce.
  • The System team is working on a TaskRay dashboard that will better demonstrate ongoing progress. More information will be available soon.