I'm also interested in leveraging Communities to allow donors to track their giving history and volunteers see events they have signed up for and track their hours. How are other nonprofits handling this process? Any ideas?
How will this work with Volunteer for Salesforce (V4S) App?
Will the Customer Community License allow these features?
#Volunteers for Salesforce (V4S) #Event Management #Fundraising #Donor Management
We are doing our accounting and donor management in Aplos. For a new program we have we would like to be able to create/update a contact in salesforce when a new person donates. I am wondering if anyone has already done any integration with Aplos and could point me in a starting direction or suggestions of ways to do this
@Nonprofit Success Pack*FOLLOW-UP ASSETS READY -- Nonprofit WealthEngine Fundraising Webinar!*
On Tuesday, May 15th, we hosted the webinar, "Data-Driven Donor Prospecting with Salesforce + WealthEngine," showcasing how leading nonprofits are using WealthEngine and Salesforce to enrich CRM data with prospect wealth scoring and donor research.
Follow-up Resources:
Thanks to @Andrea Schiller for organizing this webinar and presenting the content!
#Webinar Recording #Webinars #Fundraising #E-book #Wealthengine #Donor Prospecting #CRM Data #NGO Webinars
Moves Management and NPSP
Last week, my colleague @Sara Metheny broke down how to cultivate donors with NPSP. It's a pretty neat little hack and only 6 steps. Check it out: http://www.idealistconsulting.com/blog/moves-management-npsp-cultivation-salesforce
After upgrading to NPSP 3 in a sandbox, I saw for the first time that a non-primary donor contact role displays on a donation for a household member. That doesn't occur in our production 2.x version.
I wondering what configuration setting causes the difference.
These are the Household settings in production (2.x):
Enable Household Opportunity Rolls - checked
HH record type exclusions - no record types selected
Member opportunity contact role - Donor
Contact role exclusions - no record types selected
These are the ones in the sandbox (NPSP settings, Donations, Contact Roles)
Opp Contact Role Default Role: Donor
Always rollup to primary contact role: checked
Enable soft credit rollups: unchecked
Soft credit rolls: not set
Household contact roles on: checked
Household member contact roles: Donor
HH OCR excluded record types: not set
I'd like to enable the non-primary donor functionality in production prior to an upgrade - is this possible and if so, what settings should I change?
@Nonprofit Success Pack #Donor Contact RolesHi all,
We're rethinking our opportunity stage pipeline for major gifts and large fundraising events for which we create prospects. We would like to more accurately track where someone is in the "sales" process.
Right now we're using the SF default: Prospecting, Pledged, Posted. At the very least, we need one stage between prospecting and pledged to represent that we are in conversation with someone about their giving.
I'm looking for ideas/suggestions for opportunity stages that would more accurately reflect the lifecycle of these donations.
Here are a few resources I found so far:
https://developer.salesforce.com/page/Nonprofit_Success_-_Donation_Management#Sales_Stageshttp://www.501ctech.org/the-opportunity-cycle-in-salesforce-com-2/Thanks, all!
Jodi
, I have a (probably) quick question I'm hoping you can help with. I'm just getting started with it.
I want to use it to send receipts to donors. We send all receipts by postal mail.
The context:
* Opportunities are used to track donations
* Checkbox indicates whether or not the donor has been thanked
* All individuals and all organizations get their own account; there are no contacts under accounts. To track employment relationships, we exclusively use affiliations. Therefore, the Opportunity.AccountName will always be the actual donor -- either an individual's name (their 1:1 account), or the organization's name. We have a required opp pick list that specifies whether it's an individual or a business/entity donation.
* For donations from organizations, we use the Contact Role to indicate who the primary individual at the organization was. Contact Role of "Donor", and checked for Primary.
I've uploaded a Word doc template file as our receipt. The address block references
Account.Nameand Account billing address.
I would like the "Dear __________" line to be their first name rather than Dear
Account.Name, because that could be either Dear First Last (impersonal), or Dear Acme, Inc. (even more impersonal when we know who the primary person was at the organization).
I also need the address block to have the name of the Primary contact role individual if there one.
So how do I do these 2 things? In Apsona, I do the following to get started:
1. Click into Apsona's "Opportunities" tab
2. Filter to see only the donations that still need to be thanks/receipted
3. Click Tools / Mail Merge
4. Create a new action
5. Specify a single .DOCX file
6. Begin mapping fields
And that's where I'm lost. All the merge fields have a mapped value, except for Apsona.FirstName (the name of the field in the Word template). When I look at the long, long list of all the data fields it has for me to pick from, I can't find anything for Contacts -- so there's no first name, no last name option; just account name. Nor am I able to find anything that would seem specific to the contact role marked Primary.
Any help much appreciated.
dt
#Donations #Donor Receipt #Receipt #ApsonaSince you're merging directly from the Opportunity object, you will only have access to the Opportunity fields and the fields of objects to which there are lookups from Opportunity, i.e., Account and Campaign. So you will need to create a report containing all the fields you need, so that you can merge from it.
Also, it looks like you need fields from Contact (such as First Name), Account (such as address), and Opportunity. That spans four objects - Opportunity, Contact Role, Contact and Account - and you cannot span those objects with a single-step report. So I would suggest creating a multi-step report containing all the fields you need, and running the merge from it.
Hope this helps!
We have a couple custom fields for tracking how to recognize a donation gift using
#NPSP. One is a checkbox to indicate whether the donation should be anonymous. The second field is a text box for entering free-form how the donation should be recognized in public materials (annual reports, etc.)
Our receipts still are addressed to the Opportunity Account Name, but our mail merge templates want to show the donor recognition status.
Setting up a workflow so that:
1. If Donation_is_Anonymous checkbox is checked, set the Recognize_Donation__c text box to the value "Anonymous"
2. If Donation_is_Anonymous checkbox is NOT checked, set the Recognize_Donation__c text box value to the opportunity's account name ONLY if nothing has already been entered into the Recognize_Donation__c text box.
That way, if it's anonymous, it uses Anonymous as the value, and if I specified no explicit recognition, it assumes the
account.name(which is the donor's 1:1 account or the entity if it's an organization's gift) is the donor to be recognized...unless I've indicated something else in the field. (Say, a wife and husband, or The xxx Family).
Formula is failing with "Error: Formula result is data type (Boolean), incompatible with expected data type (Text)."
IF ( Donation_is_Anonymous__c == TRUE,
Recognize_Donation__c = "Anonymous",
IF ( Recognize_Donation__c = "",
Recognize_Donation__c =
Account.Name,
Recognize_Donation__c = Recognize_Donation__c
)
)
, that ALMOST does it! I opted not to include it in the workflow criteria since it is conceivable that a user may check the anonymous box AND enter something into the Donor Recognition field. Illogical, but far more illogical things have been done in the harried times folks spend trying to rush through piles of donations to enter.
So the first test has to be against the anonymous checkbox as a business rule priority over whatever is entered into the field.
It seemed easy enough to fix the workflow using your guidance, and
@Ashima Saigal's, that I don't need to reference the object being updated. I would've expected it to work either way, but knowing that clears it up.
Now, it works fine most of the time, but not consistently after the record is created. I'll keep playing with it.
Thanks all for the help.
dt
