Hello
Can anyone recommend where to start managing my foundation's members? We want to keep track of the people affiliated with our organization.
- Should it be just using Accounts, Contacts, and Personal Accounts?
- What should we consider to ensure it's scalable later on?
- Do you have a guide or trailmix on how to start setting up the Org and help the foundation's directors become familiar with what Salesforce can do in general? Regards
Hi Benito
Thanks for asking. Since NPC was launched, I've noticed that many Salesforce professionals haven't fully understood the new refactoring and data model. Let me give you my tips
1. Study in detail all new Objects and their definitions from the Salesforce Developer Documentation and use all available Trailhead Trailmixes
https://developer.salesforce.com/docs/atlas.en-us.nonprofit_cloud.meta/nonprofit_cloud/npc_intro.htm
https://resources.docs.salesforce.com/latest/latest/en-us/sfdc/pdf/nonprofit_cloud.pdf2. Analyse your requirements and map them to an existing feature of NPC as much as possible, avoiding creating unnecessary Objects and processes that do not follow the BEST PRACTICES and what is already developed on NPC
3. Use default and out-of-the-box features and configuration up to 90%, avoiding coding unless it is strictly necessary. The majority of NonProfit requirements can be solved by just evaluating and mapping the default functionalities of NPC
Study and explore the Salesforce Industry Components
There are lots of Industry Components, but since we are highlighting the ones utilised by nonprofits, we will be focusing our attention today on the following:
- Omnistudio
- Business Rules Engine
- Action Plans
- Document Checklists
- Data Processing Engine
- Discovery Framework (Assessments)
4. Should it be just using Accounts, Contacts, and Personal Accounts?
According to the new DataModel, it is recommended to use Accounts for Organisations and Businesses, and Person Accounts for Constituents, Individuals, and other individual entities.
Why? Because now NPC is based on Salesforce Industries, and the new DataModel in Fundraising, for example, is using PersonAccounts as part of the solution and not Contacts
But as you may know, with PersonAccounts you have certain things to consider, and you will also have access to Contacts, as it is a dual-type Object that includes Account & Contact at the same time.
5. What should we consider to ensure it's scalable later on?
Always use standard features, use NPC Objects, map requirements to existing functionality, do not alter or fork the existing NPC data model, and you will not have "scalability issues".
When your requirement is not covered by NPC, then build, but make sure that you have review all the existing solutions of NPC, including the Salesforce Industry Components too
