Skip to main content
Featured group

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.

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

2 answers
  1. Sep 1, 3:51 PM

    Try to use a None value for the Role field while creating/updating the user. If there is no flow/trigger/validation rule explictly make it required, it should work.

0/9000

----------

Error #1:

 

Error Type: Batch Apex error

Error Date: 2026-08-31 06:10:02

Message: "First error: [INACTIVE_OWNER_OR_USER] owner or user is inactive. Org Id:00DA0000000ANAI"

Context: npsp__CRLP_Account_AccSoftCredit_BATCH

 

Stack Trace:

null

2 answers
  1. Steven Trumble (Strum Consulting) Forum Ambassador
    Sep 1, 3:10 AM

    It's most likely this: 

     

    • Setup > Scheduled Jobs. If the NPSP rollup job was scheduled by a user who is now deactivated, delete all NPSP scheduled jobs running and that user. 
    • To recreate the scheduled jobs you just need to navigate to the NPSP app and the jobs will be rescheduled as your current running user. Best for this to be a system admin/someone with all the permissions required
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

11 answers
  1. Aug 31, 3:04 PM

     A custom object sounds like a good approach, especially if you want donor profiles to become searchable and reportable rather than keeping them as Word files. I’d also use Salesforce relationships to pull existing contact and giving data instead of duplicating it. For external nonprofit or organization research, something like the Nonprofit Check Plus API could potentially help automate verification and enrich profiles before Apsona merges everything into a final document. The key is designing the data model first, so you don’t end up recreating the same information in multiple places.

0/9000

Hi everyone,

I’m working on a solution to calculate the total giving influence (or "Impact") of a specific Contact Record Type we call "Members."

These Members are highly connected, and I need a single metric on their Contact record that captures their total impact across three different buckets:

  1. Direct Giving: Hard credits from their primary Household Account.
  2. Affiliated Giving: Hard credits from Organization Accounts they are affiliated with (e.g., their Company or their Family Foundation).
  3. Ad-Hoc Influence: Soft credits from Opportunities where they served as an influencer/solicitor but don't necessarily have an Account Affiliation.

Has anyone built something similar? If so, which route did you choose (Automated Soft Credits vs. DLRS/Flow)?

 

Double-counting gotchas:

What are the best practices/filter rules to ensure we don't double-count a Member if they accidentally get assigned a Soft Credit on a donation that is already rolling up through their Household or Affiliation? 

 

Thanks!

3 answers
  1. Aug 31, 1:19 PM

    Hi, for the bucket two soft credits in NPSP can be rollup by using the Opportunity Contact Role. When creating a Organization affiliation you can assigned a role (Soft Credit, desicion making, "Your own"), any opportunity/donation created for that organiation will create the soft credit. Then is just matter of filtering your roles accordingly. 

    If I remeber correctly, the household memebr roles is counted on the NPSP customizable roll ups so I edited my filter group to escluded that and avoind double counting hard credits in the household. 

    We also set up our own custom RFM score, so happy to share more on how we configured it

0/9000

I have searched on this error here and I'm not finding anything that exactly fits our situation.  Last month and this month we received an automated email.  The first time was on 12/15/2023, the second time was 1/8/2024.  The email lists 457 of the same error:

Error Type: Other

Error Date: 2024-01-07 06:00:25

Message: "field integrity exception (Guest users cannot be record owners.)"

Stack trace null

All 457 have the same date and time, but it doesn't give other details, like which records

After the December error, our Salesforce administrator searched and we don't seem to have any guest users owning any records.  Or any guest users.  We don't have any web forms.  We do have connections to Zapier and SoftEdge. Thoughts?

6 answers
  1. Aug 31, 6:46 AM

    Probably a bit late, but noticed that when guest users are deleting records, most proabaly from an automation trigger you will see this error. 

    I had a de-duplication automation running, if no duplicates it works fine but when it finds a duplicate and tries to delete one of them it errors out.

0/9000

We received the following error and I'm looking for guidance on how to address it. We noticed one of our NPSP Data Import Batch was deleted. Could this be related? Thank you.

Errors: 

 

---------- 

 Error #1: 

 

Error Type: Batch Apex error 

Error Date: 2026-08-21 06:21:59 

Message: "First error: [REQUEST_RUNNING_TOO_LONG] Your request was running for too long, and has been stopped." 

Context: npsp__CRLP_SkewDispatcher_BATCH 

 

Stack Trace: 

 null

