Constant Generation of Aliases

[[email protected]]

Hello:

We are encountering an issue where aliases are being consistently generated every time a transaction is processed in that name, although the name and contact info is often identical or nearly identical. If the contact data was different, shouldn't a temporary contact be created rather than an alias?

I've allowed C&P access on our instance (Org. ID is 00Di0000000iX2P) and include this link of the contact Virginia Mills as an example.

https://na15.salesforce.com/003i000000Xdbjh

From test donations and other transactions, more than 20 aliases have been automatically created, and, with no notifications on the creation of these, they are cluttering our C&P work area and we'd like to know how to fix this/adjust the settings.

Thank you!

[CnP.Support]

Good day!

No - actually the behavior is exactly as what you are seeing.

If a contact is matched and found based on the set criterion then the contact is attached to the transaction. If any other information is NEW, meaning not the same as the one in the contact record then we create an alias for that person. This is to make sure that any change of data is not lost, meaning if their address has changed the data is not lost and is saved.

The only condition used for matching the contact is what you choose in the Account > Contact area. If those fields match then the contact is found and the behavior is what you see.

[[email protected]]

I understand - Is there any way to set up email notifications when an alias is generated?

My issue is that it doesn't seem to be functioning the way that you have detailed as some contacts have multiple aliases with identical information. Shouldn't the system have picked up an existing alias if the contact info was the same?

A good example is the contact "Virginia Mills" where Aliases 30 through 34 are exactly the same.

[CnP.Support]

Good day!

It should not create exact duplicates - it has to find one thing that is different.

Do we have access to your account? we can review it and figure out what is going on.

[[email protected]]

Yes, access is granted - Thanks!

[[email protected]]

Did you have a chance to take a look at this? Please let us know what you find. Thanks!

[CnP.Support]

Good day!

Yes- we have identified the problem and it has to do with an "undocumented feature" (aka bug) that was fixed as part of the 8.3 release.

The problem was the zip code was being mapped into the state field by mistake.

Sorry for the inconvenience.

If your Salesforce instance has been updated to the Spring 2014 version then you can upgrade to the latest release. The release posted in the beta site is the final version but we are not posting it to AppExchange since those that are not yet upgraded to the latest Salesforce will not be able to upgrade.

Let me know if we can be of any further assistance.

[CnP.Support]

Good day!

The issue you had identified has been fixed in the new released package.

Version 8.3042 is currently available via the About C&P App tab: http://forums.clickandpledge.com/con...e-Applications

Please let us know if you need help with the upgrade. We can upgrade your instance if you grant us login access.

How to grant access: http://forums.clickandpledge.com/showthread.php?t=1065
Please make sure to post your organization name & the Salesforce Organization ID so we know how to locate your instance.