Skip to main content
Vorgestellte Gruppe

Nonprofit Success Pack

The Nonprofit Success Pack (NPSP) is a series of managed packages, installed on top of Salesforce Enterprise Edition. The 6 packages of the NPSP make it easier for you to use Salesforce to manage the core relationships between individual donors, their households, and the companies they work for. Use this group for questions and discussion about the Nonprofit Success Pack.

Our Philanthropy team are seeking a solution for capturing and recording engagements with donors (meetings, events, etc) to be viewed alongside Opportunities and households.  

 

The team have found that tasks and activities are not achieving this, and speaking with Salesforce they recommend building a custom object to mimic an object only available in Non Profit Cloud.  

 

Before we proceed with investigation into this, it would be great to connect with other NPSP users who have a similar business requirement who may have implemented something like this. Do you have any recommendations for how to achieve this?  

 

Thank you

0/9000

We have contacts that are grant writers in SF that have multiple affiliations with NPO's. The issue is that the contact has created a portal account for each org to submit a grant application using emails associated with each NPO. We are unable to merge the contacts without disabling the portal access. What are other NPO's that have grant programs doing to manage these duplicate records?  

 

I've seen posts that recommend making the duplicated records members of the household, is this the best way to handle this issue without losing the grant writer's history for portal access?

1 Antwort
  1. Gestern 01:58

    Hi @Karen Hartt

     

     

    Since each portal account uses a different NPO email, Salesforce won't flag them as duplicates automatically, that's a process problem, not a matching-rule problem, so no dedupe setting fixes it. I have seen this with one of the association I was working with.

    Options: 

    • Ask at the application stage. Add a question to the grant application form: "Are you already a registered user with us?" If yes, capture their existing email/username and route the new application to that existing Contact/portal account instead of creating a new one.
    • Match on identity, not just NPO relationship. Before granting portal access, check for an existing Contact by name + personal email or phone, not just the NPO-specific email. If found, add the new NPO affiliation to that existing Contact rather than creating a second one.
    • One portal login, multiple affiliations. If your portal license allows it, let one Contact log in once and see/submit applications for every NPO they're affiliated with, instead of a separate login per NPO. This removes the reason to duplicate in the first place.
    • If separate logins are unavoidable (portal architecture requires one Contact per login), don't merge instead, link the duplicate Contacts to each other (a custom "Related Person" or NPSP Relationship record) so staff can see they're the same human, and report on them as one person via that link rather than via Contact merge.
0/9000

For the past 6 weeks or so I've been getting nightly head size errors for the NPSP rollup above. I have reduced the batch size several times with no effect. 

Searching this site and elsewhere on the internet has not yielded a solution. Maybe this problem will go away in Winter '27 when heap sizes are increased, but I want to know why it is happening and if there  is anything I can do to address it

1 Antwort
  1. 20. Sept., 17:22

    Hi Laurel! One of the things I've seen cause this are contacts that should

    be moved to the skew processing but are not. This means that they have a LOT of child opportunities. NPSP has a special mode to account for this, but if I remember correctly it's only based on the number of closed opps.  

     

    This can happen for a number of reasons. What I've seen most often is if you have some contacts with a lot of OPEN opportunities, or if you use placeholder contacts that have a lot of related opps and they didn't get updated automatically to go into skew processing mode, you can get these errors.  

     

    Adjusting batch sizes can temporarily resolve the issue sometimes, but you have to adjust them WAY down.  

     

    This is the query that I run in client orgs first to see if there are any standouts. If so I adjust the UseSkewMode field from the query to 'True' for these contacts and then see if the heap issues disappear.  

     

    SELECT ContactId, COUNT(Id) ActualOppsCount

    FROM OpportunityContactRole WHERE Contact.npsp__CustomizableRollups_UseSkewMode__c = false

    GROUP BY ContactId

    HAVING COUNT(Id) > 250

    ORDER BY COUNT(Id) DESC

    LIMIT 2000

     

    There are certainly other reasons you might get this. Having a large number of, or overly complex, npsp rollups defined and active can do it.  

     

    Theoretically you could run into this issue if you have competing scheduled jobs (non-npsp jobs) scheduled at the same time, in which case both are competing for resources. If you run the job manually and it works without issue, this might be a place to look. 

     

    If the above doesn't square things away, look at follow-up automation that triggers on the contact record update. Make sure your flows / apex have clear entrance criteria and leverage asynchronous paths where possible, so that you don't have a lot of automations triggering at the same time (in the same transaction, which is what the heap size limit is based on). 

     

    You can also likely help this run smoothly by verifying that your Setup - Custom Settings - Customizable Rollup Settings have 'Incremental Contact Hard Credit Non-Skew' set to TRUE - which tells salesforce to only update the contacts that had records change since the last run.  

     

    Hopefully one of these gets you squared away.  

     