3 answers
  1. Aug 25, 12:48 PM

    Hey Kathleen, 

     

    This is a genuine, documented pattern in NPSP's Customizable Rollups engine, CRLP_SkewDispatcher_BATCH timing out is unrelated to your Data Import Batch object being deleted. The Skew Dispatcher just processes rollup calculations for records with unusually high numbers of related transactions (like a household with thousands of donations), and it can occasionally hit Salesforce's platform-level batch timeout if there's a lot of data or a temporarily large batch to process, this is a known NPSP behavior, not a bug tied to your Data Import Batch. 

     

    Since it's happened once so far, per NPSP's own troubleshooting guidance, this is usually self-resolving on the next scheduled run, the job will simply retry that batch. Only worth investigating further if: 

    - It repeats consistently (not just once) 

    - You notice actual rollup values (like Total Gifts, Largest Gift, etc.) on Accounts/Contacts are stale or missing afterward 

     

    If you want to confirm nothing's actually broken, check Setup > Apex Jobs to see if npsp__CRLP_SkewDispatcher_BATCH completed successfully on a later scheduled run. If it did, no action needed. 

     

    On the deleted Data Import Batch: this error type has nothing to do with NPSP Data Import at all, that's a separate object/process entirely (Data Import handles Batch Gift Entry/Import records, Customizable Rollups handles donation summary calculations). If a Data Import Batch record actually got deleted, that would've required a manual delete or a separate automation/script, not something this rollup timeout would cause. 

     

    Reference:

    https://help.salesforce.com/s/articleView?id=sfdo.npsp_custom_rllps_jobs.htm&language=en_US&type=5

0/9000

Error Type: Other  

Error Date: 2026-08-19 03:00:02  

Message: "operation performed with inactive user [005C000000AYRGD] as owner of opportunity"?   

 

I searched the user and cannot find

feroze@freeartsnyc.org.

1 answer
  1. Aug 20, 5:26 PM

    Hi Tashiera - that error is NPSP's nightly job (runs around 3am) choking on an Opportunity owned by a deactivated user. 005C000000AYRGD is a User Id (the '005' prefix means User) - you cannot find 'feroze' because they are inactive. To see them, go to Setup - Users and switch the list view from 'Active Users' to 'All Users'. 

     

    Two things to fix, and your message ('...as owner of opportunity') points to the first: 

     

    1. Reassign the records they own. Build a report or list view of Opportunities where Owner = that inactive user, then reassign them to an active user (Setup - Mass Transfer Records, or Data Loader). Salesforce blocks operations on records owned by inactive users, which is exactly what the nightly rollup hits - once none are owned by that user, the 3am error stops. 

     

    2. While you are there, check the NPSP scheduled jobs' 'Submitted By'. If a default NPSP job was scheduled by that same inactive user, reschedule it: NPSP Settings - Bulk Data Processes - Batch Process Settings (recreating the default jobs runs them as an active user). 

     

    The emails go to whoever is set as the Error Notification recipient in NPSP Settings; they stop once the ownership (and any inactive-submitted job) is cleaned up. 

     

    If this helps, please mark it as the Best Answer so it helps the next person - thanks :)

0/9000

The past few days we've found that when exporting this report (NPSP Campaign Household Mailing List V2, there may be others too), the data in the file does not match what the report showed. 

 

This specifically happens when we have to do the step-up authentication. It's like some query piece is dropped when the step-auth passes the request back to SF. 

 

Has anyone else experienced this? Any fixes?

5 answers
  1. Aug 14, 1:48 PM

    I'm having this same issue on regular Sales Cloud. It also downloads the report twice. It seems that if I just wait a while after I make a change to the report that it will work properly, but it's so annoying! Was this not even tested before releasing?

0/9000

How do I fix the following error? 

 

Error Type: Batch Apex error 

Error Date: 2026-06-12 07:00:02 

Message: "First error: [INACTIVE_OWNER_OR_USER] owner or user is inactive. Org Id:00D5f000005w7px" 

Context: npsp__OPP_OpportunityNaming_BATCH 

 

Stack Trace: 

 null 

 

4 answers
0/9000

Doing a data migration of Recurring Donations and had to re-import some of them. 

Because I kept running into random nullpointer exceptions during the import (about 10% of the records each time, lowering batch sizes helped a little), I turned off the Recurring Donation trigger handlers for my user to import them. 

Once I was done, I turned them back on and ran the Recurring Donation Batch, which seemed to finish OK. 

Now for new annual recurring donations with an Effective Date in 2027, and one new monthly recurring donation with start date next month, NPSP did not populate the Next Donation Date or generate a schedule. Is this expected behaviour?

5 answers
  1. Aug 10, 2:09 PM

    I recommend you delete these RDs and redo the import with the triggers enabled.  NPSP has a protected object named RecurringDonationSchedule that you cannot access.  I'm guessing these RDs don't have their schedule records since you had disabled the NPSP triggers.

0/9000