Non Profit Starter Pack (NPSP)
Inserts Contacts, which automatically creates Accounts. An opportunity is created for each fund designation with a donation; meaning if it's one fund in a donation, it's one opportunity. If it's 3 funds in one donation, there will be 3 opportunities. Need to ensure you've run the custom package above, which will store the RaiseDoors Donor.Id field in SF.
Standard
Inserts Accounts, which hold the various opportunities. After creating opportunities, we then create a one-off Contact, that is related to the Account.
Unfortunately, the opportunities are only related to the account. This is because out of the box with SF Standard, there is no relationship between Opportunities and Contacts. So we store the opportunities against the Account.
Setup Instructions
Access
To get started, you'll need to have these pieces of information. Username, password and security token.
This is very helpful information to understand the relationship of security between RaiseDonors and Salesforce
Your username is the email address you use to log into your salesforce installation.
Your password is the password you use to log into your salesforce installation.
To locate your security token, log into your salesforce installation,
2. Select Personal
3. Sixth option is "Reset My Security Token"
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1a000000VPUe
Note: If you are installing into a sandbox organization you must replace the initial portion of the URL with http://test.salesforce.com
RaiseDonors has complete flexibility when it comes to mapping the data from RaiseDonors (Donor & Donation) and how that maps to objects in Salesforce (Opportunity, Account, Contact). To get started, you need to send the following email to help@raisedonors.com
1a) If you have NPSP,
We need to know the field when creating an opportunity, and we need to relate it to a contact, there is a custom field for the primary_contact_keys.
2) Have you run the Package listed above? After doing so, we need to acquire the Field Name for the object "Contacts" and the field "RaiseDonors Donor ID"
3) Data mapping. We have the following objects in RaiseDonors listed below. These can be mapped to the objects in SalesForce. You need to provide a mapping list as follows,
Example {SalesforceObject.SalesforceField - RaiseDonorsObject.RaiseDonors.Field}
Opportunity.Name - Donor.FName Donor.LName Donation
Opportunity.Amount - Donation.Amount
Contact.Phone - Donor.Phone
Contact.Email - Donor.Email
Contact.Name - Donor.FName Donor.LName
Contact.MailingAddress - Donor.BillingAddress1 Donor.BillingCity Donor.BillingState
RaiseDonor Objects & Fields
DONOR
Id
FName
LName
Email
Phone
Billing Address.Address1/city/state/zip/country
Shipping Address.Address1/city/state/zip/country
DateCreated
LastModified
LastModifiedBy
LastIPAccess
NewsletterOptIn
Notes
Donation
Id
Amount (Total)
AuthorizationNumber
EmailReceiptCopy
Last4ofCC
MotivationCode
SourceCode
Status
Notes
DateCreated
LastModified
LastModifiedBy
LastIPAddress
CardBrand
PaymentMethod
CampaignId
DonorId
GatewayName
GatewayTransDetails
TransactionId
TestMode
Name
Email
Phone
RecurringDonationProfilesId
Comment
CCExpiry
DonationFundAllocations
Amount
FundName
Donation.Campaign
Id
Title
Url
MotivationCode
SourceCode
MinDonationAmount
DateCreated
LastModified
LastModifiedBy
PayFreqType
ProductCode
DownloadUrl
QuantityIncluded
FairMarketValue
IsDonation
GoalAmount
PageContent
PageContentTitle
PageContentImage
PageContentButtonText
PageContentVideo
PageContentLogo
ProductCodeName
PublicTitle
Log into your Salesforce installation. Click on Setup. On the left nav, under BUILD, click Customize. Find the object you are searching for (ex: Contacts), and click on Fields. The table on the right now lists all the fields for the selected object. Careful, there are two tables on the right hand side. It usually easiest to use the search feature of your web browser to locate the field.
Standard Fields
The third column, "Field Name" is the programatic name we are looking for. The value is the entire word in the 3 column.
Custom Fields and Relationships (usually below Standard Fields)
The third column, "API Name" is the programatic name we are looking for. The value is the entire word in the 3 column, which can contain odd things like "__c" and "npsp__".
If the fields Data Type is "Lookup", it's a bit trickier. You need to take the fieldName and add an "Id" to the end. Example, look at our sandbox, we need to use the "Primary Campaign Source". The true FieldName in this case would be "CampaignId".
And the value to use in this instance is NOT the textual representation of the Campaign. In this case, you'd navigate to the specific campaign you want to use in this instance (to be associated with this donation), and copy the unique ID of the Campaign. That ID is then associated with the "CampaignId".
We have several scenarios to be configured.
1) Standard Donation. This is what you'd expect, send the donation and donor information into Salesforce.
2) Setting up of a recurring donation. Are there specific business rules that are only applicable when setting up a new recurring donation?
3) Instance of a recurring donation. Are there specific business rules that are only applicable to a recurring donation instance (future)?
4) Ending/Stopping a recurring donation profile. When a profile is terminated, are there any updates you'd like to be applied to the donor record in SF?
5) Modifying a recurring donation profile. When a profile is edited, are there any updates you'd like to be applied to the donor record in SF?
6) Refunding or Voiding a donation. When a refund is initiated thru RaiseDonors, we have two choices in how to update Salesforce.
- Keep the original opportunity and perform various updates to the data.
- Create a new, negative amount entry in Salesforce.
When keeping the original entry, how would you like the integration to update the opportunity in SF? Perhaps set the Status of the Opportunity to "closed"?
When creating a new negative opportunity, you'll need to provide the full mapping of information just like you did for "Standard Donation".
How does RaiseDonors match donations to existing records in SalesForce?
It is completely customizable and up to you!
With each mapping you provided in the "Standard Donation", you can assign if it is should be included in the matching logic. You can have as many fields as you wish or as few fields as you wish.
In each field, you can specify...
QUALITY - how specific should we be?
Exact - must be an exact match (case insensitive)
First - match the first few letters
Last - match the last few letters
None - do not match at all
NUMCHARS - for the strings, how many characters to compare? Only applicable for First/Last Quality types.
Can RaiseDonors send ISO codes to SalesForce for state and Countries?
Yes, in the mapping we can provide the following configurations.
For State, RaiseDonors can send full-text or ISO2 (example: Texas or TX)
For Country, RaiseDonors can send full-text, ISO2, ISO3 (example: United States of America, US, USA)
What if I have multiple campaign Id's configured in the RaiseDonors configuration?
For example, if I have a campaign ID for a one time donation but have a different campaign Id configured for the recurring setup. If both are sent to SalesForce, it will error out. So how does RaiseDonors know which one to use?
We have a solution in place for this! We can specify a flag on the 'master' field to use. In the example above, we can specify which campaign Id would be given precedence when one or more are provided. We have a token 'WhenDuplicateEntryUseThisOne' that handles this.
Comments
0 comments
Please sign in to leave a comment.