3.149

Critical Changes

If you use Batch Gift Entry, you must give users Edit access to these new fields:

• Donation Campaign Source
• Donation Campaign Import Status

Changes

Batch Gift Entry Enhancements

• In the NPSP Data Importer, we expanded Campaign Matching during donation import by allowing you to specify a Campaign by ID instead of relying on matching logic. To take advantage of this functionality, you'll need to add a Donation Campaign Source column to your Data Import template. You can then copy the ID from a Campaign record's URL into the Donation Campaign Source field in the row for each related Donation. Note that if a data import row contains values in both the Donation Campaign Source field and the Donation Campaign Name field, NPSP will match using the Donation Campaign Source. There is also a new Donation Campaign Import Status field on the data import record that indicates if NPSP found a matching Campaign during dry run or processing.

  IMPORTANT: We are mapping the help text of the new Donation Campaign Source field to the Opportunity.CampaignId. If you already mapped help text that maps to the Opportunity.CampaignId, we recommend that you remove it.

• You can now associate a Donation with a Campaign in your Batch Gift Entry batches. When creating a batch, simply add the Donation Campaign Source field, and if needed, set a default Campaign for the entire batch. The Donation Campaign Source field is a lookup, so you can choose from a list of available Campaigns when entering a gift. When you process the batch, the Campaign selected populates the Primary Campaign ID field on the resulting Opportunity.

• In Batch Gift Entry, you can now apply a new Payment to an open Opportunity. The Apply New Payment option is available in the Review Donations pop up for open Opportunities that don't have any Payments at all or whose Payments are all marked as Paid. When you process a batch with a new Payment, the new Payment is related to the Opportunity record and marked as Paid. Additionally, if the new Payment makes the sum of all Paid Payments equal to the Opportunity Amount, the Opportunity status is changed to Closed Won.

• The Donation Record Type Name field now works properly in Batch Gift Entry for all orgs. This field has a hard coded mapping to the Opportunity Record Type field. If there is help text for the Donation Record Type Name field that appears to map it elsewhere, that help text is ignored.

Other Enhancements

• There is now support for disabling TDTM triggers within a given execution context. This is implemented using a new Global Class called Callable_API that implements the System.Callable interface. It currently supports the TDTM.DisableAllTriggers action.

Issues Closed

#4068: Users without delete permissions on manage allocations do not see warning message

New Metadata

Fields:

• DataImport__c.DonationCampaignImported__c
• DataImport__c.DonationCampaignImportStatus__c

Classes:

• Callable_API.cls
• Callable_API_TEST.cls
• OPP_StageToStateMapping_API.cls
• OPP_StageToStateMapping_API_TEST.cls

Custom Labels:

• CallableApiMethodNotImplemented

Installation Info

Push Schedule

Sandbox orgs: 2019-03-06
Production orgs: 2019-03-12
Use the Installation URL below to install this release before the scheduled push dates.

Installation URL

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

Trialforce Template ID

0TT1I000006ZSnT

3.150 (Beta 2)

Release of version 3.150 (Beta 2)

dependencies: [
    {
        "name": "Install Households 3.11",
        "namespace": "npo02",
        "version": "3.11",
        "dependencies": [
            {
                "name": "Install Contacts & Organizations 3.11",
                "namespace": "npe01",
                "version": "3.11"
            }
        ]
    },
    {
        "name": "Install Recurring Donations 3.13",
        "namespace": "npe03",
        "version": "3.13"
    },
    {
        "name": "Install Relationships 3.8",
        "namespace": "npe4",
        "version": "3.8"
    },
    {
        "name": "Install Affiliations 3.7",
        "namespace": "npe5",
        "version": "3.7"
    }
]

3.150 (Beta 1)

Release of version 3.150 (Beta 1)

