I did a search and returned this link: https://help.salesforce.com/s/articleView?id=sfdo.Nonprofit_Success_Pack_Release_Notes.htm&type=5
However, this is currently not working! Hoping someone here can help fix it!
#NPSP Release Announcements0 人がディスカッション中
- 最近の活動
- 作成日
- おすすめ
- すべての質問
- 承認された回答がある質問
- 未回答の質問
- 承認された回答がない質問
In Patch release 3.220, we fixed the following Known Issue: Users receive an "Unknown Error" when trying to create or edit a Recurring Donation. This patch was released to sandbox orgs on June 21, 2022 and to production orgs in EMEA and AMER on June 22, 2022 and June 23, 2022 in APAC. This update is also recorded in the Nonprofit Success Pack Release Notes.
3 件の回答
@Mathias Krüger Here is the updated link. We have transitioned from Power of Us to the core Salesforce Help site for all release notes and that broke the link I shared previously. https://help.salesforce.com/s/articleView?id=sfdo.RN_NPSP_Nonprofit_Success_Pack_Release_Notes.htm&type=5
1 件の回答
Salesforce.org has a github repository. That's where I go anyways: https://github.com/SalesforceFoundation/NPSP --Terry
Our Winter '22 release is here! NPSP version 3.209 has been pushed to production. Please look for this version in your org in the next few days and report any issues.
Critical Changes
- To enhance security for Gift Entry, Read and Edit access are required on the Payment Amount field on the Payments object.
Changes
- Announcing Elevate Power of Us edition. Integrate online fundraising with NPSP without up-front subscription costs. Learn more at Welcome to Elevate.
- We added an Undeliverable address checkbox field to the Account, Contact, and Address object. When you select or deselect the Undeliverable checkbox on any one of those records, NPSP updates the related records with the same value. Learn more in Mark an Address as Undeliverable.
- We added a Recurring Donation Change Log object to track amount, schedule, or campaign updates. Learn more at Track Upgrades, Downgrades, and Other Recurring Giving Changes.
- We added soft credits to Gift Entry. Enter one or more soft credits for an Opportunity when you create a new or update an existing gift in Gift Entry. To enable soft credits in Gift Entry, add the Soft Credits field bundle to your Gift Entry templates. Learn more in Create or Edit a Gift Entry Template.
- We refactored NPSP Household Management to improve scalability and performance.
- Important for developers and implementation partners: We updated the ACCT_IndividualAccounts_TDTM class to handle the logic for Household Accounts and Addresses instead of calling out to the ADDR_Account_TDTM and ADDR_Addresses_TDTM classes. This change makes the ACCT_IndividualAccounts_TDTM class more efficient and speeds up Contact insert operations. We recommend that you test customizations in your org if you're using custom code built within the TDTM framework. For additional technical information, see this pull request.
Issues Closed
- #6522: Contact Primary Address Type Changes to "Mailing" When Switched to "None" Value
- #6646: Number of Household Members Field Is Not Recalculating When Last Contact is Deleted From Account
Community Ideas Delivered
- Add "Bad Address" checkbox on Address Record
- Allow creation of Opportunity Contact Roles (OCR) through NPSP Gift Entry
New Metadata
- Apex Classes
- DonationView
- DonationsView
- GiftBatchView
- GiftView
- SoftCreditsView
- InboundGiftBatchDTO
- InboundGiftDTO
- RD2_ChangeLogSelector
- RD2_ChangeLog
- RD2_ChangeLog_TEST
- RD2_ChangeLogController
- RD2_ChangeLogView
- RD2_ChangeView
- RD2_FieldChangeView
- RD2_ChangeLogService
- RD2_ChangeLogService_TEST
- Custom Metadata Types
- Custom Notification
- Fields
- RecurringDonationChangeLog__c.ChangeType__c
- RecurringDonationChangeLog__c.EffectiveDate__c
- RecurringDonationChangeLog__c.NewAmount__c
- RecurringDonationChangeLog__c.NewAnnualValue__c
- RecurringDonationChangeLog__c.NewCampaign__c
- RecurringDonationChangeLog__c.NewExpectedTotalValue__c
- RecurringDonationChangeLog__c.NewInstallmentFrequency__c
- RecurringDonationChangeLog__c.NewInstallmentPeriod__c
- RecurringDonationChangeLog__c.NewPlannedInstallments__c
- RecurringDonationChangeLog__c.NewPaymentMethod__c
- RecurringDonationChangeLog__c.NewRecurringType__c
- RecurringDonationChangeLog__c.NewSchedule__c
- RecurringDonationChangeLog__c.NewStatus__c
- RecurringDonationChangeLog__c.NewStatusReason__c
- RecurringDonationChangeLog__c.PreviousAmount__c
- RecurringDonationChangeLog__c.PreviousAnnual_Value__c
- RecurringDonationChangeLog__c.PreviousCampaign__c
- RecurringDonationChangeLog__c.PreviousExpectedTotalValue__c
- RecurringDonationChangeLog__c.PreviousInstallmentFrequency__c
- RecurringDonationChangeLog__c.PreviousInstallmentPeriod__c
- RecurringDonationChangeLog__c.PreviousPlannedInstallments__c
- RecurringDonationChangeLog__c.PreviousPaymentMethod__c
- RecurringDonationChangeLog__c.PreviousRecurringType__c
- RecurringDonationChangeLog__c.PreviousSchedule__c
- RecurringDonationChangeLog__c.PreviousStatus__c
- RecurringDonationChangeLog__c.PreviousStatusReason__c
- RecurringDonationChangeLog__c.RecurringDonation__c
- npe03__Recurring_Donations_Settings__c.EnableChangeLog__c
- Address__c.Undeliverable__c
- Contact.Undeliverable_Address__c
- Account.Undevlierable_Address__c
- Lightning Web Components:
- geFormWidgetSoftCredit
- geFormWidgetSoftCreditRow
- rd2ChangeLog
- rd2ChangeEntry
- rd2ChangeEntryItem
- rd2ChangeEntryValue
- Objects:
- RecurringDonationChangeLog__c
19 件のコメント
This is the most recent NPSP release announcement I can find, but there was a Spring '22 release -- is that correct? 3.214? (As a managed package, I'm assuming NPSP3 updates automatically but just confirming. Thanks!)
In our 3.157 release, we stopped creating GAU Allocation records for $0 Opportunities.
We heard some feedback from the community, and in the 3.161 release, we’re going to be reverting that change.
Now, after 3.161, if you create an opportunity with an amount of $0, allocations will still automatically be created if you have enabled default Allocations.
If your organization doesn’t create $0 Opportunities, or use GAU Allocations, this change isn’t going to affect you at all. If this change is going to affect your org, please feel welcome to share your thoughts and feedback. Our ongoing conversations are what makes our community great - so let us know what you’re thinking!
See full release notes: https://github.com/SalesforceFoundation/Cumulus/releases/tag/rel%2F3.157
4 件の回答
@Lizzy Roberts Is the NPSP Releases a group or a topic now? What should I do to get those announcements?
1 件の回答
NPSP Release Announcements is a broadcast only group here: https://powerofus.force.com/s/group/0F980000000D9Qr/npsp-release-announcements
Join the group for email updates. The topic also exists #NPSP Releases to supplement the group, as the group is broadcast only. That goes for all release announcement groups.
I recommend you subscribe “to every post” so that you don’t miss out on important information:
- NPSP Release Announcements Chatter Group
- EDA Release Announcements Chatter Group
- SAL Release Announcements Chatter Group
- Follow the Updates & Releases topic for all general Salesforce release information
Hope that helps!
Nonprofit Success Pack version 3.154 will be pushed to production orgs tonight. Please check your sandbox orgs and report any issues. Full release details are available at https://github.com/SalesforceFoundation/Cumulus/releases/tag/rel%2F3.154
Critical Changes
We introduced a change to the Payments object that prevents both the Paid and Written Off checkboxes from being selected at the same time. You can check whether you have any records with both checkboxes selected by running the following report:
- Create an Opportunities with Payments report.
- Change Close Date filter to All Time.
- Create a filter in the report for Paid equals True AND Written Off equals True.
- Adjust the report columns to include: Payment Number, Paid, and Written Off.
- Run the report.
- If you don't see any results, you're good to go.
- If you do see results, open each Payment record and deselect either the Paid or Written Off checkbox.
Changes
- We resolved a couple of scenarios where the scheduled ERR_Notifier job consistently fails:
- When you enable either Email or Chatter Post notification and there are more than 50,000 Error__c records in your org, we now limit the number of error notifications to the most recent 500 errors created in the last 48 hours. Note that this would normally be a single email with a list of all the errors.
- If the User or Chatter Group specified for Error notification is either inactive or has been deleted, the error notification job will simply mute the error rather than fail the job.
- Admins who had previously configured error notification via email or chatter, but who had not been receiving these notifications may find that they are now working again.
- We introduced a new batch size setting for Customizable Rollups called Contact Soft Credit to Acct Batch Size that will be used for Account Contact Soft Credit Batch Sizes. The existing Account Soft Credit Batch Size will now be used for Account Soft Credits (Non-Skew mode). The current value from Account Soft Credit Batch Size will be copied to the new Contact Soft Credit to Acct Batch Size so that your existing settings are not modified. For Skew Mode, the Account Skew Mode Batch Size will also be used for Account Soft Credit Skew mode execution.
- We updated a broken link on the NPSP Getting Started page to point to the correct module on Trailhead.
Issues Closed
#4159: Payments should not be allowed to be marked as "Paid" and "Written Off"
#4165: Getting Started Page: Trailhead Link is Broken
#4166: Customizable Rollups: Account Soft Credit Jobs Using Default 200 Batch Size
Announcing Enable new NPSP Features video!
This video shows admins the steps needed when turning on new objects, fields and pages that aren't enabled by default.
Read the full documentation here: https://powerofus.force.com/articles/Resource/NPSP-Enable-New-Features
Special thanks to @Emily Jakubiak @Jessica Langelaan for help with the video!
@NPSP Community Sprints @Nonprofit Success Pack @NPSP Evangelism (ARCHIVED) @SFDO Open Source Contributors @Getting Started with Salesforce @System Administrators
When I go to the manage household page and search for a contact to add to the household, I no longer get a prompt asking whether I want to remove the contact from the old household or merge the two households. What is the expected functionality? I'm also curious about why this change was made.
1 件の回答
Ah. Perfect! I'm excited to hear that it still prompts when needed. That's much cleaner.
I've definitely already noticed the Lightning look and feel as well as the faster load times. Thank you so much!