Book Image

Accelerating Nonprofit Impact with Salesforce

By : Melissa Hill Dees
Book Image

Accelerating Nonprofit Impact with Salesforce

By: Melissa Hill Dees

Overview of this book

Salesforce Nonprofit Cloud enables a 360-degree view of people related to your nonprofit to connect fundraising, program management, and grantmaking. With a single, unified view of every interaction with constituents, nonprofits can create strong relationships with the community and streamline internal processes. The book starts by covering the tools and features that make up Nonprofit Cloud, helping you understand their standard functionalities and how Nonprofit Success Pack's (NPSP) data architecture is critical to implementation. You’ll learn how the Nonprofit Cloud Program Management Module can connect your programs, automate case management, and track client progress. Next, you’ll explore the tools for creating a change management process to increase user adoption. Moving ahead, you’ll understand how to configure necessary permissions for NPSP administration and explore how declarative tools help better align the goals of a nonprofit organization. Toward the concluding chapters, you’ll cover customizations, deployment, custom reports, and dashboards for fundraising analytics, as well as best practices for data management to maintain its integrity. By the end of this Salesforce book, you’ll be able to build and configure the Nonprofit Cloud for a variety of use cases to achieve maximum social impact with the least amount of technical debt.
Table of Contents (21 chapters)
1
Section 1: Get Ready – Learn the Basics of NPSP
8
Section 2: Get Set – Correlating Need with Nonprofit Cloud Tools
14
Section 3: Go! – Data for Impact

Order of execution

Order of execution is one of the single most important concepts in Salesforce as a whole. From what we have learned about TDTM and how it helps configure the order of execution for triggers, you should have a better understanding of how important the order of execution is. Triggers are only one part of the larger puzzle. You may want to familiarize yourself with the order that things happen and when they happen.

The list is long, and the considerations are many. At a high level, here is what the order of execution looks like when you save a record:

  1. Loads the original record from the database or initializes the record for an upsert statement.
  2. Loads the new record field values from the request and overwrites the old values.
  3. Executes record-triggered flows that are configured to run before the record is saved.
  4. Executes all previous triggers.
  5. Runs most system validation steps again, such as verifying that all required fields. have a non-null...