dependencies: [
    {
        "name": "Install Households 3.11",
        "namespace": "npo02",
        "version": "3.11",
        "dependencies": [
            {
                "name": "Install Contacts & Organizations 3.11",
                "namespace": "npe01",
                "version": "3.11"
            }
        ]
    },
    {
        "name": "Install Recurring Donations 3.13",
        "namespace": "npe03",
        "version": "3.13"
    },
    {
        "name": "Install Relationships 3.8",
        "namespace": "npe4",
        "version": "3.8"
    },
    {
        "name": "Install Affiliations 3.7",
        "namespace": "npe5",
        "version": "3.7"
    }
]

3.149 (Beta 16)

Changes

• In the NPSP Data Importer, we expanded Campaign Matching during donation import by allowing you to specify a Campaign by ID instead of relying on matching logic. To take advantage of this functionality, you'll need to add a Donation Campaign Source column to your Data Import template. You can then copy the ID from a Campaign record's URL into the Donation Campaign Source field in the row for each related Donation. Note that if a data import row contains values in both the Donation Campaign Source field and the Donation Campaign Name field, NPSP will match using the Donation Campaign Source. There is also a new Donation Campaign Import Status field on the data import record that indicates if NPSP found a matching Campaign during dry run or processing. [PR4044]
  IMPORTANT: We are mapping the help text of the new Donation Campaign Source field to the Opportunity.CampaignId. If you already mapped help text that maps to the Opportunity.CampaignId, we recommend that you remove it. [PR4044]
• There is now support for disabling TDTM triggers within a given execution context. This is implemented using a new Global Class called Callable_API that implements the System.Callable interface. It currently supports the TDTM.DisableAllTriggers action. [PR4046]
• You can now associate a Donation with a Campaign in your Batch Gift Entry batches. When creating a batch, simply add the Donation Campaign Source field, and if needed, set a default Campaign for the entire batch. The Donation Campaign Source field is a lookup, so you can choose from a list of available Campaigns when entering a gift. When you process the batch, the Campaign selected populates the Primary Campaign ID field on the resulting Opportunity. [PR4055]
• In Batch Gift Entry, you can now apply a new Payment to an open Opportunity. The Apply New Payment option is available in the Review Donations pop up for open Opportunities that don't have any Payments at all or whose Payments are all marked as Paid. When you process a batch with a new Payment, the new Payment is related to the Opportunity record and marked as Paid. Additionally, if the new Payment makes the sum of all Paid Payments equal to the Opportunity Amount, the Opportunity status is changed to Closed Won. [PR4078]
• The Donation Record Type Name field now works properly in Batch Gift Entry for all orgs. This field has a hard coded mapping to the Opportunity Record Type field. If there is help text for the Donation Record Type Name field that appears to map it elsewhere, that help text is ignored. [PR4081]

Issues Closed

#4068: Users without delete permissions on manage allocations do not see warning message [PR4069]

New Metadata

• CallableApi.cls [PR4046]
• CallableApi_TEST.cls [PR4046]
• OPP_StageToStateMapping_API.cls [PR4046]
• OPP_StageToStateMapping_API_TEST.cls [PR4046]
• CallableApiMethodNotImplemented Custom label [PR4046]
  Fields: [PR4046]
• npo02__Households_Settings__c.Opportunity_Committed_Stages__c [PR4046]
• npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4046]

Deleted Metadata

Removed npo02__Households_Settings__c.Opportunity_Committed_Stages__c and npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4092]

3.149 (Beta 15)

Changes

• In the NPSP Data Importer, we expanded Campaign Matching during donation import by allowing you to specify a Campaign by ID instead of relying on matching logic. To take advantage of this functionality, you'll need to add a Donation Campaign Source column to your Data Import template. You can then copy the ID from a Campaign record's URL into the Donation Campaign Source field in the row for each related Donation. Note that if a data import row contains values in both the Donation Campaign Source field and the Donation Campaign Name field, NPSP will match using the Donation Campaign Source. There is also a new Donation Campaign Import Status field on the data import record that indicates if NPSP found a matching Campaign during dry run or processing. [PR4044]
  IMPORTANT: We are mapping the help text of the new Donation Campaign Source field to the Opportunity.CampaignId. If you already mapped help text that maps to the Opportunity.CampaignId, we recommend that you remove it. [PR4044]
