Skip to main content
Content Starts Here
This is a publicly shared Knowledge Article from the Power of Us Hub - an online community for nonprofit and higher ed Salesforce users. Join the Hub .
Customer Service

Reporting Issues in NPSP and HEDA

Bugs happen, and telling us about issues you find is one of the best ways you can contribute to NPSP or HEDA. Thank you!

Since your Salesforce instance consists of many different pieces of functionality—some from the Salesforce platform, some from the NPSP or HEDA, and even some from other applications—it can be difficult to tell where a bug or unexpected behavior might be coming from. 

For fastest resolution, we recommend you take the following steps:
 
  1. Search the existing NPSP Known Issues or HEDA Known Issues to see if your issue has already been reported. 
  2. Search the Power of Us Hub for any error message you’re seeing. If it’s an issue outside your organization, there’s a great chance others are already talking about it.

    User-added image
     
  3. If you can’t find any suggested solutions or confirmation that it’s a bug, start a new post in the NPSP Group or HEDA Group in the Power of Us Hub. For best results:
     
    • If NPSP, State exactly what version of NPSP you are using, and which Account Model, if appropriate.
    • Describe in as much detail as you can exactly what steps you took, what you expected to happen, and what happened instead. 
    • Include screen shots! Click the Attach File link on your post to upload an image saved to your computer. To protect your constituent data, crop or blur to hide any personally identifiable information.

A member of the Salesforce.org Quality Assurance (QA) team will attempt to reproduce in a clean testing environment. If the team determines that it’s a bug or issue in the NPSP or HEDA code, they will enter it as an issue in Github so that it can be prioritized and resolved in an upcoming release.
Contributed by Judi Sohn
salesforce.com
First published April 28, 2017
Last modified May 2, 2017