...
Batch Donation Entry Permission Set
ProntoGiving Version 2: Batch Donation Entry Permission Set
Profile Permissions
Object | Object Permission | Field Permission | Read Access | Edit Access |
Batch Donation Entry | Read, Create, Edit, View All | All | TRUE | TRUE |
BDE Item | Read, Create, Edit, View All | All | TRUE | TRUE |
BDE Item Defaults | Read, Create, Edit, View All | All | TRUE | TRUE |
BDE Templates | Read, Create, Edit, View All | All | TRUE | TRUE |
...
Object | Object Permission | Field Permission | Read Access | Edit Access |
Accounts | Read, Create, Edit, View All | Billing Address Receipt Recipient (PPlus) | TRUE | TRUE |
Campaigns | Read, View All | |||
Contacts | Read, Create, Edit, View All |
| TRUE | TRUE |
Gateways | Read | |||
GAU Allocations | Read, Create | Amount Percent | TRUE | TRUE |
General Accounting Units | Read | |||
Opportunities | Read, Create | Lead Source Receipt Action (PPlus) Receipt Template (PPlus) | TRUE | TRUE |
Payment Sources | Read, Create | All fields | TRUE | TRUE |
Payment Transactions | Read, Create | All fields | TRUE | TRUE |
Receipt Template (PPlus) | Read | All fields | ||
Recurring Donations | Read, Create | Always use last day of month
| TRUE | TRUE |
BDE Matching Criteria
Setup BDE Matching Criteria
Note: This step is done automatically after installation. However, if the user needs to add more fields to be mapped, follow the steps outlined below.
Add Mapping
Go to ProntoGiving Settings > Batch Donation Entry > BDE Matching Criteria
The user can specify Matching Rules for Primary Contact, Soft Credit Contact, Primary Account, Soft Credit Account, Campaign and Primary Campaign on BDE Item fields, based on the specified matching fields and Priority on the setting
Submitted BDE Items will search for matching records or create new record if not found
When Match is found, action is taken based on the Matching Rules
When Match is not found, create new record and populate to appropriate fields. For example a user might want to map the Contact Object with its BDE Item matching fields.
Object | Matching fields | Priority |
Contact | FirstName;LastName;Email | 1 |
BDE Item fields FirstName, LastName, Email was mapped to the Contact Object as the highest priority 1. Additionally, these are the Matching fields that should be mapped accordingly, although some fields may be omitted depending on the user requirements.
BDE Matching Criteria
Name | ASPHPPADDON__Object__c | ASPHPPADDON__Matching_Fields__c | ASPHPPADDON__Priority__c |
Contact | Contact | FirstName;LastName;Email | 1 |
Account | Account | Name;ASPHPP__PPEmail__c | 1 |
Account2 | Account | Name | 2 |
Campaign | Campaign | Name | 1 |
Expected Outcome
Assumption:
The user has typed the First Name, Last Name, Email on the BDE Item record details (before Process Batch). Clicking Process Batch button submits the record, then creates an appropriate Opportunity and will populate the Contact record based on the Matching Criteria fields being setup on the settings.
If there is a match, it will populate the Contact record on the created Opportunity.
If there is no match, it will create a new Contact record and populate on the Opportunity.
BDE Data Load in BDE Item Object
Data Loader is used to insert or update donations to Salesforce; one-off or recurring donations in one batch. The following instructions will walk you through the minimum required fields for each type.
Minimum required fields for One-Off Donation
ASPHPPADDON__Primary_Account__c/ASPHPPADDON__Primary_Contact__c
ASPHPPADDON__Date__c
ASPHPPADDON__Amount__c
ASPHPPADDON__Opportunity_Stage__c
ASPHPPADDON__Frequency__c (One-Off)
ASPHPPADDON__Donation_Type__c
Minimum required fields for Recurring Donation
ASPHPPADDON__Primary_Account__c/ASPHPPADDON__Primary_Contact__c
ASPHPPADDON__Amount__c
ASPHPPADDON__Date__c
ASPHPPADDON__Frequency__c (Weekly, Monthly, Yearly)
Note: If any field that you want to add, then that field doesn’t exist, you can create that as custom field and add the mapping in the BDE Item Record Mapping.
.
Minimum required fields for updating
Recurring Donations. This a sample CSV filefor updating recurring donation.
a. ASPHPPADDON__Recurring_Donation__c
b. It could be any Recurring Donation fields specified in the Item Record Mapping.
c. Note: For Recurring Donation required fields that are not mapped or setup inBDE Item Record Mapping, make sure to put default values in the following fields:
i. Date Established → Current Date
ii. npe03_Contactc or npe03Organization_c should not be empty
iii. npe03_Installment_Period_c → Monthly
iv. npe03_Installments_c → 12
v. npe03_Next_Payment_Date_c → Current Date
vi. npe03_Open_Ended_Status_c → Open
vii. npe03_Schedule_Type_c → Multiple By
. d. Note: If any field that you want to update, then that field doesn’t exist, you can create that as custom field and add the mapping in the BDE Item Record Mapping.
Minimum required fields for donations via
Credit Card (aside from one-off or recurring donations).
a. ASPHPPADDON__Credit_Card_Name__c
b. ASPHPPADDON__Credit_Card_Number__c
c. ASPHPPADDON__Credit_Card_Expiry_Year__c
d. ASPHPPADDON__Credit_Card_Type__c
e. ASPHPPADDON__Credit_Card_Expiry_Month__c
f. ASPHPPADDON__CCV__c
.
Minimum required fields for donations via
Bank Account (aside from one-off or recurring donations).
a. ASPHPPADDON__Bank_Account_Name__c
b. ASPHPPADDON__Bank_Account_Number__c
c. ASPHPPADDON__Bank_Account_BSB__c
.
Minimum required fields for donations with
1 GAU Allocation (aside from one-off or recurring donations).
a. ASPHPPADDON__GAU_1_Amount__c
b. ASPHPPADDON__GAU_1_ID__c
c. ASPHPPADDON__GAU_1_Name__c
.
Minimum required fields for Donation with Multiple
GAU Allocations
. a. ASPHPPADDON__GAU_Allocations__c
. b. ASPHPPADDON__New_GAU_Allocation_on_Recurring_Donation__c
This is the format to be inserted in the GAU Allocations field.
[
{
"gauID" : "a0w0o00000QefXjAAJ",
"allocationAmount" : 15
}, {
"gauID" : "a0w0o00000QeYXtAAN",
"allocationAmount" : 20
}, {
"gauID" : "a0w0o00000QeYXtAFGH",
"allocationAmount" : 25
}
]
Note: You can add as many GAU Allocations as you want as long as it meets the criteria.
Import Data via Data Loader
Open the
Data Loader.
Click
Insert.
Enter your Salesforce username and password. To log in, click
Log in.
Choose the
ASPHPPADDON__BDE_Item__c object. If this object name is not displayed on the default list, select Show all objects to see the complete list of the objects that you can access.
To select your CSV file, click
Browse.
Click
Next. After the object and CSV file are initialized, click OK.
Define how the columns in your CSV file map to Salesforce fields. To select an existing field mapping, click
Choose an Existing Map. To create or modify a map, click Create or Edit a Map.
For each operation, the Data Loader generates two unique CSV log files, one file name starts with “success”, and the other starts with “error”. Click
Browse to specify the directory for these files.
To complete the operation, click
Finish, and then click Yes to confirm. As the operation proceeds, a progress information window reports the status of the data movement.
10. To view your success or error files, click View Successes or View Errors. To close the wizard, click OK.
11. To verify that the records are saved to Salesforce successfully, go to the BDE Items tab. Create a list view that will display all the records created today to see your imported records.
Map BDE Item fields to any record fields
Please follow this link.
Process BDE Items
To process the records that you imported, please follow this link.