• Created a new Global Class called CallableApi that implements the System.Callable interface. It currently supports the 'TDTM.disableAllTriggers' action. [PR4046]
• Added a new public method disableAllTriggers to the TDTM_Config_API class to allow users to disable all TDTM triggers for the current execution context. [PR4046]
• You can now associate a Donation with a Campaign in your Batch Gift Entry batches. When creating a batch, simply add the Donation Campaign Source field, and if needed, set a default Campaign for the entire batch. The Donation Campaign Source field is a lookup, so you can choose from a list of available Campaigns when entering a gift. When you process the batch, the Campaign selected populates the Primary Campaign ID field on the resulting Opportunity. [PR4055]
• In Batch Gift Entry, you can now apply a new Payment to an open Opportunity. The Apply New Payment option is available in the Review Donations pop up for open Opportunities that don't have any Payments at all or whose Payments are all marked as Paid. When you process a batch with a new Payment, the new Payment is related to the Opportunity record and marked as Paid. Additionally, if the new Payment makes the sum of all Paid Payments equal to the Opportunity Amount, the Opportunity status is changed to Closed Won. [PR4078]
  --Donation Record Type works in all orgs, regardless of help text mapping. [PR4081]

Issues Closed

#4068: Users without delete permissions on manage allocations do not see warning message [PR4069]

New Metadata

• CallableApi.cls [PR4046]
• CallableApi_TEST.cls [PR4046]
• OPP_StageToStateMapping_API.cls [PR4046]
• OPP_StageToStateMapping_API_TEST.cls [PR4046]
• CallableApiMethodNotImplemented Custom label [PR4046]
  Fields: [PR4046]
• npo02__Households_Settings__c.Opportunity_Committed_Stages__c [PR4046]
• npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4046]

Deleted Metadata

Removed npo02__Households_Settings__c.Opportunity_Committed_Stages__c and npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4092]

3.149 (Beta 14)

Changes

• In the NPSP Data Importer, we expanded Campaign Matching during donation import by allowing you to specify a Campaign by ID instead of relying on matching logic. To take advantage of this functionality, you'll need to add a Donation Campaign Source column to your Data Import template. You can then copy the ID from a Campaign record's URL into the Donation Campaign Source field in the row for each related Donation. Note that if a data import row contains values in both the Donation Campaign Source field and the Donation Campaign Name field, NPSP will match using the Donation Campaign Source. There is also a new Donation Campaign Import Status field on the data import record that indicates if NPSP found a matching Campaign during dry run or processing. [PR4044]
  IMPORTANT: We are mapping the help text of the new Donation Campaign Source field to the Opportunity.CampaignId. If you already mapped help text that maps to the Opportunity.CampaignId, we recommend that you remove it. [PR4044]
• Created a new Global Class called CallableApi that implements the System.Callable interface. It currently supports the 'TDTM.disableAllTriggers' action. [PR4046]
• Added a new public method disableAllTriggers to the TDTM_Config_API class to allow users to disable all TDTM triggers for the current execution context. [PR4046]
• You can now associate a Donation with a Campaign in your Batch Gift Entry batches. When creating a batch, simply add the Donation Campaign Source field, and if needed, set a default Campaign for the entire batch. The Donation Campaign Source field is a lookup, so you can choose from a list of available Campaigns when entering a gift. When you process the batch, the Campaign selected populates the Primary Campaign ID field on the resulting Opportunity. [PR4055]
• Fixed a scroll issue in the Donation Matching Rule dual picklist [PR4067]
• Fix issue where save button was not reenabling after BGE entry form save [PR4076]
• Allows Users to apply a new Payment to an existing Opportunity in Batch Gift Entry [PR4078]
  --Donation Record Type works in all orgs, regardless of help text mapping. [PR4081]

