Salesforce NPSP V3 Upgrade Package Evaluation - Soapbox Engage QuickStart for SalesForce 1.4

Purpose

This document provides information pertaining to whether the Soapbox Engage QuickStart for SalesForce 1.4 package published by PICnet must be uninstalled, or have a special configuration established during:

Upgrade from Non-Profit Starter Pack (NPSP) V2 to NPSP V3
Package configuration needs for use of the Salesforce Account Model Conversion (AMC) utility are also evaluated/documented here.
Transfer of data from Production instance to a sandbox used for testing data manipulations required as part of a upgrade or conversion to NPSP V3
Data transfers of this type may be required if:
1. A developer or developer pro sandbox is being used for testing NPSP V3 upgrade/conversion processes
  The use of these sandboxes can avoid the expense of a full sandbox in some situations.
2. A sandbox test of NPSP V3 upgrade/conversion has revealed problems that require a revised test that in turn requires reloading of the sandbox with test data.
  Even though a full sandbox will include data contents, the typical full sandbox 29-day refresh cycle may result in a need to reload the sandbox if a single upgrade/conversion test doesn't suffice.

Red-colored text is used to represent critical information items that may interfere with needed operations in very important ways.

Blue-colored text is used to represent useful information which nonetheless is somewhat less than critical in importance.

Green-colored text is used to represent useful information which indicates an absence of problems or special configuation/data handling needs.

Use agreement

Information provided here is copyrighted by Larry Bednar and licensed under the GNU Free Documentation License. A copy of the text of this license may be found at http://www.gnu.org/licenses/fdl.html

The main points of the GNU license indicate that users are allowed to distribute the orginal licensed product, or distribute modified versions if the following conditions have been fulfilled:

Distributed versions must indicate if changes have been made, and the date of the changes
Source code must be provided with distributed versions of the product or made readily accessible through other means
The distributed product must also be licensed under the GNU Lesser General Public License or the GNU Public License
A copy of the the applied GNU license must be provided with the distributed product.

If a more detailed understanding is needed, please follow the links provided above to review the actual text of the GNU licenses.

If you distribute modified copies of these items, it is both polite and useful (but not required) to provide some additional information:

The author(s) of any changes, with contact information
Modified versions of accompanying documentation that reflect your changes

Package Details

[(LB) - The version of this package that I examined was unmanaged.]

Publisher: PICnet

Package Name: Soapbox Engage QuickStart for SalesForce

Package Version: 1.4

Description: This includes the custom fields to automate the building of cross-product base components for organizations installing any of the Soapbox Engage products (www.soapboxengage.com).

(A catalogue of package components is provided in this file: pkg_components_soapbox_engage_quick_start_for_sf_1_4.xls)

Package components include:

Custom Fields
[If an uninstall is required, these fields and associated data will likely be removed. Export of those data and updates after a reinstall may be required.]
1. 27 defined on Lead
2. 28 defined on Opportunity

NPSP V3 Install and ACM Usage Configuration

The AMC utility is stated to require that no additional automation should execute during AMC operation.

Any package automation (Apex triggers, workflow rules, or validation rules) that execute in these situations may cause problems:

Creation of Account records
Update of Contact records
Update of Opportunity records
Update of Task records

(The list of package components provided above uses blue-colored text for components types that might present problems.)

Publisher Input

[(LB) - The publisher was contacted for information about problems encountered with NPSP V3 install and/or use of the AMC utility while this package is installed. They indicate that They indicate that problems are sometimes encountered during use of the AMC utility for changes in account model when Soapbox Donations is installed. More specific information was not provided.]

User Input

[(LB) - Discussions on Power of Us Hub or elsewhere were uncovered which provide information about problems encountered during NPSP V3 installation or related data processing. Input there from PICnet staff indicated that problems are sometimes encountered during use of the AMC utility for changes in account model when Soapbox Donations is installed. They suggested direct contact with their support services, which was done.]

Final Evaluation for NPSP V3 Install and AMC Operation

Regarding configuration of this package during NPSP V3 installation and use of the AMC utility...

[LB - My educated guess is that leaving this package (which is just one package among several installed as a part of Soapbox Donations) installed during use of the Account Model Conversion utility will typically cause no problems. There appears to be no automation that would execute during use of the AMC utility.]

Sandbox Data Loading

Package automation that creates records in response to record insertions may create records that are not derived from the data source.

This may be important if users intend to use the sandbox for a complete review and validation of post-conversion functionality. Especially if users will expect to see an exact and accurate representation of records from the source database (usually the production instance) within the sandbox

This may not be important if the sandbox is used only to verify correct conversion of data to a new account model (such as the new NPSP V3 household account model), and if the sandbox will not be expected to contain an overall faithful representation of data from the source database. If package automation does not create new records within key objects being handled by the AMC utility, data transfers undertaken solely to create an NPSP V3 data processing test environment, data transferred to the sandbox should be acceptable for the intended uses.

The AMC utility works with records in these objects:

Accounts
If the database is being converted from one-2-one or bucket to the new household account model, new Account records will be created to represent NPSP Household records already present in the instance.
Contacts
Contacts linkages to Accounts may be updated.
Opportunities
Linkage of Opportunities to Accounts may be updated.
Tasks
Linkage of Tasks to Accounts may be updated.

Publisher Input

[(LB) - The publisher was contacted for information about problems encountered data loading with this package installed. They indicate that problems are sometimes encountered during use of the AMC utility for changes in account model when Soapbox Donations is installed. More specific information about this specific package component of Soapbox Donations was not obtained.]

User Input

[(LB) - Discussions on Power of Us Hub or elsewhere were started to seek input about problems encountered with sandbox data loading. Input there from PICnet staff indicated that problems are sometimes encountered during use of the AMC utility for changes in account model when Soapbox Donations is installed. They suggested direct contact with their support services, which was done.]

Final Evaluation for Sandbox Data Loading

Regarding configuration of this package during data loading...

[LB - My educated guess is that leaving this package installed and configured in a normal fashion will not interfere with Production->Sandbox data transfer. Components of this specific part of the Soapbox Donations install do not seem to include any automation that might be expected to cause problems]

Last modified: 14:28:59 14-Mar-2015