0/9000
When updating the default address on a Household account, the Mailing Address for the related Contacts is update as well. This works for most accounts...but I have identified a few that aren't working and I can't figure out why or how they are different from the accounts which work as expected.
9 Antworten
  1. 18. Sept., 18:05

    @Eric Pohlabel @Ankur Jain

     Hello from the future. Did you figure this out? I was running into a similar situation and discovered that somehow the seasonal address fields had been set to use an old address for month 1 to month 12, and all days. When I updated those fields to be empty the addresses updated everywhere else as expected.   

    Not sure if this is the same situation, but I felt the need to share after spending some time searching through trailhead for similar issues.  

0/9000
1 Antwort
  1. 17. Sept., 19:03

    You posted this in the NPSP group so first question... are you a System Administrator? If so, when you go to Setup > Object Manager > Leads > Buttons, Links and Actions and click the drop down to the right and "Edit" what do you see under "Salesforce Classic Override"? 

     

    In terms of NPSP "coaching clients" isn't something out of the box, so you will need to provide more information on your lead conversion process. Does this error only happen with certain leads? If so, what makes these different?

0/9000

We'd like to turn on the setting to use SLDS 2 for pages that include <apex:slds> when an SLDS 2 theme is active in User Interface in order to take advantage of dark mode and SLDS 2 for our custom Visualforce pages. 

 

However, when we do so, some of our managed package Visualforce pages have significantly degraded appearance. This includes Salesforce's Nonprofit Success Pack Contact Merge page in particular.  

 

Is there a way to enable SLDS 2 on particular Visualforce pages (the ones we have control over) and leave SLDS 1 for the managed package ones that we can't update (and may not be able to get Salesforce to update)? It looks like there is a way to force <apex:slds> to use SLDS 1, but that doesn't really help us as we can't edit the managed packaged pages where that would be necessary. 

 

I can try opening a Salesforce support case, but since they started replacing everything with AI, it's been much more difficult to get a decent response. I suspect the answer will be to create an Idea, which will then languish for years or just be closed (which doesn't really help solve our problem).  

 

@Nonprofit Success Pack @Design Trailblazers

1 Antwort
  1. 16. Sept., 21:21

    Hi , 

     

     

    Unfortunately, I don't believe Salesforce currently provides a way to selectively enable SLDS 2 for some Visualforce pages while forcing managed-package Visualforce pages to remain on SLDS 1. If a managed package page such as NPSP Contact Merge is broken by SLDS 2, this is likely an issue that must be addressed by the package provider or Salesforce itself.

0/9000

We currently create our donor research profiles in Word and attach them as Files to Account records. The profile contains Contact info (name, email, phone, mailing address), some giving history, and data from external sources. We would like to transition this to Salesforce. My preliminary idea is a custom object with fields for data that doesn't already live somewhere else, then some sort of mail merge tool (we have Apsona) that merges it all together in one document. Has anyone built anything like this,or used a third party tool they recommend?  

 

We are on NPSP with no immediate plans to move to NPC.