• updated the robot_libdoc task to generate documentation for both NPSP.robot and NPSP.py [PR4091]

Issues Closed

#4068: Users without delete permissions on manage allocations do not see warning message [PR4069]

New Metadata

• CallableApi.cls [PR4046]
• CallableApi_TEST.cls [PR4046]
• OPP_StageToStateMapping_API.cls [PR4046]
• OPP_StageToStateMapping_API_TEST.cls [PR4046]
• CallableApiMethodNotImplemented Custom label [PR4046]
  Fields: [PR4046]
• npo02__Households_Settings__c.Opportunity_Committed_Stages__c [PR4046]
• npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4046]

Deleted Metadata

Removed npo02__Households_Settings__c.Opportunity_Committed_Stages__c and npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4092]

3.149 (Beta 13)

Changes

• In the NPSP Data Importer, we expanded Campaign Matching during donation import by allowing you to specify a Campaign by ID instead of relying on matching logic. To take advantage of this functionality, you'll need to add a Donation Campaign Source column to your Data Import template. You can then copy the ID from a Campaign record's URL into the Donation Campaign Source field in the row for each related Donation. Note that if a data import row contains values in both the Donation Campaign Source field and the Donation Campaign Name field, NPSP will match using the Donation Campaign Source. There is also a new Donation Campaign Import Status field on the data import record that indicates if NPSP found a matching Campaign during dry run or processing. [PR4044]
  IMPORTANT: We are mapping the help text of the new Donation Campaign Source field to the Opportunity.CampaignId. If you already mapped help text that maps to the Opportunity.CampaignId, we recommend that you remove it. [PR4044]
• Created a new Global Class called CallableApi that implements the System.Callable interface. It currently supports the 'TDTM.disableAllTriggers' action. [PR4046]
• Added a new public method disableAllTriggers to the TDTM_Config_API class to allow users to disable all TDTM triggers for the current execution context. [PR4046]
• You may notice two new fields on the Household Settings custom settings page: Opportunity Committed Stage and Opportunity Finalized Stage. These fields were created to support a future feature and shouldn't be used until the feature is released. Please ignore the fields for now. [PR4046]
• You can now associate a Donation with a Campaign in your Batch Gift Entry batches. When creating a batch, simply add the Donation Campaign Source field, and if needed, set a default Campaign for the entire batch. The Donation Campaign Source field is a lookup, so you can choose from a list of available Campaigns when entering a gift. When you process the batch, the Campaign selected populates the Primary Campaign ID field on the resulting Opportunity. [PR4055]
• Fixed a scroll issue in the Donation Matching Rule dual picklist [PR4067]
• Fix issue where save button was not reenabling after BGE entry form save [PR4076]
• Allows Users to apply a new Payment to an existing Opportunity in Batch Gift Entry [PR4078]
  --Donation Record Type works in all orgs, regardless of help text mapping. [PR4081]

• updated the robot_libdoc task to generate documentation for both NPSP.robot and NPSP.py [PR4091]

Issues Closed

#4068: Users without delete permissions on manage allocations do not see warning message [PR4069]

New Metadata

• CallableApi.cls [PR4046]
• CallableApi_TEST.cls [PR4046]
• OPP_StageToStateMapping_API.cls [PR4046]
• OPP_StageToStateMapping_API_TEST.cls [PR4046]
• CallableApiMethodNotImplemented Custom label [PR4046]
  Fields: [PR4046]
• npo02__Households_Settings__c.Opportunity_Committed_Stages__c [PR4046]
• npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4046]

Deleted Metadata

Removed npo02__Households_Settings__c.Opportunity_Committed_Stages__c and npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4092]

3.149 (Beta 12)

Changes

