NWDC

home   about   contact   downloads   links   pricing   reading list   [salesforce]   site map  

Current loctn: salesforce > npsp v3 upg > pkg eval > pkg eval wealthanalytics for sf 1.4

Salesforce NPSP V3 Upgrade Package Evaluation - WealthAnalytics NP for Salesforce 1.4

Purpose

This document provides information pertaining to whether the WealthAnalytics NP for Salesforce 1.4 package published by WealthEngine must be uninstalled, or have a special configuration established during:

  1. 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.

  2. 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:

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:

Package Details

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

Publisher: WealthEngine

Package Name: WealthAnalytics NP for Salesforce

Package Version: 1.4

Description: WealthEngine is the leading provider of on-demand solutions for sophisticated wealth identification, prospect research and analytics on individuals, companies and foundations. This package provides the ability to pass contact information to the WealthEngine FindWealth8 (FW8) solution for evaluation and scoring for wealth and propensity to donate. The package leverages WealthEngine's ProspectLink web service API which passes Salesforce.com contact data and returns wealth ratings and scoring information. The package also leverages WealthEngine's WebConnect to display the full contents of a FW8 query

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

Package components include: [Directions to author - This template provides a full list of components that might be included. This list should be edited as appropriate for the package being evaluated. And this direction to author may be deleted.]

  1. Apex Classes
  2. Apex Triggers

    [Indicate key objects on which triggers are defined.]

    1. 1 defined on "Results" object provided with package.
  3. 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. 6 defined on Contact
    2. 6 defined on Lead
    3. All others defined on objects provided with package
  4. Custom Objects

    [If custom objects are provided with the package, this may mean that a required uninstall action would also require export of records from these objects prior to the uninstall and reloading of that data when the package is later reinstalled.]

    [May be helpful to list custom objects provided with package.]

    1. Result
    2. WETrackingId_CS
    3. WEUser
  5. Custom Report Types
  6. List Views
  7. Page Layouts
  8. Report Folders
  9. Reports
  10. Static Resources
  11. Tabs
  12. Visualforce Pages

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:

  1. Creation of Account records
  2. Update of Contact records
  3. Update of Opportunity records
  4. 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 not contacted about problems encountered with NPSP V3 install and/or use of the AMC utility while this package is installed. Package components did not appear to suggest problems.]

User Input

[(LB) - No discussions on Power of Us Hub or elsewhere were sought for information about problems encountered during NPSP V3 installation or related data processing. Package components did not appear to suggest problems.]

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 installed during use of the Account Model Conversion utility will 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:

  1. 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.

  2. Contacts

    Contacts linkages to Accounts may be updated.

  3. Opportunities

    Linkage of Opportunities to Accounts may be updated.

  4. Tasks

    Linkage of Tasks to Accounts may be updated.

Publisher Input

[(LB) - The publisher was not contacted about problems encountered during data loading with this package installed. Package components did not appear to suggest problems.]

User Input

[(LB) - No discussions on Power of Us Hub or elsewhere were uncovered which provide information about problems encountered during sandbox data loading. Package components did not appear to suggest problems.]

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.]