Coming May 9, 2026! This release is dedicated to maintenance and bug fixes. This update resolves a wide range of issues across merge fields, icon displays, and External Review Responses — delivering increased reliability and consistency throughout the GivingData platform.
🐛 Notable Bug Fixes
Each release includes bug fixes to enhance stability and improve your experience. Here are some key fixes:
- Application Receipt Dates Missing: Some requests were saving without an Application Receipt Date populated. The data has been backfilled for the affected records, and the underlying logic has been corrected so the receipt date is reliably captured on intake going forward.
- Workflow Task Requirement Icon: When a payment requirement was completed via a workflow task, the request displayed the red "overdue" flag icon instead of the green completion checkmark, even though the success message confirmed the requirement was complete. The icon logic has been corrected so completed requirements now display the green checkmark as expected.
- Default Docket Sort Order: The Default List View for DocketDocketLinkedRequestDocuments setting was not sorting the documents list by the specified sort order. The sort order now correctly honors the configured direction.
- Unsolicited Application Grantee Portal Permissions: When a new contact submitted an unsolicited application, the contact was not automatically receiving the "Access Organization in Grantee Portal" and "Manage Assigned" permissions. The auto-permission logic has been restored so unsolicited applicants now receive the correct grantee portal permissions on submission.
- External Reviewer Percentage Calculation: The "Percentage of Reviews Submitted" column on the External Review Management dashboard was returning incorrect percentages for some unsolicited applications. The calculation has been corrected so percentages now accurately reflect the ratio of submitted reviews for each application.
- Dashboard "Unassigned" Display Issue: On Payment and Approval Dashboards filtered by code, an "Unassigned" column was appearing for codes that had no child codes, and clicking the totals returned an empty list of payments. The dashboard now suppresses the "Unassigned" column when no child codes exist, eliminating the dead click-through.
- Document Upload OneDrive Conflict: Uploading documents to certain Requests was failing with a "name already exists in OneDrive" error because the Organization's DocumentFolderKey was missing from the database, causing the upload to misroute against an existing SharePoint folder. The folder key population has been corrected so document uploads succeed against the correct organization and request folders.
- Bank Account Custom Field Types: When configuring Bank Account custom fields with the String data type, the HTML Editor and Text Area field types were missing the configuration options (such as Dropdown/Input checkboxes) that should appear for all string-based field types per the design spec. The configuration UI has been updated so all expected options are now available across HTML Editor and Text Area field types.
- External Reviewer Table Filter: On the External Review Form Responses table, typing a name into the filter search bolded matching values but did not actually narrow the list, requiring users to scroll through all entries to find a match. The filter now properly limits the displayed rows to only those matching the search term.
- Mailing Address Merge Field Format: The merge field, Organization.PrimaryAddress.FullAddress, was rendering with incorrect formatting in default invitation messages and intake forms. The merge field now outputs the address in the proper format across invitation messages and imported intake forms.
- Tax ID Hover Selection: After the 5.3.4.1 release, adding a new Tax ID number on an organization's Financials & Compliance page required users to hover with much more precision than before. The Tax ID hover and click target has been restored so users can add new Tax ID numbers without the precision-targeting workaround.
- Singapore Address Formatting: Singapore addresses generated through the Organization.Address merge field were appending an extraneous "~X1" string from the map-based formatting (a side effect of Singapore's "No State" option), forcing users to manually delete the unwanted text. The merge field now displays the address with the correct formatting.
- External Review Response Duplicate Data: The External Review Form Response dashboard was showing two entries for a single question when the reviewer had only saved one response. The response retrieval logic has been corrected so each question now returns a single, accurate response per reviewer.
- BILL Description: When syncing transactions from GivingData to BILL, the hierarchy arrows (>) used to display coding hierarchy in the Default BILL Description field (e.g., "All Initiatives > Invention & Entrepreneurship") were being passed through as the HTML-encoded value, distorting the readability of Initiative levels in BILL. The integration now correctly preserves the ">" character so descriptions display as intended in.
- Inconsistent State Field Abbreviation: When adding a State column to an Organization Super Search results list, Australian state values were displaying as full names instead of standard abbreviations. The state-formatting logic has been corrected so all states, including the three affected Australian regions, now consistently display as abbreviations in Super Search results.
- Docket Grant Totals by Coding Drill-Down: When grouping a Docket's Grant Totals By Program Area at Coding Level 1, clicking into a code that displayed a non-zero record count and total returned a blank results list instead of the underlying grants. The drill-down query has been corrected so clicking a Level 1 now returns the matching grant records as expected.
- Request Alert Symbol Missing on Overview: When an alert was added directly to a Request, the alert indicator was not appearing on the Request's Overview page; the indicator only displayed when an Organization-level alert was present. The alert logic has been corrected so request-level alerts now properly trigger the alert symbol on the Overview page.