• In the NPSP Data Importer, we expanded Campaign Matching during donation import by allowing you to specify a Campaign by ID instead of relying on matching logic. To take advantage of this functionality, you'll need to add a Donation Campaign Source column to your Data Import template. You can then copy the ID from a Campaign record's URL into the Donation Campaign Source field in the row for each related Donation. Note that if a data import row contains values in both the Donation Campaign Source field and the Donation Campaign Name field, NPSP will match using the Donation Campaign Source. There is also a new Donation Campaign Import Status field on the data import record that indicates if NPSP found a matching Campaign during dry run or processing. [PR4044]
  IMPORTANT: We are mapping the help text of the new Donation Campaign Source field to the Opportunity.CampaignId. If you already mapped help text that maps to the Opportunity.CampaignId, we recommend that you remove it. [PR4044]
• Created a new Global Class called CallableApi that implements the System.Callable interface. It currently supports the 'TDTM.disableAllTriggers' action. [PR4046]
• Added a new public method disableAllTriggers to the TDTM_Config_API class to allow users to disable all TDTM triggers for the current execution context. [PR4046]
• You may notice two new fields on the Household Settings custom settings page: Opportunity Committed Stage and Opportunity Finalized Stage. These fields were created to support a future feature and shouldn't be used until the feature is released. Please ignore the fields for now. [PR4046]
• You can now associate a Donation with a Campaign in your Batch Gift Entry batches. When creating a batch, simply add the Donation Campaign Source field, and if needed, set a default Campaign for the entire batch. The Donation Campaign Source field is a lookup, so you can choose from a list of available Campaigns when entering a gift. When you process the batch, the Campaign selected populates the Primary Campaign ID field on the resulting Opportunity. [PR4055]
• Fixed a scroll issue in the Donation Matching Rule dual picklist [PR4067]
• Fix issue where save button was not reenabling after BGE entry form save [PR4076]
• Allows Users to apply a new Payment to an existing Opportunity in Batch Gift Entry [PR4078]
  --Donation Record Type works in all orgs, regardless of help text mapping. [PR4081]

• updated the robot_libdoc task to generate documentation for both NPSP.robot and NPSP.py [PR4091]

Issues Closed

#4068: Users without delete permissions on manage allocations do not see warning message [PR4069]

New Metadata

• CallableApi.cls [PR4046]
• CallableApi_TEST.cls [PR4046]
• OPP_StageToStateMapping_API.cls [PR4046]
• OPP_StageToStateMapping_API_TEST.cls [PR4046]
• CallableApiMethodNotImplemented Custom label [PR4046]
  Fields: [PR4046]
• npo02__Households_Settings__c.Opportunity_Committed_Stages__c [PR4046]
• npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4046]

3.149 (Beta 9)

Changes

• In the NPSP Data Importer, we expanded Campaign Matching during donation import by allowing you to specify a Campaign by ID instead of relying on matching logic. To take advantage of this functionality, you'll need to add a Donation Campaign Source column to your Data Import template. You can then copy the ID from a Campaign record's URL into the Donation Campaign Source field in the row for each related Donation. Note that if a data import row contains values in both the Donation Campaign Source field and the Donation Campaign Name field, NPSP will match using the Donation Campaign Source. There is also a new Donation Campaign Import Status field on the data import record that indicates if NPSP found a matching Campaign during dry run or processing. [PR4044]
  IMPORTANT: We are mapping the help text of the new Donation Campaign Source field to the Opportunity.CampaignId. If you already mapped help text that maps to the Opportunity.CampaignId, we recommend that you remove it. [PR4044]
