ProntoGiving - additional configuration
On this page
Hide Unused/Deprecated Components
Navigate to Setup | Users | Choose Profile. (Note: Do to all Profiles or a specific profile
that you want to hide those tabs)
Click Edit
Go to Tab Settings section and hide the following tabs if visible:
DEPRECATED - BDE Wizard 2.0
DEPRECATED-ProntoPayments Settings
DEPRECATED - Bulk Donation Templates
Deprecated ProntoPayments Settings
DEPRECATED - ProntoGiving Settings2
DEPRECATED-Manage ABA Files
Bulk Donation Entry Wizard v1.0
Bulk Donations (v1.0)
Receipt Templates
Consolidated Statements
Consolidated Statements Settings
Quick Donate 1
Batch Data Entry
Quick Donate
Setup Process Type for Payment Transaction
Go to Setup | Object Manager | Payment Transactions | Fields & Relationships | Process Type
Make sure that the Manual Payment and Via ProntoPayments are active in the picklist values section.
Setup Field Dependencies on Process Type
Go to Setup | Object Manager | Payment Transactions | Fields & Relationships | Process Type
Edit the Field Dependencies
Under Manual Payment select:
Cash
Cheque
Bank Account
Credit Card
Under Via ProntoPayments select:
Bank Account
Credit Card
Enable the Manual Payment record type
Go to Setup | Object Manager | Payment Transaction | Record Types | Manual Payment | Edit
Setup Cash record type
Process Type
Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Process Type → Edit
Ensure Manual Payment and Via ProntoPayments are in the Selected Values column
Payment Type
Ensure all values are in the Selected Values column
Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Payment Type
Card Expiry Month
Ensure all values are in the Selected Values column
Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Card Expiry Month
CardType
Ensure all values are in the Selected Values column
Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Card Type
Payment Status
Ensure all values are in the Selected Values column
Go to Setup | Object Manager | Payment Transactions | Record Types | Cash | Edit Payment Status
Setup Manual Payment record type
Follow the same steps as Cash record type
Setup Field Sets
This section uses the Field Sets section found under Setup | Object Manager | Opportunity. For each field set type, select Edit and display the following fields:
One-Off Donation
Close Date
Lead Source
Stage
Primary Campaign Source
Receipt Action (PPlus)
Receipt Template (PPlus)
Recurring Donation
Recurring Type
Date Established
Installment Period
Installment Frequency
Day Of Month
Number of Planned installments
Receipt Action (PPlus)
Receipt Template (PPlus)
Campaign
QD New Contact Fieldset
First Name
Last Name
Email
Work Email
Personal Email
Alternate Email
Receipt Email (PPlus)
Receipt Action Preference (PPlus)
QD Existing Contact
First Name
Last Name
Mailing Street
Mailing City
Mailing Country
Mailing State/Province
Mailing Zip/Postal Code
Phone
Email
Work Email
Personal Email
Alternate Email
Receipt Email (PPlus)
Receipt Action Preference (PPlus)
QD New Account Fieldset
Account Name
Receipt Recipient (PPlus)
QD Existing Account Fieldset
Billing Street
Billing City
Billing State/Province
Billing Zip/Postal Code
Billing Country
Receipt Recipient (PPlus)
QD Credit Card Fields (This is only optional because not all gateways require CCV field)
Add CCV (PPlus) field
Additional Information for Quick Donate
If Account is existing/new and the Donation Type is equal to Household or Organisation, the account should have Primary Contact or Receipt Recipient (PPlus) as the value.
If Contact is existing/new and the Donation Type is equal to Individual, the contact should have Receipt Email (PPlus) as the value.
Setup Default Values
Set the default values in your Quick Donate Page.
Go to ProntoGiving Settings | Donation | Quick Donate. These will be set by the client
Setup Sales Process
Go to Setup | Feature Settings | Sales | Sales Process
Ensure that the Pledged or Prospecting stage is selected in your active Sales
Processes
Set Default Record Type to Cash
Go to Setup | Profile | System Admin | Object Settings | Payment Transactions
Set the default record type to Cash.
Donation Fields Mapping
Donation Fields Mapping is a mapping to use for Quick Donate and Batch Donation Entry.
Go to ProntoGiving Settings | Donation Fields Mapping.
Create new mapping by clicking the New button.
Add the mapping below
Donation Type (PPlus)
Receipt Action (PPlus) - for clients that use Wordpress in their Donation Form.
Barcode
Go to ProntoGiving Settings | Donation | Settings | Barcode
Enable the barcode. Once enabled, the barcode field will display in the Quick Donate and Batch Donation Entries page.
Unique ID Campaign Member Field Name - It will recognised the campaign based on what was being setup in the BDE Template. a. Scenario: If the user chooses Barcode Number field the workaround will be; In order to recognise all campaigns with its campaign member barcodes, untick the Campaign as required and remove the campaign from the default list in all templates
Unique ID Account Field Name - scans a matching value on the field specified for Account
Unique ID Contact Field Name - scans a matching value on the field specified for Contact
Unique ID Recurring Donation Field Name - scans a matching value on the field specified for Recurring Donation.
Access permissions
Set these permissions for users to access Quick Donate.
Object | Object Permission | Field Permission | Read Access | Edit Access |
Accounts | Read, Create | Billing Address Receipt Recipient (PPlus) | TRUE | TRUE |
Campaigns | Read, View All |
|
|
|
Contacts | Read, Create | Alternate Email Mailing Address Personal Email Receipt Action Preferences (PPlus) Receipt Email (PPlus), Work Email | 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 |
Payments | Read | All fields | 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 Campaign Date Established Department Exclude in RD Monitoring Installment Period Lead Source Number of Planned Installments Open Ended Status Receipt Action (PPlus) Receipt Template (PPlus) Schedule Type | TRUE | TRUE |
Visualforce Page access | ASPHPPADDON.QuickDonate2 |
ProntoGiving Settings
Setup Opportunity Stages
a. Go to ProntoGiving Settings | Donation | Stage and set according to the client requirements
Setup Settings
Go to ProntoGiving Settings | Donation | Settings and make changes to the following according to the client requirements:
Enable Default Campaign
Anonymous Contact
One-Off Record Type.
Recurring Donations
Go to ProntoGiving Settings | Recurring Donations | Recurring Donation Naming
Setup Recurring Donation Naming.
Setup Update Payment Sources
NPSP Phone and Email Work Flow
These Phone and Email Work Flow Rules should be turned on by default.
Email Workflow Rule
Contact.EmailChanged_Alternate
Contact.EmailChanged_Personal
Contact.EmailChanged_Work
Contact.Preferred_Email__c
Email only: Paste to Work
Phone Workflow Rule
Contact.PhoneChanged_Home
Contact.PhoneChanged_Mobile
Contact.PhoneChanged_Other
Contact.PhoneChanged_Work
Contact.Preferred_Phone__c
Phone only: Paste to Work
Go to Setup > Workflow Rules. Click Activate the workflow rule’s name.
Remote Site Setup
Update Remote Site - Metadata
Setup Remote Site Settings
Switch to Classic Environment
Go to ProntoGiving Settings and copy the highlighted link below.
Note: Every org has a different URL
Go to Setup > Security > Remote Site Settings. Update Metadata Remote Site
Make sure that the “Active” checkbox is ticked and save when done.
Trigger Handlers
Note: Ensure these triggers are added and activated. Adjust the load order accordingly if the client is not using the other features.
Go to App Launcher | Trigger Handler
The PP_ASPaymentTXN_TDTM trigger handler requires ProntoPayments version 2.7 or
higher
Add the PP_Opportunity_TDTM trigger handler if:
The org has NPSP installed, if none, don’t add
Once the trigger is added, enable the NPSP TDTM toggle in ProntoPayments Settings
Load Order should be ProntoPayments, ProntoGiving, ProntoPlus and org customisation for every object.
Please note: all triggers should be Active.
Trigger Handler Name | Object | Class | Load Order | Trigger Action | Asynchronous After Events | Purpose |
---|---|---|---|---|---|---|
PGIV_ASPaymentRefund_TDTM | ASPHPP__ASPayment_Refund__c | ASPHPPADDON.PGIV_ASPaymentRefund_TDTM | 1 | AfterInsert; AfterUpdate |
| Holds the process for the refunding of a payment It will create a Negative GAU record |
PP_ASPaymentTXN_TDTM | ASPHPP__ASPayment_TXN__c | ASPHPPADDON.ProntoPayments_ASPaymentTXN_TDTM | 1 | BeforeInsert; BeforeUpdate; AfterInsert; AfterUpdate | If Asynchronous is true cannot process payment. | After creating/updating the Opportunity record, the Last Payment Transaction field will be populated based on the Payment Transaction of the Opportunity After refunding a payment in Payment Transaction record, the negative Payment Transaction record is populated based on the values from the Payment Refund |
PGIV_RecurringDonation_TDTM | npe03__Recurring_Donation__c | ASPHPPADDON.PGIV_RecurringDonation_TDTM | 3 | BeforeInsert; BeforeUpdate; AfterInsert |
| Set the important info of Recurring Donation before insert/update of Recurring Donation record Create Recurring Donation Action records for newly created Recurring Donations |
PP_Opportunity_TDTM | Opportunity | ASPHPPADDON.ProntoPayments_Opportunity_TDTM | 5 | BeforeInsert; BeforeUpdate; BeforeDelete; AfterInsert; AfterUpdate; AfterDelete | Yes | Validates the Opportunity record before updating if “Allow Opportunity Update even Stage Name is Closed Won” is FALSE e.g. Not allowed to update the Opportunity Amount, this opportunity is already Closed Won Validate the Opportunity record when deleting the record if it has Pending or Success Payment Transaction Automatically creates Payment Transaction when the Opportunity’s Do Not Automatically Create Payment is FALSE |
PGIV_Opportunity_TDTM | Opportunity | ASPHPPADDON.PGIV_Opportunity_TDTM | 6 | BeforeInsert; BeforeUpdate; AfterInsert; AfterUpdate |
| Sets Receipt Number after an Opportunity record is saved Send Receipts for the list of Opportunities Logs the Payment Source update from the Opportunity |
Default Batches to Run
Go to ProntoGiving Settings | Schedule Process | Settings
Batches | Batch Class Name | Descriptions | Default Scheduled Hour |
---|---|---|---|
Delete Donation Page Error Logs | ASPHPPADDON__Donation_Page_Error_Log__c | Donation Page Error Logs records are created if errors are encountered in Donation Page/Forms. All Donation Page Error_Logs with lookup to Opportunities that are Closed/Won with CreatedDate <LAST_N_DAYS> (settings) It remove records because they’re no longer significant. |
|
Process BDE Items | ASPHPPADDON__BDE_Item__c | Processing BDE Items via list view Query all BDE Items with Processing Status “Pending Processing” | Every 6pm |
Recurring Donations
Batches | Batch Class Name | Descriptions | Default Scheduled Hour |
---|---|---|---|
Recurring Donations Monitoring | BatchUpdateRecurringFields |
| Every Hour |
Update Number Of Failed Recurring Donations | BatchUpdateNumberOfFailedRD | Query all non-closed RDs and counts the number of (latest) consecutive closed lost opportunities. | Every Midnight |
Close Open Recurring Donations with Contact Flagged as Deceased | BatchCloseOpenRDWithDeceasedContact | Query all non-closed RDs with Contact npsp__Deceased__c == TRUE Open-Ended Status = Closed Status = Cancelled | Every Midnight |
Number of Fails before Cancelling Recurring Donation |
| Based on “Number of Failed Recurring Donations” field on RD record, if the field matches the set limit in ProntoGiving Settings, RD Status is updated to “Cancelled”, thus Open-Ended Status is updated to “Closed” |
|
Update Paused Donation-s due to Restart |
|
|
|
Update Opportunity Stages via ProntoGiving
This config is for ProntoGiving to update Opportunities instead of ProntoPayments.
In Custom Settings > ProntoPayments Settings, set Use ProntoPayments to Update Opportunity to FALSE.
Set Update Opportunities in the last N days
In ProntoGiving Settings, provide the Update Opportunities in the last N days. This field indicates the date range of the opportunities to be updated to Closed Won/Lost. If not provided, query will then be Close Date For All Time.
Remove old Update Opportunity Stage schedules
This is now removed because this process is called every time payment processing runs.
Setup Retry Function
Check if these toggles are enabled,
o ProntoPayments Settings>Set n as the maximum Donation Retries for bank transactions
o ProntoPayments Settings>Set as the maximum Donation Retries for credit card transactions
BDE
BDE Item processing will only process standard objects; custom objects are not supported.
Ensure Type field picklist values are: Offline Donation, Direct Debit and Credit Card.
Go to Setup > Object Manager > BDE Templates > Fields & Relationships > Type. Picklist values should only be Offline Donation, Direct Debit and Credit Card.
Approval Process
Enable record locking and unlocking in Apex. Go to Setup > Process Automation > Process Automation Settings.
Create Approval Process
Go to Setup > Process Automation > Approval Process. Create new Approval Process for Batch Donation Entry (if not yet created)
In Manage Approval Process For picklist, select the Batch Donation Entry and select the Use Standard Setup Wizard option.
The Process Name should be “Batch Donation Entry Approval Process”. Click Next to proceed.
Under the Use this approval process of the following picklist select “formula evaluates to true” and copy the formula below. Click Next to proceed.
AND($Setup.ASPHPPADDON__ProntoGiving_Settings__c.ASPHPPADDON__Use_Approval_Process_for_Batches__c = true, NOT(ISPICKVAL(ASPHPPADDON__Bulk_Donation_Status__c, 'Processed')), NOT(ISPICKVAL(ASPHPPADDON__Bulk_Donation_Status__c, 'Done')), NOT(ISPICKVAL(ASPHPPADDON__Bulk_Donation_Status__c, 'Approved')) )
In the Record Editability Properties section, choose the “Admins ONLY can edit records during the approval process”. Click Next to proceed.
Choose the BDE Approval Process Template (BDE 2.0). Click Next to proceed
Choose the fields to display in the Approval Request page:
Batch Donation Entry Name
Bulk Donation Status
Description
Expected Total Amount of Donations
Expected Number of Donations
Click Next to proceed
Select Record Creator as the Allowed Submitters. Click Save to finish. After saving, you will be redirected to this page.
Create Initial Submission Actions for Update Batch Status Awaiting Approval. Click the Add Existing button and select Field Update
Create Approval Steps
Click the New Approval Step button
Enter Name and Description, click Next
Step 1: User Approval, Unique Name Step_1_User_Approval
Specify step criteria: Select “Enter this step if the following” criteria are met, else reject record and copy the values below.
Field | Operator | Value |
Batch Donation Entry: Bulk Donation Status | equals | To Be Processed,Awaiting Approval |
Select Approver step and click Save when done.
Create Final Approval Actions - for Update Batch Status Approved. Click the Add Existing button and select Field Update
Create Final Rejection Actions - for Update Batch Status To Be Processed. Click the Add Existing button and select Field Update. After completing the setup click the Activate button to activate the Approval Process.
Enable Approval Process
Enabling the Approval Process toggle will help the Admin to receive an Approval Request and approve or reject the BDE records. Only those Approved BDE records will be processed.
Navigate to ProntoGiving Settings > Batch Donation Entry > BDE 2.0 > Settings > Use Approval Process for Batch Donation Entries. Enabling the toggle will allow processing of Batch Donation Entry records if status is marked as “Approved” only
If the toggle is enabled (ASPHPPADDON__Use_Approval_Process_for_Batches__c = true), the user needs to click the Submit for Approval button to get approval before processing the BDE record, or else an error notification message will pop-up that the criteria is not met, because it is not yet approved. Only “Approved” BDE status will be processed.
Disabling the toggle will allow processing of Batch Donation Entry records even though the status is “To Be Processed”. If the toggle is disabled (ASPHPPADDON__Use_Approval_Process_for_Batches__c = false), the user can process the BDE record bypassing the Approval stage by clicking directly the Process Batch button.
BDE Components
Setup Settings
Go to Setup | Session Settings | Enable Content Delivery Network (CDN) and ensure the tickbox is selected.
User Interface
If some of the components in the Batch Donation Entries are not showing, you can show them by following these steps.
Go to Batch Donation Entries tab
Select any records in the list
Click the settings cog icon and select the Edit Page option. It will load the Lightning record page layout where you can see which Lightning Components are available to use. Search the components by going to the Lightning Components search bar
Ensure the following Components are displayed in the Batch Donation Entries tab:
New BDE Item Form
BDE Items Summary
BDE Items Related List
Search for the components in the search bar and drag them onto the centre component, and Save.
Show BDE Barcode Field in BDE UI
The BDE Barcode will only be visible if the toggle is enabled in the settings. Go to ProntoGiving Settings | Donation | Settings | Barcode. Enable the toggle.
Required Custom Fields
Create the following fields under the BDE Item object before creating the BDE Templates and Item Record Mapping.
Field Label | Field API Name | Data Type |
BSB | Cheque_Bank_Number_BSB__c | Text(80) |
Cheque Account Number | Cheque_Account_Number__c | Text(80) |
Cheque Bank Name | Cheque_Bank_Name__c | Text(255) |
Cheque Date | Cheque_Date__c | Date |
Cheque Drawers Name | Cheque_Drawers_Name__c | Text Area(255) |
Cheque Number | Cheque_Number__c | Text(80) |
Cheque Transit Number | Cheque_Transit_Number__c | Text(80) |
Description | Description__c | Long Text Area(32000) |
Payment ID | Payment_ID__c | Text(80) |
Payment Type | Payment_Type__c | Picklist Cash Cheque Credit Card Tokenisation Bank Account Direct Deposit |
Payment Type 2 | Payment_Type_2__c | Picklist Cash Cheque Credit Card BPay eWallet Direct Deposit |
Receipt Action(PPlus) | Receipt_Action__c | Picklist Default Post Do Not Receipt |
Receipt Template(PPlus) | Receipt_Template__c | Lookup(Receipt Template (PPlus)) |
Billing State | Billing_State__c | Text(80) |
Billing Country | Billing_Country__c | Text(25) |
Billing Street | Billing_Street__c | Text(80) |
Billing City | Billing_City__c | Text(80) |
Billing Postal Code | Billing_Postal_Code__c | Text(18) |
Open Ended Status | Open_Ended_Status__c | Picklist Open None |
Add the following fields if not yet added.
Object | Field Label | Field API Name | Data Type |
Opportunity | Soft Credit Contact | Soft_Credit_Contact__c | (contact lookup) |
Opportunity | Soft Credit Account | Soft_Credit_Account__c | (account lookup) |
Recurring Donation | Soft Credit Contact | Soft_Credit_Contact__c | (contact lookup) |
Recurring Donation | Soft Credit Account | Soft_Credit_Account__c | (account lookup) |
BDE Item fields to be manually deleted
Object | Field Label | Field API Name | Data Type |
BDE Item | Create BDE Item Only | Create_BDE_Item_Only__c | Checkbox |
BDE Item | RD Status | Revised_RD_Status__c | Picklist |
BDE Item | Next Donation | Revised_Next_Donation_Date__c | Date |
BDE Item | Revised Frequency | Revised_Frequency__c | Picklist |
BDE Item | Revised Campaign | Revised_Campaign__c | Lookup(Campaign) |
BDE Item | Revised Amount | Revised_Amount__c | Currency |
BDE Item | RDA Comments | RDA_Comments__c | Long Text Area |
BDE Item | Cheque Account Number | ASPHPPADDON__Cheque_Account_Number__c | Text(80) |
BDE Item | Cheque Account Number | ASPHPPADDON__Cheque_Account_Number_2__c | Text(80) |
BDE Item | Cheque Bank Name | ASPHPPADDON__Cheque_Bank_Name__c | Text(255) |
BDE Item | Cheque Date | ASPHPPADDON__Cheque_Date__c | Date |
BDE Item | Cheque Drawers Name | ASPHPPADDON__Cheque_Drawers_Name__c | Text Area(255) |
BDE Item | Cheque Number | ASPHPPADDON__Cheque_Number__c | Text(80) |
BDE Item | Cheque Transit Number | ASPHPPADDON__Cheque_Transit_Number__c | Text(80) |
Batch Donation Entry Balancing
Go to ProntoGiving Settings > Batch Donation Entry > BDE 2.0 > Settings User Interface. On the Batch Donation Entry Total Match Default field click the dropdown besides to select Unchecked, Checked, and Checked and Locked then click Save.
If Unchecked - The Require Expected Total Match checkbox is unchecked and editable.
If Checked - The Require Expected Total Match checkbox is checked and editable.
If Checked and Locked - The Require Expected Total Match checkbox is checked and this field is read-only.
BDE Settings
Under ProntoGiving Settings > Batch Donation Entry > BDE 2.0 > Settings page:
if the “Use Approval Processs for Batch Donation Entries” toggle is Enabled, it requires that the Batch Donation Entry needs an approval before processing.
if the “Process Payment Immediately” toggle is Enabled, the payment will be processed immediately.
if the “Include BDE Items linked to a BDE” toggle is Enabled, when creating a Batch Donation Entry record it allows to linked a BDE item.
if the “Allow Changes to Processed Batch Donation Entries” is Enabled, it allow changes on the processed Batch Donation Entry records like deleting or editing it.
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 |
Additional Fields
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:
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
Recurring Donation
ASPHPPADDON__Primary_Account__c/ASPHPPADDON__Primary_Contact__c
ASPHPPADDON__Amount__c
ASPHPPADDON__Date__c
ASPHPPADDON__Frequency__c (Weekly, Monthly, Yearly)
Note: If you want to add a field that doesn’t already exist, you can create it as custom field and add the mapping in the BDE Item Record Mapping.
Updating Recurring Donations
ASPHPPADDON__Recurring_Donation__c
It could be any Recurring Donation fields specified in the BDE Item Record Mapping.
Note: For Recurring Donation required fields that are not mapped or setup in BDE Item Record Mapping, make sure to put default values in the following fields:
Date Established → Current Date
npe03_Contactc or npe03Organization_c should not be empty
npe03_Installment_Period_c → Monthly
npe03_Installments_c → 12
npe03_Next_Payment_Date_c → Current Date
npe03_Open_Ended_Status_c → Open
npe03_Schedule_Type_c → Multiple By
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.
Donations via Credit Card (aside from one-off or recurring donations).
ASPHPPADDON__Credit_Card_Name__c
ASPHPPADDON__Credit_Card_Number__c
ASPHPPADDON__Credit_Card_Expiry_Year__c
ASPHPPADDON__Credit_Card_Type__ck
ASPHPPADDON__Credit_Card_Expiry_Month__c
ASPHPPADDON__CCV__c
Donations via Bank Account (aside from one-off or recurring donations)
ASPHPPADDON__Bank_Account_Name__c
ASPHPPADDON__Bank_Account_Number__c
ASPHPPADDON__Bank_Account_BSB__c
Donations with 1 GAU Allocation (aside from one-off or recurring donations)
ASPHPPADDON__GAU_1_Amount__c
ASPHPPADDON__GAU_1_ID__c
ASPHPPADDON__GAU_1_Name__c
Donation with Multiple GAU Allocations
ASPHPPADDON__GAU_Allocations__c
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 provided it meets the criteria.
Import Data via Data Loader
Open the Data Loader application
Click Insert and 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 initialised, 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
To view your success or error files, click View Successes or View Errors. To close the wizard, click OK. 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.
Setup BDE Item Record Mapping
Note: This step is done automatically after installation or upgrade. However, if you need to add more fields to your mapping, you can do so by following the steps provided below.
For example you might have the Amount custom field in the Opportunity object. You need to create the matching custom field in the BDE Item custom object first before you proceed with the mapping.
Add Mapping Via ProntoGiving Settings
Go to ProntoGiving Settings > Batch Donation Entry > BDE 2.0 > Item Record Mapping. It allows you to set certain fields in BDE Items (object) to map against particular object fields (e.g. Opportunity, Contact, Account, Campaign objects, etc).
Once finished, the mapping will be added on the list.
The BDE Item field “Receipt Action (PPlus)” was mapped to the “Receipt Action (PPlus)” field on the Opportunity object.
When the Opportunity record is created, BDE Item “Receipt Action (PPlus)” field value will be copied over to Opportunity “Receipt Action (PPlus)” field.
Add Mapping Via Custom Settings
Go to Setup > Custom Settings > BDE Item Record Mapping > Click Manage.
Add the mappings below by clicking the “New” button.
Additionally, these are mostly the fields in BDE Item that should be mapped accordingly and automatically although some fields may be omitted depends to your need. This is the standard BDE Item Record Mapping.
List of BDE Item fields
Label | API Name | Description |
---|---|---|
Account Name | ASPHPPADDON__Account_Name__c | Name of the new Account record created through processing BDE Item |
Amount | ASPHPPADDON__Amount__c | Amount for each donation for payment transactions |
Bank Account BSB | ASPHPPADDON__Bank_Account_BSB__c | Bank BSB in bank transactions for payment source creation |
Bank Account Name | ASPHPPADDON__Bank_Account_Name__c | Account Name in bank transactions for payment source creation |
Bank Account Number | ASPHPPADDON__Bank_Account_Number__c | Bank number in bank transactions for payment source creation |
Campaign | ASPHPPADDON__Campaign__c | Campaign lookup of the donation |
Campaign Name | ASPHPPADDON__Campaign_Name__c | Name of the new Campaign record created through processing BDE Item |
Cheque BSB Number | Cheque_Bank_Number_BSB__c | Cheque BSB number for cheque transactions |
Cheque Number | Cheque_Number__c | Cheque number for cheque transactions |
Cheque Transit Number | Cheque_Transit_Number__c | Cheque Transit number for cheque transactions |
CCV | ASPHPPADDON__CCV__c | CCV in credit card transaction for payment source creation |
Credit Card Expiry Month | ASPHPPADDON__Credit_Card_Expiry_Month__c | Credit card expiry month in credit card transaction for payment source creation |
Credit Card Expiry Year | ASPHPPADDON__Credit_Card_Expiry_Year__c | Credit card expiry year in credit card transaction for payment source creation |
Credit Card Name | ASPHPPADDON__Credit_Card_Name__c | Credit card name in credit card transaction for payment source creation |
Credit Card Number | ASPHPPADDON__Credit_Card_Number__c | Credit card number in credit card transaction for payment source creation |
Credit Card Type | ASPHPPADDON__Credit_Card_Type__c | Credit card type in credit card transaction for payment source creation |
Day of Month | ASPHPPADDON__Day_of_Month__c | Sets the specific day of the month for future installment Opportunities when the Installment Period is Monthly. If you select 29 or 30, the installment date will be the last day of the month for months that don't have that many days. |
Recurring Type | ASPHPPADDON__Recurring_Type__c | Select Open for an ongoing Recurring Donation. Select Fixed for a Recurring Donation that has a specific number of installments. |
RD Effective Date | ASPHPPADDON__Effective_Date__c | The date that new or updated schedule information (Amount, Day of Month, etc.) for this Recurring Donation takes effect. The default is the current date. |
Number of Planned Installments | ASPHPPADDON__Number_of_Planned_Installments__c | Number of installments (donations) you expect to receive. For Fixed-Length Recurring Donations only. |
Installment Frequency | ASPHPPADDON__Installment_Frequency__c | The Installment Frequency along with Installment Period defines the installment schedule of the Recurring Donation |
Installment Period | ASPHPPADDON__Installment_Period__c | How often you’ll receive the donations. |
Date | ASPHPPADDON__Date__c | Close Date for Opportunity record, Date Established in Recurring Donation record and Payment Date in Payment Transaction record |
ASPHPPADDON__Email__c | Email of the Contact record | |
Account Email | ASPHPPADDON__Account_Email__c | Email of the Account record |
First Name | ASPHPPADDON__First_Name__c | First name of the new Contact record created through processing BDE Item |
Frequency | ASPHPPADDON__Frequency__c | Installment Period of the Recurring Donation |
Gateway | ASPHPPADDON__Gateway__c | Gateway used for processing the payments from the donation |
Last Name | ASPHPPADDON__Last_Name__c | Last name of the new Contact record created through processing BDE Item |
Lead Source | LeadSource__c | Lead Source for Opportunity record and Recurring Donation record |
Billing Street | Billing_Street__c | Billing street of the Account’s billing address |
Billing City | Billing_City__c | Billing city of the Account’s billing address |
Billing State | Billing_State__c | Billing state of the Account’s billing address |
Billing Postal Code | Billing_Postal_Code__c | Billing postal code of the Account’s billing address |
Billing Country | Billing_Country__c | Billing country of the Account’s billing address |
Department | Department__c | Department for the Opportuntiy record and Recurring Donation record |
Receipt Template (PPlus) | Receipt_Template__c | Receipt template in Opportuntiy record and Recurring Donation record used for the receipt of the donation |
Donation Type | ASPHPPADDON__Donation_Type__c | Donation Type for the donation if it is Individual, Household, Organisation or Anonymous |
Cheque Date | Cheque_Date__c | Cheque date for cheque transactions |
Cheque Account Number | Cheque_Account_Number__c | Cheque account number for cheque transactions |
Cheque Drawers Name | Cheque_Drawers_Name__c | Cheque drawer’s name for cheque transactions |
Open Ended Status | Open_Ended_Status__c | Open Ended Status of the Recurring Donation record |
Payment Type 2 | Payment_Type_2__c | Payment Type for Opportunity record and Recurring Donation record with eWallet and BPAY options |
Parent Campaign Name | ASPHPPADDON__Parent_Campaign_Name__c | Parent campaign name of the new Campaign record created through processing BDE Item |
Payment Source | ASPHPPADDON__Payment_Source__c | Payment Source of the of the payments |
Payment Source Token | ASPHPPADDON__Payment_Source_Token__c | Payment source token of the Payment Source |
Payment Type | Payment_Type__c | Payment Type of the payment for Opportunity record and Recurring Donation record |
Donor Organisation | ASPHPPADDON__Primary_Account__c | Account lookup for the Opportunity record and Recurring Donation record |
Donor Contact | ASPHPPADDON__Primary_Contact__c | Contact lookup for the Opportunity record and Recurring Donation record |
Primary Contact Address 1 | ASPHPPADDON__Primary_Contact_Address_1__c | Mailing street of the Contact’s mailing address |
Primary Contact City | ASPHPPADDON__Primary_Contact_City__c | Mailing city of the Contact’s mailing address |
Primary Contact Country | ASPHPPADDON__Primary_Contact_Country__c | Mailing country of the Contact’s mailing address |
Primary Contact Postal Code | ASPHPPADDON__Primary_Contact_Postal_Code__c | Mailing postal code of the Contact’s mailing address |
Primary Contact State | ASPHPPADDON__Primary_Contact_State__c | Mailing state of the Contact’s mailing address |
Receipt Action (PPlus) | Receipt_Action__c | Receipt action in Opportuntiy record and Recurring Donation record used if the receipt of the donation is Post or Email |
RD Status | ASPHPPADDON__RD_Status__c | Status of the Recurring Donation record |
Soft Credit Account Email | ASPHPPADDON__Soft_Credit_Account_Email__c | Email for the soft credit Account record |
Soft Credit Account Name | ASPHPPADDON__Soft_Credit_Account_Name__c | Name for the soft credit Account record |
Soft Credit Account | ASPHPPADDON__Soft_Credit_Account__c | Account lookup for the Recurring Donation record |
Soft Credit Contact Address | ASPHPPADDON__Soft_Credit_Contact_Address__c | Mailing street of the soft credit Contact’s mailing address |
Soft Credit Contact City | ASPHPPADDON__Soft_Credit_Contact_City__c | Mailing city of the soft credit Contact’s mailing address |
Soft Credit Contact Country | ASPHPPADDON__Soft_Credit_Contact_Country__c | Mailing country of the soft credit Contact’s mailing address |
Soft Credit Contact Email | ASPHPPADDON__Soft_Credit_Contact_Email__c | Email of the soft credit Contact record |
Soft Credit Contact First Name | ASPHPPADDON__Soft_Credit_Contact_First_Name__c | First name of the soft credit Contact record |
Soft Credit Contact Last Name | ASPHPPADDON__Soft_Credit_Contact_Last_Name__c | Last Name of the soft credit Contact record |
Soft Credit Contact Phone | ASPHPPADDON__Soft_Credit_Contact_Phone__c | Phone number of the soft credit Contact record |
Soft Credit Contact Postal Code | ASPHPPADDON__Soft_Credit_Contact_Postal_Code__c | Mailing postal code of the soft credit Contact’s mailing address |
Soft Credit Contact State | ASPHPPADDON__Soft_Credit_Contact_State__c | Mailing state of the soft credit Contact’s mailing address |
Soft Credit Card Contact | ASPHPPADDON__Soft_Credit_Contact__c | Contact lookup for the Recurring Donation record |
List of BDE Item fields Mapping
NAME | ASPHPPADDON__BULK_DONATION_ITEM_FIELD__C | ASPHPPADDON__OBJECT_FIELD__C | ASPHPPADDON__OBJECT__C | ASPHPPADDON__PARENT_CAMPAIGN__C | ASPHPPADDON__SOFT_CREDIT__C |
Donation Type RD | ASPHPPADDON__Donation_Type__c | ASPHPPADDON__Donation_Type__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Cheque BSB Number | Cheque_Bank_Number_BSB_c__c | ASPHPP__Check_Bank_Number__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
Cheque Drawers Name | Cheque_Drawers_Name__c | ASPHPP__Cheque_Bank_Name__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
P-2 | Payment_Type_2__c | ASPHPP__Payment_Type__c | Opportunity | FALSE | FALSE |
Receipt Action | Receipt_Action__c | ProntoPlus__Receipt_Action__c | Opportunity | FALSE | FALSE |
Receipt Action 2 | Receipt_Action__c | ProntoPlus__Receipt_Action__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Soft Credit Contact2 | ASPHPPADDON__Soft_Credit_Contact__c | Soft_Credit_Contact__c | npe03__Recurring_Donation__c | FALSE | TRUE |
Soft Credit Account2 | ASPHPPADDON__Soft_Credit_Account__c | Soft_Credit_Account__c | npe03__Recurring_Donation__c | FALSE | TRUE |
Billing State | Billing_State__c | BillingState | Account | FALSE | FALSE |
Billing Country | Billing_Country__c | BillingCountry | Account | FALSE | FALSE |
Billing Street | Billing_Street__c | BillingStreet | Account | FALSE | FALSE |
Billing City | Billing_City__c | BillingCity | Account | FALSE | FALSE |
Billing Postal Code | Billing_Postal_Code__c | BillingPostalCode | Account | FALSE | FALSE |
Parent Campaign Name | ASPHPPADDON__Parent_Campaign_Name__c | Name | Campaign | FALSE | FALSE |
Account Name | ASPHPPADDON__Account_Name__c | Name | Account | FALSE | FALSE |
Amount | ASPHPPADDON__Amount__c | Amount | Opportunity | FALSE | FALSE |
Amount2 | ASPHPPADDON__Amount__c | npe03__Amount__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Amount3 | ASPHPPADDON__Amount__c | ASPHPP__aspp_Amount__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
Bank Account BSB | ASPHPPADDON__Bank_Account_BSB__c | ASPHPP__Account_BSB__c | ASPHPP__ASPayment_Source__c | FALSE | FALSE |
Bank Account Name | ASPHPPADDON__Bank_Account_Name__c | ASPHPP__Account_Name__c | ASPHPP__ASPayment_Source__c | FALSE | FALSE |
Bank Account Number | ASPHPPADDON__Bank_Account_Number__c | ASPHPP__Account_Number__c | ASPHPP__ASPayment_Source__c | FALSE | FALSE |
Campaign | ASPHPPADDON__Campaign__c | CampaignId | Opportunity | FALSE | FALSE |
Campaign Name | ASPHPPADDON__Campaign_Name__c | Name | Campaign | FALSE | FALSE |
Campaign2 | ASPHPPADDON__Campaign__c | npe03__Recurring_Donation_Campaign__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Credit Card CCV | ASPHPPADDON__CCV__c | ASPHPP__Card_CCV__c | ASPHPP__ASPayment_Source__c | FALSE | FALSE |
Credit Card Expiry Month | ASPHPPADDON__Credit_Card_Expiry_Month__c | ASPHPP__Card_Expiry_Month__c | ASPHPP__ASPayment_Source__c | FALSE | FALSE |
Credit Card Expiry Year | ASPHPPADDON__Credit_Card_Expiry_Year__c | ASPHPP__Card_Expiry_Year__c | ASPHPP__ASPayment_Source__c | FALSE | FALSE |
Credit Card Name | ASPHPPADDON__Credit_Card_Name__c | ASPHPP__Card_Name__c | ASPHPP__ASPayment_Source__c | FALSE | FALSE |
Credit Card Number | ASPHPPADDON__Credit_Card_Number__c | ASPHPP__Card_Number__c | ASPHPP__ASPayment_Source__c | FALSE | FALSE |
Credit Card Type | ASPHPPADDON__Credit_Card_Type__c | ASPHPP__Credit_Card_Type__c | ASPHPP__ASPayment_Source__c | FALSE | FALSE |
Day of Month | ASPHPPADDON__Day_of_Month__c | npsp__Day_of_Month__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Recurring Type | ASPHPPADDON__Recurring_Type__c | npsp__RecurringType__c npe03__Open_Ended_Status__c | npe03__Recurring_Donation__c | FALSE | FALSE |
RD Effective Date | ASPHPPADDON__Effective_Date__c | npsp__StartDate__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Number of Planned Installments | ASPHPPADDON__Number_of_Planned_Installments__c | npe03__Installments__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Installment Frequency | ASPHPPADDON__Installment_Frequency__c | npsp__InstallmentFrequency__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Installment Period | ASPHPPADDON__Installment_Period__c | npe03__Installment_Period__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Date | ASPHPPADDON__Date__c | CloseDate | Opportunity | FALSE | FALSE |
Date2 | ASPHPPADDON__Date__c | npe03__Date_Established__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Date3 | ASPHPPADDON__Date__c | ASPHPP__aspp_Payment_Date__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
ASPHPPADDON__Email__c | Contact | FALSE | FALSE | ||
Email2 | ASPHPPADDON__Account_Email__c | ASPHPP__PPEmail__c | Account | FALSE | FALSE |
First Name | ASPHPPADDON__First_Name__c | FirstName | Contact | FALSE | FALSE |
Frequency | ASPHPPADDON__Frequency__c | npe03__Installment_Period__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Gateway | ASPHPPADDON__Gateway__c | ASPHPP__Gateway__c | Opportunity | FALSE | FALSE |
Gateway2 | ASPHPPADDON__Gateway__c | ASPHPPADDON__Gateway__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Last Name | ASPHPPADDON__Last_Name__c | LastName | Contact | FALSE | FALSE |
Payment Source | ASPHPPADDON__Payment_Source__c | ASPHPP__Payment_Source__c | Opportunity | FALSE | FALSE |
Payment Source Token | ASPHPPADDON__Payment_Source_Token__c | ASPHPP__Token__c | ASPHPP__ASPayment_Source__c | FALSE | FALSE |
Payment Source2 | ASPHPPADDON__Payment_Source__c | ASPHPPADDON__Payment_Source__c | npe03__Recurring_Donation__c | FALSE | FALSE |
PPlus Donation Type | ASPHPPADDON__Donation_Type__c | ProntoPlus__Donation_Type__c | Opportunity | FALSE | FALSE |
PPlus Donation Type2 | ASPHPPADDON__Donation_Type__c | ProntoPlus__Donation_Type__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Primary Account | ASPHPPADDON__Primary_Account__c | AccountId | Opportunity | FALSE | FALSE |
Primary Account2 | ASPHPPADDON__Primary_Account__c | npe03__Organization__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Primary Contact | ASPHPPADDON__Primary_Contact__c | npsp__Primary_Contact__c | Opportunity | FALSE | FALSE |
Primary Contact Address 1 | ASPHPPADDON__Primary_Contact_Address_1__c | MailingStreet | Contact | FALSE | FALSE |
Primary Contact City | ASPHPPADDON__Primary_Contact_City__c | MailingCity | Contact | FALSE | FALSE |
Primary Contact Country | ASPHPPADDON__Primary_Contact_Country__c | MailingCountry | Contact | FALSE | FALSE |
Primary Contact Postal Code | ASPHPPADDON__Primary_Contact_Postal_Code__c | MailingPostalCode | Contact | FALSE | FALSE |
Primary Contact State | ASPHPPADDON__Primary_Contact_State__c | MailingState | Contact | FALSE | FALSE |
Primary Contact2 | ASPHPPADDON__Primary_Contact__c | npe03__Contact__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Recurring Status | ASPHPPADDON__RD_Status__c | ASPHPPADDON__Status__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Soft Credit Account Email | ASPHPPADDON__Soft_Credit_Account_Email__c | ASPHPP__PPEmail__c | Account | FALSE | TRUE |
Soft Credit Account Name | ASPHPPADDON__Soft_Credit_Account_Name__c | Name | Account | FALSE | TRUE |
Soft Credit Contact Address 1 | ASPHPPADDON__Soft_Credit_Contact_Address__c | MailingStreet | Contact | FALSE | TRUE |
Soft Credit Contact Phone | ASPHPPADDON__Soft_Credit_Contact_Phone__c | MobilePhone | Contact | FALSE | TRUE |
Soft Credit Contact City | ASPHPPADDON__Soft_Credit_Contact_City__c | MailingCity | Contact | FALSE | TRUE |
Soft Credit Contact Email | ASPHPPADDON__Soft_Credit_Contact_Email__c | Contact | FALSE | TRUE | |
Soft Credit Contact First Name | ASPHPPADDON__Soft_Credit_Contact_First_Name__c | FirstName | Contact | FALSE | TRUE |
Receipt Template RD | Receipt_Template__c | ProntoPlus__Receipt_Template__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Receipt Template Opp | Receipt_Template__c | ProntoPlus__Receipt_Template__c | Opportunity | FALSE | FALSE |
Department Opp | Department__c | ProntoPlus__Department__c | Opportunity | FALSE | FALSE |
Department RD | Department__c | ProntoPlus__Department__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Soft Credit Contact Last Name | ASPHPPADDON__Soft_Credit_Contact_Last_Name__c | LastName | Contact | FALSE | TRUE |
Soft Credit Contact Country | ASPHPPADDON__Soft_Credit_Contact_Country__c | MailingCountry | Contact | FALSE | TRUE |
Soft Credit Contact Postal Code | ASPHPPADDON__Soft_Credit_Contact_Postal_Code__c | MailingPostalCode | Contact | FALSE | TRUE |
Soft Credit Contact State | ASPHPPADDON__Soft_Credit_Contact_State__c | MailingState | Contact | FALSE | TRUE |
Payment Type Opp | Payment_Type__c | ASPHPP__Payment_Type__c | Opportunity | FALSE | FALSE |
Payment Type 2 | Payment_Type__c | ASPHPP__Payment_Type__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
P-1 | Payment_Type_2__c | ASPHPP__Payment_Type__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
Cheque Date | Cheque_Date__c | ASPHPPADDON__Cheque_Date__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
Open Ended Status | Open_Ended_Status__c | npe03__Open_Ended_Status__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Lead Source 2 | LeadSource__c | ASPHPPADDON__Lead_Source__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Cheque Number | Cheque_Number__c | ASPHPP__Check_Number__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
Cheque Account Number | ASPHPPADDON__Cheque_Account_Number_2__c | ASPHPP__Check_Account_Number__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
Donation Type Opp | ASPHPPADDON__Donation_Type__c | ASPHPPADDON__Donation_Type__c | Opportunity | FALSE | FALSE |
Cheque Transit Number | Cheque_Transit_Number__c | ASPHPP__Check_Transit_Number__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
Lead Source | LeadSource__c | LeadSource | Opportunity | FALSE | FALSE |
Payment Type RD | Payment_Type__c | ASPHPPADDON__Payment_Type__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Payment Type RD2 | Payment_Type_2__c | ASPHPPADDON__Payment_Type__c | npe03__Recurring_Donation__c | FALSE | FALSE |
Payment Type RD3 | Payment_Type_2__c | ASPHPPADDON__Payment_Type__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
Payment Type RD4 | Payment_Type__c | ASPHPPADDON__Payment_Type__c | ASPHPP__ASPayment_TXN__c | FALSE | FALSE |
Add Mapping Via Data Loader
Fields not included for mapping (BDE Item field exceptions) are:
Batch Donation Entry
BDE Item Name
GAU Allocation fields
Processing Status
Status Message
Custom fields in Recurring Donation and Opportunity that needs to be created in the client’s org (per request), if non existing.
Object | Custom Fields | Data type |
Opportunity | Soft Credit Account | Lookup (Account) |
Opportunity | Soft Credit Contact | Lookup (Contact) |
Recurring Donation | Soft Credit Account | Lookup (Account) |
Recurring Donation | Soft Credit Contact | Lookup (Contact) |
Expected Outcome
Assumption: Batch Donation Entry record is already created with BDE Items record, say Batch Donation Entries > Select a BDE Record > Related Lists > BDE Items. Assuming Approval Process is disabled in ProntoGiving Settings, clicking the Process BDE button submits the related BDE Items and creates the appropriate records. In this case, an Opportunity record.
The values from BDE Item fields are copied to Opportunity fields, based on the BDE Item Record Mapping in ProntoGiving Settings.
Process BDE Items
Assumption: Make sure that BDE Item fields are already mapped to preferred object/record fields. Please see BDE 2.0: Item Record Mapping on how to do it.
Via Process BDE Items button
The user is able to process selected BDE Items or all Items in list view through Process BDE Items button. The following instructions will walk you through.
Go to BDE Items tab
Let’s assume that BDE Items with Pending Processing is already created
To process these BDE Items, the user needs to select item(s) and click the Process BDE Items button
After the user clicks the button, a pop up page will appear and allows him to choose whether to process Selected BDE Items or All BDE Items on the List View
If the Selected BDE Items option is selected, it will process only the BDE Items that are ticked
If the All BDE Items on List View option is selected, it will process all the items on the List View even if a few records are only selected
When the user selects an option and clicks the Process button from the popup page, BDE Items are processed
After the BDE Items are successfully processed, the user is notified through the notification message
Otherwise, if failed, Processing Status of BDE Item will be Failed.
Via Batch Job
BDE Items with processing status value of Pending Processing and are not linked to any Batch Donation Entry record can be processed through a manual batch or scheduled job.
Step 1: Manual Batch Run
Go to ProntoGiving Settings | Schedule Process | Settings | Process BDE Items
The user can specify how many records will be processed per batch iteration. This can be done by setting up the number on this field. If the Number of Records per iteration field has no value, the hard-coded default value is 10 records per iteration
Click Save Batch Size button
The user can then click the Run Batch button
The progress of the batch can be monitored in the Setup | Environments | Jobs | Apex Jobs
Step 2: Scheduled Batch Run
The user can set the schedule easily through the ProntoGiving Settings scheduler page. Navigate to ProntoGiving Settings | Schedule Process | Settings
Under the Single/Bulk Donations section, there’s a process name called Process BDE Items
The user can set the time through the field provided in the settings
Click the Schedule Batch button to start the schedule
To check whether the schedule is set successfully, the Schedule Batch button is changed to Stop Batch. You can also verify it in Setup | Environments | Jobs | Scheduled Jobs
Sync BDE Item Fields
Insert Automations
An option to automate the process in adding a volume of Active Values to Batch Donation Entry Item from the Opportunity Stage, Account Record Type, Campaign Record Type and Opportunity Record Type.
Note: The BDE Item Object Values should have the same Values with Opportunity, Account and Campaign Object. If it will not coincide, a conflict might occur if there is any future processing in BDE Item.
Check the existing values from Opportunity Stage and Record Type, Account Record Type and Campaign Record Type, before Syncing to Batch Donation Item fields. Making sure that there are values to be synced.
Step 1: Check Opportunity Stage (Clicking ‘New’ button will insert new value). Navigate to Setup | Object Manager | Opportunity | Fields & Relationships | Stage | Opportunity Stages Picklist Values
Step 2: Check Accounts Record Type (Clicking ‘New’ button will insert new value). Navigate to Setup | Object Manager | Account | Field & Relationship | Type | Account Type Picklist Values
Step 3: Check Campaign Record Type (Clicking ‘New’ button will insert new value). Navigate to Setup | Object Manager | Campaign | Field & Relationship | Type | Campaign Type Picklist Values
Step 4: Check Opportunity Values (clicking ‘new’ button will insert new value). Navigate to Setup | Object Manager | Opportunity | Fields & Relationships | Type | Opportunity Type Picklist Values.
Step 5: Sync Button Behaviours
Navigate to ProntoGiving Settings | Batch Donation Entry | BDE 2.0 | Settings | Sync BDE Item Fields
Clicking Opportunity Stage Sync button, the active values from Opportunity Stage will be copied to BDE Item field “ASPHPPADDON__Opportunity_Stage__c” (picklist) as values
Clicking Account Record Type Sync button, the active values from Account Record Type will be copied to BDE Item field “ASPHPPADDON__Primary_Account_Record_Type__c” (picklist) as values
Clicking Campaign Record Type Sync button, the active values from Campaign Record Type will be copied to BDE Item field “ASPHPPADDON__Campaign_Record_Type__c” (picklist) as values
Clicking Opportunity Record Type Sync button, the active values from opportunity Record Type will be copied to BDE Item field “ASPHPPADDON__Opportunity_Record_Type__c” (picklist) as values.
Step 6: Test Syncing Process. To check if it is successfully synced and populated in Batch Donation Entry Item fields, go to Setup | BDE Item | Fields & Relationships.
ASPHPPADDON__Opportunity_Stage__c | Values
ASPHPPADDON__Primary_Account_Record_Type__c | Values
ASPHPPADDON__Campaign_Record_Type__c | Values
ASPHPPADDON__Opportunity_Record_Type__c | Values
Insert Manually
You have another option to manually add a single value to BDE Item fields or to Opportunity, Account, Campaign object fields.
Note: The BDE Item Object Values should have the same Values with Opportunity, Account and Campaign Object. If it will not coincide, a conflict might occur if there is any future processing in BDE Item.
BDE Item Fields
Step 1: Insert Opportunity Stage value manually. Navigate to Setup | Object Manager | BDE Item | Fields & Relationships | Opportunity Stage | Picklist Values.
Click New button to insert new value. Select Save button when done.
Step 2: Insert Account Record Type value manually. Navigate to Setup | Object Manage | BDE Item | Fields & Relationships | Primary Account Record Type | Picklist Values.
Click New button to insert new value and click Save button when done.
Step 3: Insert Campaign Record Type value manually. Navigate to Setup | Object Manager | BDE Item | Fields & Relationships | Campaign Record Type | Picklist Values
Click New button to insert new value and select Save button when done.
Step 4: Insert Opportunity Record Type value manually. Navigate to Setup | Object Manager | BDE Item | Fields & Relationships | Opportunity Record Type | Picklist Values
Click New button to insert new value and select Save button when done.
Note: Make sure to Add Values also in Opportunity, Account Campaign Object fields (B), right after you’ve finished adding on the BDE item fields. (Proceed on Step B)
B. Opportunity, Account, Campaign
Step 1: Insert Opportunity Stage value manually. Navigate to Setup | Object Manager | Opportunity | Fields & Relationships | Stage | Picklist Values.
Click New button to insert new value. Complete the following fields and select Save when done.
Stage Name
Type
Description
Probability
Forecast Category
Step 2: Insert Opportunity Record Type manually. Navigate to Setup | Object Manager | Opportunity | Fields & Relationships | Type | Picklist Values
Click New button to insert new value and select Save.
Step 3. Insert Account Record Type manually. Navigate to Setup | Object Manager | Account | Fields & Relationships | Type | Picklist Values.
Click New button to insert new value and select Save.
Step 4. Insert Campaign Record Type manually. Navigate to Setup | Object Manager | Campaign | Fields & Relationships | Type | Picklist Values
Click New button to insert new value and select Save.
Enhanced Recurring Donations - Upgrade Guide
Complete reference: https://sfdo-docs.s3-us-west-2.amazonaws.com/npsp_rd_upgrade_guide.pdf
NOTE: As mentioned on the reference above, it is strongly recommended to test these steps first in your sandbox environment.
Enable Enhanced Recurring Donation
Database Preparation Tasks
See Database Preparation Tasks section from this reference https://sfdo-docs.s3-us-west-2.amazonaws.com/npsp_rd_upgrade_guide.pdf. Make sure to follow these steps before proceeding.
Validate Migration
Go to NPSP Settings tab > Recurring Donations > Upgrade to Enhanced Recurring Donations. Click Validate Migration. =
After validation completes, you can view the results.
Enable Enhanced Recurring Donations
Confirm that you have completed the preparation and validation tasks (1) if Validate Migration finds errors, resolve them before you continue. Once confirmed, you can enable the Enhanced Recurring Donations (2). Please take note that after the Enhanced RD is enabled, there’s no way to disable it again.
Deploy Metadata
After enabling the Enhanced Recurring Donation, click Launch MetaDeploy (3). MetaDeploy is an external service and opens in a new browser tab. When you’re done with the MetaDeploy, close it and return to your Salesforce org to complete the upgrade process.
Click Log In to Start Pre-Install Validation, then choose whether you’re installing in a Production or Sandbox org.
Provide your Salesforce login credentials and click Log In.
When prompted, Allow access. Wait for the Pre-Intsall Validation to finish. Click Install
Read the Product Terms of Use and Licenses. Select the confirmation checkbox then click Confirm
Wait for the installation to finish
Close MetaDeploy and return to your Salesforce org
Confirm that you’ve installed the Enhanced Recurring Donations metadata.
Migrate Data
To check for any changes occurred in your org after you enabled Enhanced Recurring Donations (between steps 2 and 3), click Validate Migration again to confirm no errors before migration. You may also click Skip Validation if you chose not to re-validate.
When validation without errors is confirmed, click Ready to Migrate.
Then click Run Migration. The data migration may take some time to complete, depending on the number of Recurring Donation records in your database.
When the migration process completes, you can view the details. If the Status is Complete, you’re all done!
Product Configuration after enabling Enhanced Recurring Donations
Donation Fields Mapping
Go to ProntoGiving Settings tab > Donation Field Mappings and add the Payment Type → Payment Method mapping (highlighted below)
PGIV Recurring Donation Field | Map to Recurring Donation Field |
ASPHPPADDON__Payment_Type__c | npsp__PaymentMethod__c |
Go to NPSP Settings tab > Recurring Donations > Recurring Donation Custom Field Mappings and add the Payment Method → Payment Type mapping (highlighted below)
Recurring Donation Field | Opportunity Field |
npsp__PaymentMethod__c | ASPHPP__Payment_Type__c |
Quick Donate New Tab
Create the Recurring Donation Field Sets by adding the following fields:
Recurring Type
Date Established
Installment Period
Installment Frequency
Day of Month
Number of Planned Installments
Receipt Action (PPlus)
Receipt Template (PPlus)
Campaign
If Enhanced Recurring Donations is disabled, the Quick Donate page will not display and a validation message is shown.
Recurring Donation Section - Quick Donate
Display the minimum required fields on the form for Recurring Donation section via field set
Go to Setup > Object Manager > Recurring Donation > Field Sets > QD Recurring Donation
Date Established (required)
Recurring Type - Open or Fixed
If Recurring Type is Fixed, Number of Planned Installments should be enabled and required. Otherwise field is disabled
Recurring Period - Monthly or Advanced
Monthly
Day of Month (required)
Effective Date
Advanced
Installment Frequency (required)
Installment Period (required)
Day of Month - displayed and required only if Installment Period is Monthly
Effective Date
To verify, create recurring donation record for monthly, weekly, fortnightly, quarterly and yearly.
Donation Type - Quick Donate
For Individual and Household, Contact should be displayed and required. Organisation field is not required and Organisation section is hidden.
For Organisation, the Organisation field should be displayed and required. The Contact field is not required and Contact section is hidden.
Quick Donate Button Redirect
Go to ProntoGiving Settings tab > Donation > Quick Donate and set the version to “Enhanced RD”. To confirm, go to any Contact or Account record and click the Quick Donate button. Make sure the Quick Donate New (VF) is displayed.