Mapping Address fields to opportunity record

[katieVNY]

Is there a way to map the billing address for the credit card used for the opportunity to the opportunity record? It is mapped and matched to the contact, but I would like it to also be in the opportunity record.

I found this article about custom mapping, but address is not a custom question. I'm not sure if it's not working because I didn't do it correctly or if it's not possible.

https://support.clickandpledge.com/s...custom-mapping

Thanks

[CnP.LiveSupport.AB]

No, there is no way to map the address to the Opportunity record.

You control the mapping for new Contacts under C&P Settings > Contacts & Accounts, but the app was designed to match to existing Contacts in Salesforce, and create aliases when temporary contacts are matched to Contacts.

Was there a reason that the Contact's mailing address is not working for your needs? Or are you just wanting to respond with the same address used for the latest transaction?

[katieVNY]

Our instance is set up a little different than most. We are not using the household model, but the bucket/individual model. The mailing address fields are a contact's home address and the other address fields are their business address (if we have it). Sometimes we have a contact who under the business organization, for example, ABC Company, and we have both a home and business address for this person. With semi automatic matching in place, if the contact from ABC Company makes a personal donation where the home (mailing) address matches the billing address for the donation, it is processed. However, the donation is processed as a donation for the organization and not the individual. We are trying to get around this with a process builder to change the donation organization and name, which works, but sometimes the contact is actually making a donation on behalf of the company. In that case, the billing address doesn't match the home (mailing) address and goes into temporary contacts. In this case we are trying to prevent the process builder from changing the record. We thought if we could get the billing address into the opportunity, that could be a step in the process builder and use it to decide if the donation record should be changed.

[CnP.LiveSupport.AB]

OK - your account model is really irrelevant.

The app has no way of knowing if someone is making a personal donation or a business donation. If people always used their work email when they were making a business donation, and always used their personal email when they were making a personal donation, there would be nearly as many problems.

To keep your amount of work to manage donations as simple as possible- you need to reduce how often it is a problem. Start by making it as obvious as possible to the donor about how they should specify whether the donation is business or personal. Generally, I would suggest having one form for business donations, and another for personal donations. Then make sure the one for the business donations specifically labels the email field as "Work Email"

If you can do that much, then you can set your C&P Settings to match only on first name, last name, and personal email. Then when a donation comes in using a work email, it fails the match and goes to Temporary Contacts. Then you'll have the chance to match the donation to the business account when you process the temporary contact

BUT YOU CAN'T STOP THERE-
Each time you manually match a temporary Contact, PaaS creates an Alias record so that the next time someone uses that same first name, last name, email combination - PaaS can review the Aliases to see if there is a match.

So you can either:

• Make it a practice when you process a Temporary Contact for a business donation to ALWAYS remove the Alias record that gets created - so the next time they use their work email, it will be caught in Temporary Contacts again.

In which case your C&P Settings > Contacts & Account > Match Fields should look like this:

• OR you can remove the C&P Alias from the Match Fields - so that PaaS only attempts to match on the Contacts Email, Alternate, and Personal - that way even if an alias is created, it will still fail the match and go to Temporary Contacts.

Although this way, you don't have to make sure you delete the Alias when someone uses their work email, you are likely to end up having to process more Temporary Contacts just because you're not matching against Alias values for email anymore.

(And this is all assuming you are not trying to match any of the address fields, because that would be a total mess)