@Nonprofit Success Pack #Nonprofit Success Pack

12 Antworten
  1. 15. Sept., 12:20

    A custom object sounds like a great approach here. I have seen organisations struggle when donor research ends up scattered across Word documents. Moving that information into a structured Salesforce object can make reporting much easier. You could use a rich text field for the narrative sections while keeping key research details in dedicated fields. External data merging may still require a separate tool, but native Salesforce fields will give you a much stronger foundation. This sort of strategy usually pays off in the long term.

0/9000

Hi all,

Wondering if anyone uses Formstack to/from Salesforce. We have a weird issue arising. We have a Youth consent form for parents to sign for youth taking classes. They need to sign this at least twice a year if they are taking additional classes in a different month. We have it set up to pull the data from the record into the form if they have completed it before - totally fine.

We did not have it set up previously to update the submitted date on the contact record. Now I have that box checked on JUST that field. The checkbox is "Update existing Salesforce record matching this field value:"

I haven't hit this button on any other field so that we don't have blanks erasing previously provided information.

We now have an issue popping up where the birthdate is then changed to blank when the new form is submitted. It is not a required field and I do not have the box checked to update the field upon resubmission. The weird thing is that when I see a record where the birthdate was removed, I go to the form submission and the birthdate is there pre-filled in the form.

Any thoughts? I'm hoping the checkbox update for just the date field isn't causing the issue here. I'm going to reach out to formstack support to, but wanted to check in and see if anyone has run into this issue before.

4 Antworten
  1. 13. Sept., 13:17

    We kept the form side separate and used Skyvia for the Salesforce update, with only the fields we actually wanted mapped for update. That gave us a lot more control than letting the form integration write back to the whole record.

0/9000

How to delete NPSP Data Import records before the final Import?

Ran NPSP Data Import and found some blank data was imported. The next day, deleted the records and checked from "All" that the records were deleted. Ran NPSP Data Import ensure the correct number of records were import. When trying to take the next step of Data Import, no records were found. 

Ran NPSP Data Import records and all the records were found but not available for Importing.

Can all the 2 days of records be completely deleted and start a new import?

 

@Fundraising

@Nonprofit Success Pack

@Salesforce.org System Administrators

4 Antworten
  1. 9. Sept., 09:37

    This was the solution that worked for me.  I had two thousand records needed to delete after I discovered a mistake in the data I was going to import.  I created a report on the NPSP Date Import object to include the records I wanted to delete.  Make sure you include the Salesforce Record ID, the Import ID will not work.  With Salesforce Record ID  in hand I used Dataloader to delete the import records,

0/9000

Has anyone else come across the issue where the user role is now required? My org doesn't really use them except in specific circumstances for our Development officers (my previous org didn't use them at all so I know I'm not alone in this). I noticed in August when I was reactivating a user with a standard license and was forced to pick something. It did the same thing when I created a new user (also with a standard license) as well. It defaults to the first choice on the list if you have any roles created, and I can't select none.  

 

I asked SF Support when I couldn't find any documentation on it. They thought it might have been a setting I turned on, but were surprised when they opened their own demo org and saw that it was required for them too. They told me this morning that they were asking some higher ups about it. 

 

I've attached screenshots of my account where you can see that when my account was created, a role was not selected but if I were to edit it, it defaults to the first choice on the list and is required. 

 

@* Salesforce Administrators * @Nonprofit Success Pack @Admin Addicts

3 Antworten
  1. 8. Sept., 13:34

    I've run into a similar issue. We also do not utilize roles. I had a non-sys admin who was responsible for creating new user records, and he had permissions via the manage internal users permission. I forget when it started, one day he could no longer save new records. He could still edit existing ones. I am pretty sure it is also related to roles. He did not have the 'not specified' option that I see as an admin.  Nothing we tried restored his ability to create new user records, but we did not bother calling Salesforce for it, maybe we should have?  I created a screen flow that he now uses to create new user records.

0/9000