Salesforce Certified Nonprofit Cloud Consultant

Which of the following is NOT a target object for custom roll-ups?

1. Payment

2. Account

3. Contact

4. GAU

The correct answer is: Payment

The concept of custom roll-ups is primarily associated with aggregating data from child records to their parent records within Salesforce. This technique is particularly valuable in nonprofit use cases where organizations need to track and analyze various aspects of their operations, such as donations or volunteer hours. In the context of the listed objects, the ones that are standard targets for custom roll-ups typically include records that have a defined parent-child relationship that can be utilized for aggregation. The Account, Contact, and GAU (Grant Allocation Unit) objects are all part of this architecture, supporting roll-up summaries due to their relationships to other records. For example, GAUs are used to manage the allocation of funds and can be rolled up to provide insights at a higher level. The Payment object, however, is not usually a target for custom roll-ups in the same manner. Payments are transactional records related to donations but do not directly aggregate information to their parent objects in the same way that Accounts and Contacts might. Therefore, they don't fit into the typical framework of custom roll-ups within Salesforce, making it the correct choice for which is NOT a target object for this process. Understanding the relationships and the implications of roll-ups in Salesforce data architecture is critical for effective data management and reporting, especially for