• Created a new Global Class called CallableApi that implements the System.Callable interface. It currently supports the 'TDTM.disableAllTriggers' action. [PR4046]
• Added a new public method disableAllTriggers to the TDTM_Config_API class to allow users to disable all TDTM triggers for the current execution context. [PR4046]
• You may notice two new fields on the Household Settings custom settings page: Opportunity Committed Stage and Opportunity Finalized Stage. These fields were created to support a future feature and shouldn't be used until the feature is released. Please ignore the fields for now. [PR4046]
• You can now associate a Donation with a Campaign in your Batch Gift Entry batches. When creating a batch, simply add the Donation Campaign Source field, and if needed, set a default Campaign for the entire batch. The Donation Campaign Source field is a lookup, so you can choose from a list of available Campaigns when entering a gift. When you process the batch, the Campaign selected populates the Primary Campaign ID field on the resulting Opportunity. [PR4055]
• Fix issue where save button was not reenabling after BGE entry form save [PR4076]
  --Donation Record Type works in all orgs, regardless of help text mapping. [PR4081]

Issues Closed

#4068: Users without delete permissions on manage allocations do not see warning message [PR4069]

New Metadata

• CallableApi.cls [PR4046]
• CallableApi_TEST.cls [PR4046]
• OPP_StageToStateMapping_API.cls [PR4046]
• OPP_StageToStateMapping_API_TEST.cls [PR4046]
• CallableApiMethodNotImplemented Custom label [PR4046]
  Fields: [PR4046]
• npo02__Households_Settings__c.Opportunity_Committed_Stages__c [PR4046]
• npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4046]

3.149 (Beta 11)

Changes

• In the NPSP Data Importer, we expanded Campaign Matching during donation import by allowing you to specify a Campaign by ID instead of relying on matching logic. To take advantage of this functionality, you'll need to add a Donation Campaign Source column to your Data Import template. You can then copy the ID from a Campaign record's URL into the Donation Campaign Source field in the row for each related Donation. Note that if a data import row contains values in both the Donation Campaign Source field and the Donation Campaign Name field, NPSP will match using the Donation Campaign Source. There is also a new Donation Campaign Import Status field on the data import record that indicates if NPSP found a matching Campaign during dry run or processing. [PR4044]
  IMPORTANT: We are mapping the help text of the new Donation Campaign Source field to the Opportunity.CampaignId. If you already mapped help text that maps to the Opportunity.CampaignId, we recommend that you remove it. [PR4044]
• Created a new Global Class called CallableApi that implements the System.Callable interface. It currently supports the 'TDTM.disableAllTriggers' action. [PR4046]
• Added a new public method disableAllTriggers to the TDTM_Config_API class to allow users to disable all TDTM triggers for the current execution context. [PR4046]
• You may notice two new fields on the Household Settings custom settings page: Opportunity Committed Stage and Opportunity Finalized Stage. These fields were created to support a future feature and shouldn't be used until the feature is released. Please ignore the fields for now. [PR4046]
• You can now associate a Donation with a Campaign in your Batch Gift Entry batches. When creating a batch, simply add the Donation Campaign Source field, and if needed, set a default Campaign for the entire batch. The Donation Campaign Source field is a lookup, so you can choose from a list of available Campaigns when entering a gift. When you process the batch, the Campaign selected populates the Primary Campaign ID field on the resulting Opportunity. [PR4055]
• Fixed a scroll issue in the Donation Matching Rule dual picklist [PR4067]
• Fix issue where save button was not reenabling after BGE entry form save [PR4076]
  --Donation Record Type works in all orgs, regardless of help text mapping. [PR4081]

• updated the robot_libdoc task to generate documentation for both NPSP.robot and NPSP.py [PR4091]

Issues Closed

#4068: Users without delete permissions on manage allocations do not see warning message [PR4069]

New Metadata

• CallableApi.cls [PR4046]
• CallableApi_TEST.cls [PR4046]
• OPP_StageToStateMapping_API.cls [PR4046]
• OPP_StageToStateMapping_API_TEST.cls [PR4046]
• CallableApiMethodNotImplemented Custom label [PR4046]
  Fields: [PR4046]
• npo02__Households_Settings__c.Opportunity_Committed_Stages__c [PR4046]
• npo02__Households_Settings__c.Opportunity_Finalized_Stages__c [PR4046]