Raven (v1.48) | Release Notes | May 2026
Our release notes offer brief, high-level descriptions of new features, enhancements, and resolved issues. Detailed information on the features, their setup, and configuration are available in the Amp Impact Knowledge Base (specific links below).
Contact support@verasolutions.org to share feedback.
Feature Enhancements:
Locked Budget Planning and Reporting Periods
Functional Documentation:
With the Raven release (v1.48), Amp Impact introduces two new fields on the Budget object to independently track which Reporting Periods have been submitted from the Plan Budget and Report Expenditure LWCs respectively. Previously, when Budget Planning Periods and Budget Reporting Periods overlapped, submitting from one LWC would incorrectly lock Reporting Periods on the other. These fields ensure that locking on planning and reporting is tracked separately, so submission/locking on one LWC no longer affects the other.
Two new fields have been added to the Budget object and are displayed in the Budgeting Cycle component:
Locked Budget Planning Period(s) - displays Reporting Periods that have been submitted from the Plan Budget LWC. Unchecking a Reporting Period unlocks it, allowing edits to resume.
Locked Budget Reporting Period(s) - displays Reporting Periods that have been submitted from the Report Expenditure LWC. Unchecking a Reporting Period unlocks it, allowing edits to resume.
With the Raven (v1.48), the locking functionality for Budget Planning and Reporting Periods on the LWCs has moved to the new Locked Budget Planning Period(s) and Locked Budget Reporting Period(s) fields on the Budget object. The Budget Locked field on the Reporting Period object no longer serves a purpose in the locking flow. Please follow upgrade instructions to remove it from your page layout.
Behind the Scenes: Technical Stuff
Compatibility with Latest Salesforce Non-Profit Cloud Objects
Salesforce's Non-Profit Cloud supports fundraising, programs, grantmaking, outcomes, and volunteers with the latest CRM capabilities. With the Raven release, Amp Impact adds NPC objects introduced across the Salesforce Winter '26 and Spring '26 releases.
These objects are now visible as Source Objects on the Aggregation Criteria popup modal and Submission Template Creation functionalities.
Fundraising (Winter '26):
GiftActuarialEntry
GiftStewardship
GiftStewardshipActivity
Fundraising (Spring '26):
DonorGiftConceptOpportunity
Grant Making (Spring '26):
Note: ApplicationFormEvalSection and ApplicationFormEvaluation are only visible when both "Grantmaking" and "Track Applications" are enabled in the org. Track Applications is available from NPC 260 onwards and requires a separate license. Contact your Salesforce account executive for Track Applications license provisioning.
ApplicationFormEvaluation
ApplicationFormEvalSection
ApplicationForm
Group Membership and Households (previously missed):
Note: The fields IsPrimaryMember, DataRollupCategories, and IsIncludedInGroup on AccountContactRelation are visible when the "Create and manage households and groups" setting is enabled. To enable it, search for "Group Membership Settings" in Salesforce Setup.
Record Rollup Definitions (previously missed):
RecordAggregationResult
API Version Update
With the Raven release, all Amp Impact components have been updated from API version 64 to API version 66, aligning with Salesforce's latest platform release. Keeping components on the current API version ensures Amp Impact benefits from the latest platform optimizations, known bug fixes, and new capabilities introduced by Salesforce.
Legacy Visualforce Pages and Dynamic Script Loading
As part of an ongoing effort to address technical debt and improve security, the following legacy Visualforce pages have been deprecated in this release. All internal references to these pages including custom buttons, page layouts, permission set access, and translations have been removed from the package. The pages themselves will be fully deleted from the package in a future release.
SetTargets.page
AddResults.page
ManageIndicators.page
ManageLogFrames.page
The corresponding Lightning Web Component equivalents continue to work as expected and are unaffected by these changes.
For upgrade steps, refer to the Raven (v1.48) Upgrade Instructions.
Please upgrade the above mentioned Visualforce pages to their Lightning Web Component counterparts before upgrading to Raven release.
Visualforce pages and their related actions will no longer be available from the next release. Subscribers are advised to review and remove any unused references to these pages from their org to ensure a smooth installation of future releases.
Additionally, dynamic script loading for addResults.js and setTargets.js has been updated to align with Salesforce's evolving security standards and performance guidelines.
Resolved Issues
Financials LWC
Deactivated planned Budget Line Items no longer visible in Report Expenditure table
In the previous version, Budget Line Items that were deactivated on the Planning table/component remained visible in the Report Expenditure table. This issue has now been resolved.
Submitting from Plan LWC no longer locks all Reporting Periods
In the previous version, when Budget Planning Period and Budget Reporting Period were set to the same value, submitting the budget from the Plan Budget LWC incorrectly submitted and locked all Reporting Periods in the Reporting LWC as well. This issue has now been resolved.
Example: If your Budget Planning Period and Budget Reporting Period were both set to "Q1 2025", submitting a budget in the Plan Budget LWC would also incorrectly lock Q1 2025 in the Reporting LWC. This no longer occurs.
Submission Response Form
Multiple picklist values with similar text no longer bolded in Word download
In the previous version, when downloading a Submission Response Form as a Word document, multiple picklist values with similar text were incorrectly displayed in bold. This has now been fixed, and only the selected picklist value is displayed in bold.
Uploaded files remain visible across all file upload questions
In the previous version, when a Submissions Response Form contained multiple required file upload questions, previously uploaded files were not visible (when interacting with other file upload questions on the same page). This issue has now been resolved.
Indicators, addResults and setTargets
Duplicate Result records are no longer created for Cross Disaggregated Indicators on STAR pages
Editing or removing Target, Result, or Baseline values for Cross-Disaggregated Indicators without refreshing the page was causing the system to generate duplicate Result records on each save. This has been resolved. The system now correctly updates existing records instead of creating duplicates, consistent with the behaviour for Group Disaggregated and Non Disaggregated Indicators.
Results template upload no longer creates blank Result records for Indicator Results that are left empty
In the previous versions, blank result records were being created for all Project Indicators when a user uploaded the Results Excel template, even if no result value was entered for those indicators. This issue has now been resolved. The system now only creates Result records for indicators where a Result value has actually been entered, consistent with the existing behaviour for Targets upload.
Set Targets page now loads correctly in non-english languages when nested indicators with Disaggregation Group translations are present
When the user language was set to any non-english language and nested disaggregated indicators with translated Disaggregation Group names were present, the setTargets LWC failed to load and displayed a 'Something went wrong' error. This issue has now been resolved.
Activities LWC
Implementation Plan upload no longer hangs on invalid dependent picklists
Previously, uploading an Implementation Plan that contained an invalid dependent picklist value (e.g., a "Planning" status applied to a Milestone) would cause the upload popup to buffer indefinitely, with no error log generated and no feedback to the user. This has been resolved, the system now correctly identifies invalid picklist entries and surfaces them in the error log, giving users clear visibility into what needs to be corrected.
IATI Reporting
IATI XML validation now correctly handles non-Humanitarian and non-Conditional projects
XML files for projects where the IATI Humanitarian or IATI Condition Attached fields were set to FALSE were failing validation because empty child blocks (Humanitarian Scope, Conditions) were still being printed to the XML. This issue has now been resolved. Empty child blocks are no longer included when the parent field is set to FALSE.