Deployment Considerations for NFP SuiteApps in NetSuite

TL;DR

This article discusses vital deployment considerations for NFP SuiteApps, ensuring a smooth installation and update process. Key aspects include requirements for provisioning, user roles, and name restrictions on classifications.

Key Deployment Considerations for NFP SuiteApps

Before proceeding with the installation or updating of NFP SuiteApps, it is essential to keep the following considerations in mind:

• Provisioning: Prior to installing NFP Financials, contact your NetSuite sales or account representative to get the SuiteApp provisioned specifically for your account. This is crucial to avoid potential issues post-installation.
• User Role Requirement: Only users assigned the Administrator role have the permissions necessary to install NFP SuiteApps. This role limitation helps ensure that only authorized personnel can make significant changes to the system.
• Naming Restrictions: It is vital not to rename the standard classifications—specifically, Department, Class, Location, Subsidiary, or Account—with names identical to those used in the custom segments of the NFP Financials SuiteApp. Such naming conflicts might lead to complications during updates to the SuiteApps.
• Custom Segments: The Custom Segments used in NFP Financials are unlocked, allowing for modifications to their definitions. However, be aware that any changes made to these segments will revert to their default settings during a bundle update. The only exceptions are:
  • Label
  • Mandatory checkbox
  • Default Selection
  • Default Record Access Level
  • Default Search/Reporting Access Level
  • Sourcing lists from Transactions, Transaction Columns, Entities, CRM, and Items.

Conclusion

Being mindful of these deployment considerations will help streamline the process for installing and updating NFP SuiteApps, thereby enhancing the efficiency of nonprofit operational management in your NetSuite environment.

Who This Affects

• Administrators: Responsible for the installation and configuration of SuiteApps.
• Account Representatives: Need to be contacted for suite provisioning.
• Finance Teams: Users managing financial classifications and reports will be directly impacted by the deployment strategies.

Key Takeaways

• Ensure SuiteApps are provisioned before installation.
• Installation requires Administrator-level access.
• Avoid naming conflicts with default classifications.
• Changes to custom segments revert after updates, except for specific field values.