This document provides information pertaining to whether the
User Adoption Dashboard 1.0
package published
by Arrowpointe Corp. (AppExchange Org)
must be uninstalled, or have a special
configuration established during:
Package configuration needs for use of the Salesforce Account Model Conversion
(AMC) utility are also evaluated/documented here.
Productioninstance to a
sandboxused for testing data manipulations required as part of a upgrade or conversion to NPSP V3
Data transfers of this type may be required if:
developeror
developer prosandbox 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.
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.
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:
Publisher: Arrowpointe Corp. (AppExchange Org)
Package Name: User Adoption Dashboard
Package Version: 1.0
Description: (not viewable due to "internal server error" during attempt to view package details)
Package components include: [(LB) - internal server error
encountered when attempting to view package details (mentioned just above) prevented
refinement of the list provided below. At this time, the full list of
possible package components is provided.]
[Indicate key objects on which triggers are defined.]
[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.]
[Indicate important custom fields defined on any object that are _not_ provided as part of package.]
[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.]
[May be helpful to list any standard objects on which record types are defined.]
[Indicate approx number of rules. May be helpful to list objects on which they are defined and identifying information.]
[Indicate approximate number of rules.]
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:
(The list of package components provided above uses blue-colored text for components types that might present problems.)
[(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 no problems are anticipated.]
[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. Feedback from those discussions was that leaving this package installed during NPSP V3 upgrade data processing should cause no problems.]
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.]
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:
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 linkages to Accounts may be updated.
Linkage of Opportunities to Accounts may be updated.
Linkage of Tasks to Accounts may be updated.
[(LB) - The publisher was contacted for information about problems encountered data loading with this package installed. They indicate that no problems are anticipated.]
[(LB) - Discussions on Power of Us Hub or elsewhere were started to seek input about problems encountered with sandbox data loading. Feedback from those discussions generally indicated that this package contained only dashboards and reports and that these components would have no impact on 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.]