Skip to main content

Thank you to everyone who joined our ANZ AMA yesterday, June 24th. Special shout to our June panelists @Mia Pacey @Nicole Aebi-Moyo @Gourav Sood. Here is your recap:  

 

Q: DPE - can I ask a few questions?! We are having a lot of knock-on effects of only having them update overnight, once a day, in connected email journeys etc. (Greenpeace Australia) moving from customized sales into npc. Using custom objects in Hubspot, then a workflow to put it into the contact record, doing what we can with what we have right now. Know that DPE can run as long as there are enough tokens but the ability to not have rollups on the contact that are live or updated when they choose to, what is the plan for this? Were finding its affecting our email journeys. Ex. Sending receipts- what about a first time donor or recurring gifts, usually have to wait until the next day, feeling this change in process. Is this it is what it is? 

 

A: DPE runs as a scheduled flow and can be configured to run at different times. If it is currently only running once per day, it's worth reviewing the implementation with your consultant to understand the scheduling and resource usage. 

 

The group discussed that the primary concern is enabling key information to update immediately rather than waiting for the overnight process. One suggestion was to identify which critical fields require real-time updates while allowing less time-sensitive data to continue processing overnight. For lower-volume use cases, Salesforce Flow may provide a more immediate solution without consuming the same level of DPE processing resources. 

 

Community Note:

 DPE is constrained by processing limits (record volume, processing hours, concurrent runs, and writeback limits) rather than AI tokens. 

 

Q: I’d like to understand the security implications of integrating Salesforce with external AI platforms such as Claude via MCP. What are the recommended data protection practices, security controls, and governance frameworks organizations should implement to ensure compliance and safeguard sensitive Salesforce data in such integrations? 

 

A: Before integrating Salesforce with external AI platforms, ensure your Salesforce security foundation is well established. Review profiles, permission sets, sharing settings, and user access to confirm users only have access to the data they need. Regular security audits and strong governance should be in place before exposing Salesforce data to external AI tools. 

 

Q: Concerned about the retirement of the NPSP certification is this leading to the eventual death of NPSP? Thoughts? 

 

A: The hosts agreed that AFNP is clearly the future direction for Salesforce nonprofit solutions, with new innovation focused there rather than NPSP. However, NPSP remains fully supported, and because of its large customer base, it is expected to remain available for quite some time. There is no indication that it will be retired overnight, so organizations currently using NPSP should not feel pressured to migrate immediately. 

 

Q: How are people approaching development with claude? What skills or anything you’ve seen be really helpful? 

 

A: The recommendation was to spend time planning before asking Claude to generate code. Community members highlighted the "Grill Me"

 skill for refining ideas and reviewing implementation plans before development begins. 

 

Another best practice is to have Claude analyze your Salesforce org's naming conventions, architecture, and coding standards, then document those patterns in a markdown file. Providing this context in future prompts leads to more consistent and higher-quality outputs. 

 

Resources:

Q: Very basic one....search results home page. It shows Contacts then Accounts. Can I edit this to not show Contacts? What are your tips for 'mashing' Account & Contact fields into one field history tracking solution and one search results output. 

 

A: No discussion or answer was provided during the session.

Resources

Upcoming Events

Helpful Resources

0/9000