Hi all,
I shared this over in the NPSP group but wanted to share it more widely. My org discovered an issue in NPSP with the '25 Summer Release where the Auto name checkbox functionality in Manage Household is not working as expected. We reported it to support and they created a KB article:
https://help.salesforce.com/s/issue?id=a02Ka00000fBHG9
Summary of the issue:
On the 'Manage Household' page, when the "Auto Name," "Formal Greeting," and "Informal Greeting" options are unchecked and a custom name is entered, the Account Name, Formal Greeting, and Informal Greeting initially update as expected. However, after subsequently editing and saving the account record, these fields revert to the automatic household naming instead of retaining the custom values entered.
I wanted to let folks know in case they were having similar issues. As of right now (6/17/25), there are no solutions. Please report if you're also having the same issue.
I've seen two other NPSP naming bugs since the recent NPSP release. Salesforce says they are part of the same "Known Issue" Caitlin linked, though the Steps to Reproduce/Workarounds are different:
- For one client, their Contacts are being automatically marked as Excluded from Household Formal and Informal Greeting (but not Account Name) such that their greeting fields are "Sir or Madam". Not sure what triggers which contacts are impacted, but all have an Account Last Modified Date of 6/16 or later. The contact can be unmarked as excluded to fix - I haven't confirmed if the fix holds on subsequent edits or reverts to excluded.
- Another client reported that "the organization account name is updating when the contact name is changed. For example, this proxy contact "Friends of NONPROFIT at ORGANIZATION LLC" had "Family" in the last name, so I removed "Family " from it and saved. It populates "Family" in the last name again and added another "Family" to the Account Name" resulting in Organization Account name "ORGANIZATION LLC Family Family Family Family Family Family" because it adds family again each time they try to remove family from the Contact Last Name. The workaround is: "to remove "Family" from the Account Name, not the Contact Name, and it will be removed from both the Account and Contact Name."
These three bugs are wreaking havoc for NPSP users for two weeks!
We were told on Case #470831649 that there is nothing else to do other than monitor the associated Known Issues article for updates on the fix release timeline.
Nonprofits need a solution, not a problem to monitor. Take better care of your customers!If you experience the two issues I noted here, be sure to report on the known issue page to increase the urgency of attention needed:
https://help.salesforce.com/s/issue?id=a02Ka00000fBHG9
