Skip to content

3.146

Choose a tag to compare

@mrbelvedere mrbelvedere released this 09 Jan 18:41
· 26956 commits to master since this release
6e9b664

Critical Changes

To get started using Batch Gift Entry, you'll need to enable My Domain, expose the Batch Gift Entry tab and ensure that you have access to all related objects and fields.

In order to view the Batch Gift Entry app, My Domain must be enabled (if it isn't already). My Domain is a Salesforce Identity feature that adds a subdomain to your Salesforce org. It is required for features like Batch Gift Entry that are built using Lightning components in Lightning component tabs. To find out if My Domain is enabled in your org, go to Salesforce Setup and search for My Domain. For information on setting up My Domain, see My Domain.

We recommend that you create a permission set that includes the following:

  1. Batch Gift Entry tab setting set to Available, Visible
  2. Create and Edit access to the following objects. For NPSP Data Imports, also grant Delete access:
    • Accounts
    • Addresses
    • Contacts
    • NPSP Data Import Batches
    • NPSP Data Imports
    • Opportunities
    • Payments
  3. Edit access to these fields:
    • All NPSP Data Import fields
    • All NPSP Data Import Batch fields (Read only access to Gift Batch field)
    • Opportunity fields: Opportunity Amount and Opportunity Close Date
    • All fields you will select as part of the batch (during batch creation) and all fields that those fields map to (otherwise, users will only see the fields they have access to. For example, if your batch includes Donation Date and that field maps to Opportunity Close Date and Payment Date, then the user must have Edit access to all three fields.)
  4. Enable Visualforce Page Access for these pages:
    • BDI_BatchOverride
    • BDI_DataImport

For complete setup instructions, see Batch Gift Entry Setup.

Changes

Batch Gift Entry

An influx of donations is a good problem to have. It likely means that your quarterly (or annual) giving campaign went as well as (or better than) expected. And the large stack of checks that represent these donations is a wonderful thing, that is, unless you’re the sole person at your organization that is tasked with quickly and efficiently getting the data from those checks into your system. It’s tedious. It’s error prone. It’s a problem that needs solving. And fast.

Now, imagine you had a tool where you could quickly enter gift data in one form. One where you can define which fields to enter, and whether there should be defaults. One where you can search your database for a Contact or Account (to associate the donation with the right person), easily tab between cells (mouse free), and ensure you’re not entering duplicate donations. Think about the implications! This easy system would mean that you could enter all of the data in a snap! Or it might mean that you could share the data entry responsibilities with other teams since there wouldn't be a huge learning curve. Think of all the time that would free up…

Batch Gift Entry in NPSP is an easy-to-use tool for manually entering donations. Its simplicity makes it ideal for when you have a large number of gifts to enter and you need to do it fast. Batch Gift Entry provides the following capabilities:

  • Easily define the Opportunity and Payment fields to enter for a particular batch.
  • Search NPSP for existing Accounts or Contacts, to ensure that you associate each donation with the right person or organization.
  • No mouse required! Tab between fields to make data entry much faster.
  • Prevent duplicates by selecting from open donations (and updating them as needed).
  • Automatically check for potential errors when you save a gift to the batch.

If you started using NPSP prior to version 3.146, you'll need to perform some additional setup. For complete setup instructions, see Batch Gift Entry Setup. For information on creating batches and getting a kickstart on your batch gift entry, see Create Gift Batches.

Other Changes

  • NPSP no longer sends gift acknowledgement emails when the Opportunity's Acknowledgement Status field is set to "Acknowledged." Previously, it was possible to send multiple emails for the same gift.
  • To view Address Settings in NPSP Settings and run Health Check on address verification, users must now have the Customize Application system permission and Read, Create, and Delete permissions on the Address object.
  • We fixed a security issue with the deletion of NPSP Data Import records. After you click Delete All Data Import Records or Delete Imported Data Import Records, you will now be required to confirm deletion of records by clicking a Mass Delete button. Additionally, the Delete permission on the NPSP Data Imports object is now required to delete NPSP Data Import records. For information on deleting NPSP Data Import records, see the Administrator's Guide to Importing Donor Data.
  • Addressed security issues on the NPSP Relationships Viewer page.
  • Addressed security issues on NPSP Settings pages.
  • Addressed security issues on the Account Conversion page.
  • We added a TDTM trigger that deletes all related Payment Allocations when a Payment is deleted. This trigger was created to support a future feature and should have no visible impact.

Issues Closed

#2817: Affiliation auto creation is setting Status to Translated Value
#3747: Customizable Rollups Null Pointer Exception When RecordTypeId Referenced in Filter Rule with Null Value
#3761: Opportunity FMV Workflow Rule does not account for when Amount is $0 and FMV has not been populated
#3799: Contact Merge does not use Customizable Rollups for post-merge rollup fixing
#3843: Relationship Viewer Labels XSS Vulnerability
#3854: Customizable Rollups: Unexpected Filtering Results
#3860: Creating a new primary Affiliation is not changing prior Affiliation Status to Former or adding End Date value
#3949: Cascade delete Payment Allocations when related Payment is deleted

New Metadata

ApexComponents:

  • UTIL_PageMessageInfo

Lightning Components:

  • BGE_BatchGiftEntryTab
  • BGE_ConfigurationWizard
  • BGE_DataImportBatchEntry
  • BGE_DonationSelector
  • BGE_EntryForm
  • modalFooter
  • modalHeader

Classes:

  • BGE_BatchGiftEntry_UTIL.cls
  • BGE_ConfigurationWizard_CTRL.cls
  • BGE_ConfigurationWizard_CTRL_TEST.cls
  • BGE_DataImportBatchEntry_CTRL.cls
  • BGE_DataImportBatchEntry_CTRL_TEST.cls
  • PMT_CascadeDeleteLookups_TDTM.cls
  • PMT_CascadeDeleteLookups_TEST.cls

Lightning Pages:

  • Data_Import_Batch_Record_Home.flexipage

Tabs:

  • Batch_Gift_Entry.tab

Fields:

  • DataImportBatch__c.Active_Fields__c
  • DataImportBatch__c.Expected_Count_of_Gifts__c
  • DataImportBatch__c.Expected_Total_Batch_Amount__c
  • DataImportBatch__c.GiftBatch__c
  • DataImportBatch__c.RequireTotalMatch__c

Labels:

  • bdiMatchedApplyNewPayment
  • bdiMatchedByUser
  • bdiMatchedByUserNewOpp
  • bgeBatchAvailableFields
  • bgeBatchBatchProcessSizeHelp
  • bgeBatchDonationDateRangeHelp
  • bgeBatchDonationMatchingBehaviorHelp
  • bgeBatchDonationMatchingClassHelp
  • bgeBatchDonationMatchingRuleHelp
  • bgeBatchDonorLookupInfo
  • bgeBatchErrorRequiredFields
  • bgeBatchInfoWizard
  • bgeBatchOverview
  • bgeBatchOverviewWizard
  • bgeBatchPostProcessClassHelp
  • bgeBatchProcessUsingScheduledJobHelp
  • bgeBatchRunOpportunityRollupsWhileProcessingHelp
  • bgeBatchSelectFields
  • bgeBatchSelectedFields
  • bgeBatchSetBatchOptions
  • bgeBatchSetFieldOptions
  • bgeEditBatchFieldOptionsWarning
  • bgeEditBatchFieldSelectionWarning
  • bgeEditBatchOptionsWarning
  • bgeFLSError
  • bgeFormMatchingModalText
  • bgeFormNoneLink
  • bgeFormSelectedOpportunity
  • bgeFormSelectedPayment
  • bgeFormUpdateOpportunity
  • bgeFormUpdatePayment
  • bgeGridAllGifts
  • bgeGridDonorType
  • bgeGridErrorFromDryRun
  • bgeGridErrorRequiredTotalsExpected
  • bgeGridGiftCountHeader
  • bgeGridGiftDeleted
  • bgeGridGiftSaved
  • bgeGridGiftUpdated
  • bgeGridNoGiftsBody
  • bgeGridNoGiftsHeader
  • bgeGridTotalAmount
  • bgeGridTotalCount
  • bgeGridWarningRequiredTotalsExpected
  • bgeMatchingAlert
  • bgeMatchingSelect
  • bgeNewBatch
  • bgeNewGift
  • bgeProcessBatch
  • bgeTabHeader
  • stgBtnBack
  • stgClearErrors
  • stgDefaultValue
  • stgLabelField
  • stgLabelHidden
  • stgLabelObject
  • stgAddrPermissionDenied
  • sendAcknowledgmentNumberAlreadySent

Installation Info

Push Schedule

Sandbox orgs: 2019-01-09
Production orgs: 2019-01-15
Use the Installation URL below to install this release before the scheduled push dates.

Installation URL

https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1Y0000011Sz3QAE

Trialforce Template ID

0TT1I000006WS53