3.151 (Beta 5)

Changes

• Save button will grey out and be disabled pending save. [PR4139]

Batch Gift Entry Enhancements

• New Batch Dry Run feature allows users to test processing a whole batch and resolve any errors. While Batch Dry Run is in progress, the user won't be able to add new gifts. [PR4095]

3.151 (Beta 4)

Changes

• Save button will grey out and be disabled pending save. [PR4139]

Batch Gift Entry Enhancements

• New Batch Dry Run feature allows users to test processing a whole batch and resolve any errors. While Batch Dry Run is in progress, the user won't be able to add new gifts. [PR4095]

3.151 (Beta 3)

Changes

Batch Gift Entry Enhancements

• New Batch Dry Run feature allows users to test processing a whole batch and resolve any errors. While Batch Dry Run is in progress, the user won't be able to add new gifts. [PR4095]

3.151 (Beta 2)

Changes

Batch Gift Entry Enhancements

• New Batch Dry Run feature allows users to test processing a whole batch and resolve any errors. While Batch Dry Run is in progress, the user won't be able to add new gifts. [PR4095]

3.150

Changes

Batch Gift Entry Enhancements

• You can now include any Lookup fields from Opportunities & Payments in Batch Gift Entry.
• Batch Gift Entry now supports improved mapping to standard and custom checkbox fields. In order to allow your users more flexibility around checkbox fields in Batch Gift Entry and Data Importer, the corresponding field should be a picklist. This picklist translates what you see in the Opportunity or Payment checkbox field (checked or unchecked) to their boolean equivalents (True for checked and False for unchecked). Through Batch Gift Entry, your users will be able to uncheck a previously checked checkbox field or even leave a checkbox field completely unchanged by leaving that field blank for any given donation line item. Read more about this in the Add Custom Fields to Your Batch documentation.
• Prior to this release, users were able to include fields in their matching rules even if the fields weren't used in the batch; this would cause errors when processing the batch. With this release, Opportunity or Payment fields must be included in a batch in order to be used in the matching rules.

Other Changes

• The Add Row button on the Manage Allocations page has been moved to below the list of Allocation records.
• We've added a new Callable_Api action called CRLP.getDefinitionsForRollupType for use in upcoming products. The action itself is not useable in this release.

Issues Closed

#4087: Opportunity Naming Batch Hits 50 Million Row QueryLocator Limit
#4101: Manage Allocations: If a new Allocation entry is added between other entries, the values are saved incorrectly

Installation Info

Push Schedule

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

Installation URL

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

Trialforce Template ID

TBA

3.151 (Beta 1)

Release of version 3.151 (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.150 (Beta 27)

Changes

• The Add Row button on the Manage Allocations page has been moved to below the list of Allocation records. [PR4123]

• We've added a new Callable_Api action called CRLP.getDefinitionsForRollupType for use in upcoming products. The action itself is not useable in this release. [PR4131]

Batch Gift Entry Enhancements

• You can now include any Lookup fields from Opportunities & Payments in Batch Gift Entry. [PR4082]
• Batch Gift Entry now supports improved mapping to standard and custom checkbox fields. In order to allow your users more flexibility around checkbox fields in Batch Gift Entry and Data Importer, the corresponding field should be a picklist. This picklist translates what you see in the Opportunity or Payment checkbox field (checked or unchecked) to their boolean equivalents (True for checked and False for unchecked). Through Batch Gift Entry, your users will be able to uncheck a previously checked checkbox field or even leave a checkbox field completely unchanged by leaving that field blank for any given donation line item. [PR4105]
• Prior to this release, users were able to include fields in their matching rules even if the fields weren't used in the batch; this would cause errors when processing the batch. With this release, Opportunity or Payment fields must be included in a batch in order to be used in the matching rules. [PR4110]

Issues Closed

#4087: Opportunity Naming Batch Hits 50 Million Row QueryLocator Limit [PR4124]
#4101: Manage Allocations: If a new Allocation entry is added between other entries, the values are saved incorrectly [PR4123]

3.150 (Beta 26)

Changes

• The Add Row button on the Manage Allocations page has been moved to below the list of Allocation records. [PR4123]

• We've added a new Callable_Api action called CRLP.getDefinitionsForRollupType for use in upcoming products. The action itself is not useable in this release. [PR4131]

Batch Gift Entry Enhancements

• You can now include any Lookup fields from Opportunities & Payments in Batch Gift Entry. [PR4082]
• Batch Gift Entry now supports improved mapping to standard and custom checkbox fields. In order to allow BGE and BDI to uncheck a previously checked checkbox field, the corresponding field in BGE and BDI needs to be a picklist. Read more about this in the Add Custom Fields to Your Batch documentation. [PR4105]
• Prior to this release, users were able to include fields in their matching rules even if the fields weren't in the batch, and this would cause errors when processing the batch. With this release, Opportunity or Payment fields must be included in a batch in order to be used in the batch's matching rules. [PR4110]

Issues Closed

#4087: Opportunity Naming Batch Hits 50 Million Row QueryLocator Limit [PR4124]
#4101: Manage Allocations: If a new Allocation entry is added between other entries, the values are saved incorrectly [PR4123]

3.150 (Beta 25)

Changes

• The Add Row button on the Manage Allocations page has been moved to below the list of Allocation records. [PR4123]
  We've added a new Callable_Api action called crlpApiSvc.getRollupDefinitions for use in upcoming products. The action itself is not useable in this release. [PR4131]

Batch Gift Entry Enhancements

• You can now include any Lookup fields from Opportunities & Payments in Batch Gift Entry. [PR4082]
• Batch Gift Entry now supports improved mapping to standard and custom checkbox fields. In order to allow BGE and BDI to uncheck a previously checked checkbox field, the corresponding field in BGE and BDI needs to be a picklist. Read more about this in the Add Custom Fields to Your Batch documentation. [PR4105]
• Prior to this release, users were able to include fields in their matching rules even if the fields weren't in the batch, and this would cause errors when processing the batch. With this release, Opportunity or Payment fields must be included in a batch in order to be used in the batch's matching rules. [PR4110]

Issues Closed

#4101: Manage Allocations: If a new Allocation entry is added between other entries, the values are saved incorrectly [PR4123]

3.150 (Beta 24)

Changes

Batch Gift Entry Enhancements

• You can now include any Lookup fields from Opportunities & Payments in Batch Gift Entry. [PR4082]
• Batch Gift Entry now supports improved mapping to standard and custom checkbox fields. In order to allow BGE and BDI to uncheck a previously checked checkbox field, the corresponding field in BGE and BDI needs to be a picklist. Read more about this in the Add Custom Fields to Your Batch documentation. [PR4105]
• Prior to this release, users were able to include fields in their matching rules even if the fields weren't in the batch, and this would cause errors when processing the batch. With this release, Opportunity or Payment fields must be included in a batch in order to be used in the batch's matching rules. [PR4110]