Views:

Revised 10/10/2025

RELEASE NOTES: October 9, 2025

akoyaGO release notes give all users information about bug fixes, enhancements, and new features in the current release. This document describes all changes as of 10/09/2025. Documentation will be updated or created to reflect these changes. If you have questions, please contact your account manager or akoyaGO Support. Please be aware that you may need to refresh your browser, clear your browser cache, or log out/log back in to see the following changes after the day of the release.


akoyaGO

  • Bug Fixes
    • We have fixed a bug in which users were seeing handling note script errors when opening a constituent record.
    • We have added a filter to the Requirements Summary system view to include Requirements that do not have a Requirement Type assigned.
    • The Constituent table Business Rule "Default GOapply contact to Primary Contact" has been deprecated. This business rule is no longer enabled by default. It can be enabled as an option, if desired.
    • We have fixed a bug that was causing error messages when users attempted to delete records in akoyaGO. Reminder: to maintain data integrity and auditability, the recommended best practice in akoyaGO is to deactivate records rather than delete them. 
  • Enhancements
    • Mailing Lists: We have added validation to the +Add to Mailing List button on Contact and Constituent that will prevent users from adding the same record to a Mailing List twice. If the record already exists as a Mailing List Member on the list they are trying to add to, they will be notified and the action will be canceled. This will prevent instances of duplicates.
    • Users will now be notified via page banner if they deactivate a Contact record that is the Primary Contact on a Constituent record.
    • The akoyaGO community forum link has been added to the navigation pane of all workspaces under the Resources section.
    • We have cleaned up the Activity types available on the Committee table. Allowable types now include Appointment, Email, Phone Call, Task, and Note.
    • We have added a subgrid to the Org Details tab of Constituent records that displays all child constituents of that record – all records where the constituent is listed as the Parent Constituent.
    • We have added a column for Net Amount to the Request Payment Summary system view.
    • The Email Templates table has been moved to the Mailings section of the Tools workspace.
    • Donor Portal Connections (GOfund) will now validate the email address of the Contact to which it is connecting. If it is invalid, the connection will not be created and the CRM user will be alerted as to what needs to be fixed.
    • We have created a new activity type for activities that were imported into systems during the implementation process. This is to provide transparency into activity creation and origin. The Imported Activity type cannot be manually created.
    • We have added a standard workflow template to fill in Requirement Due date based on fields in Request called Populate Requirement Due. Users can update the template as desired to fit their needs and it will run on create of a new Requirement record. For instructions on turning a workflow template into a workflow, see the knowledge article Creating a Process Workflow from a Workflow Template in PowerApps.

akoyaGO with Accounting
 
  • Bug Fixes
    • General (affects all workspaces)
      • We have fixed a bug in which users were seeing handling note script errors when opening a constituent record.
      • The Constituent table Business Rule "Default GOapply contact to Primary Contact" has been deprecated. This business rule is no longer enabled by default. It can be enabled as an option, if desired.
      • We have fixed a bug that was causing error messages when users attempted to delete records in akoyaGO. Reminder: to maintain data integrity and auditability, the recommended best practice in akoyaGO is to deactivate records rather than delete them.
    • Grants Management
      • We have added a filter to the Requirements Summary system view to include Requirements that do not have a Requirement Type assigned.
      • We have fixed a bug in which the Approve – Partial option on Request was creating duplicate payments.
      • Request Quick Create: We have fixed a bug in which a payment was not being created when Original Grant was filled in in the quick create form. Reminder that the only time Original Grant will trigger a payment creation is in the Request Quick Create form.
  • Enhancements
    • General (affects all workspaces)
      • Mailing Lists: We have added validation to the +Add to Mailing List button on Contact, Constituent, and Donor that will prevent users from adding the same record to a Mailing List twice. If the record already exists as a Mailing List Member on the list they are trying to add to, they will be notified and the action will be canceled. This will prevent instances of duplicates.
      • Users will now be notified via page banner if they deactivate a Contact record that is the Primary Contact on a Constituent or Fund record.
      • The akoyaGO community forum link has been added to the navigation pane of all workspaces under the Resources section.
      • The Email Templates table has been moved to the Mailings section of the Tools workspace.
      • We have created a new activity type for activities that were imported into systems during the implementation process. This is to provide transparency into activity creation and origin. The Imported Activity type cannot be manually created.
    • Grants Management
      • We have cleaned up the Activity types available on the Committee table. Allowable types now include Appointment, Email, Phone Call, Task, and Note.
      • The Concepts table has been added to the navigation pane of the Grants Management workspace.
      • We have added a subgrid to the Org Details tab of Constituent records that displays all child constituents of that record – all records where the constituent is listed as the Parent Constituent.
      • We have added a column for Net Amount to the Request Payment Summary system view.
      • We have enhanced the logic surrounding GOverify and Est. Grant Pay Date so that GOverify will run once the Est. Grant Pay Date is within 30 days or any time the Payee changes.
      • We have added a standard workflow template to fill in Requirement Due date based on fields in Request. Users can update the template as desired to fit their needs and it will run on create of a new Requirement record. For instructions on turning a workflow template into a workflow, see the knowledge article Creating a Process Workflow from a Workflow Template in PowerApps.
    • Donor Management
      • The Gifts by Donor subgrid on Donor will now be sorted newer to older by Gift Date.
      • Donor Portal Connections (GOfund) will now validate the email address of the Contact to which it is connecting. If it is invalid, the connection will not be created and the CRM user will be alerted as to what needs to be fixed.
    • Fund Management
      • On create of a new Fund, Fund Name will default to the Formal Fund Name. This will streamline data entry and ensure that Fund Name contains data as it is used in multiple system processes.
      • We have created a new system view on the Accounts table called ‘Accounts Used as DT Accounts’ to give users insight into accounts which are used as a DT account on a Fund.
  • New Features
    • Fund Management
      • akoyaGO can now run mailable fund statements. Fund statements can be run for multiple funds and by the Donor List Email, Donor Portal Access (GOfund), or Fund Statement Recipient role. Mailable fund statements can include a cover page and a back page. For more information, see the Mailable Fund Statements knowledge article on GOsupport.
Business Central
 
  • Bug Fixes
    • We have removed the Gift/Request No. column from General Journals as editing this data can result in an interruption of processes. This column can be optionally added back to the form using the native Personalization tool. Reminder, this field should not be set manually and doing so may result in invalid updates to gifts and/or requests in the CRM.
    • We have fixed a bug in which users were receiving an error when trying to run the G/L Entries report.
    • We have fixed a bug in which adjustments were failing on payments that were created before the implementation of document type. The adjustment process relies on Document Type containing data and in payments created prior to its implementation, that field is blank. Adjustments on payments where Document Type is blank will use updated logic to determine document type and fill it in as part of the adjustment process.
  • Enhancements
    • We have made improvements to the Vendor Bank Account card by way of field level validation surrounding the Preferred Bank Account field. The form will now validate whether that field is required based on the Country/Region. If Country/Region = US and Payment Method = Bank then the form will require Preferred Bank Account.
    • With the latest Business Central version (26.4), users are now able to upload documents to Purchase Invoices.
    • For new vendor/customer records, the Tax Identification Type will default to Legal Entity.
    • The following fields have been demoted on the Bank account card, users will need to click See More in the Transfer section to see them: Client No., Client Name, Input Qualifier, and EFT IAT Export Format.
    • The 1099 reporting feature will be upgraded to the newest version available from Microsoft. For more information, see the new knowledge article on 1099 reporting
      • 1099 data will now be captured by IRS reporting period
      • Printing on 1099 forms from Business Central will no longer be supported
      • Electronic submission of 1099 forms will now be submitted
      • For new vendor/customer records, the Tax Identification Type will default to Legal Entity
GOapply
 
  • Bug Fixes
    • We have fixed a bug in which a deprecated Submit Date field was causing submission errors during the scholarship automatch process.
    • We have updated the on-screen language when a user submits a phase for scholarship automatch. Users were briefly seeing a message saying they could close the tab, which would result in abandonment of the automatch process. That text has been removed when automatch is enabled.
    • We have fixed a bug in which users were experiencing API errors when trying to approve Organization Profile Change Requests.
    • Advanced Form Builder: We have fixed a bug in which choices were not populating when mapping to a Boolean field type like Anonymous, for example. Reminder that in order to map to a Boolean field in CRM, you must use the Dropdown field type in the form editor and the choices (yes/no) will populate after you map the field.
    • We have fixed a bug in which a payment was being created in addition to the requirement when a final report phase was submitted. Final report phases should only create Requirement records.
    • We have fixed a bug in which the GOapply user approval request emails were being sent twice.
    • We have fixed a bug in which the submitted supplemental scholarship forms were not being uploaded to the Request’s document folder.
    • We have fixed a bug in which the link was broken in the GOapply Invite New User email template. Users were not able to click the hyperlink, they were having to copy/paste into a new browser.
    • GOapply Reviewer bug fixes:
      • We have fixed a bug where fields would be hidden from reviewers if the Show to Applicant setting was disabled, even if Hide from Reviewer was not enabled.
  • Enhancements
    • Scholarship Automatch can now be set on an Opportunity by Opportunity basis using a new field on GOapply Opportunity called Automatch Enabled. This field works in conjunction with the Automatch Enabled field in GOapply Settings. For more information, please see the GOapply Admin Guide.
    • Publish Date: GOapply Opportunities now contain a date/time field called Publish Date. This field works in conjunction with the Publish toggle (Publish must = Yes) to determine when an Opportunity becomes live on your GOapply site. A future date/time can be selected here to schedule publishing of an Opportunity. Publish Date will become required via a Business Rule when an Opportunity is published. If you want this Opportunity to be accessible immediately, make sure to set this field to today's date. A Publish Date is required for all Opportunities to be published, including those that are Invite Only.
    • We have enabled transcript and recommendation panels and form editors on Scholarships so that if individual scholarships require their own letters or transcripts, you can collect those.
    • The ‘In Progress’ and ‘Submitted’ system views on the Status Tracking table now include descriptions of all filters used. Users can see the description by hovering their mouse over the ‘i’ next to the view name.
    • In the Organization Profile tab of GOapply Settings, a descriptive tooltip has been added to the Display GOapply Users field that specifies that if checked, GOapply users will be able to deactivate other users registered under the same organization.
    • We have added a system view to the Status Trackings table called ‘Applications in Error’ that displays status tracking records where the Current Phase Status is ERROR or the Error Message field contains data.
    • We have updated the Scholarship form builder to Simple Form Builder. New scholarship forms after 10/9/25 will open in Simple Form Builder. For more information on Simple Form Builder, please see the knowledge article on GOsupport.
    • The Founded field on Constituent is now searchable which means it is available to add to forms like the GOapply Organization Profile.
    • We have improved the on-screen language shown to the user during scholarship automatching. Users were being led to believe that they could close the window, but this stops the process and would result in errors. The new language clarifies that they must remain on the screen until the process completes.
    • We have clarified the language on the new user onboarding page to say “Create a password” when users are invited to apply.
    • We have added a scholarship counter into the automatch process so the applicant can see the matching progress in real time.
    • The “Invite Constituent to Apply” feature has been enhanced so that, if no GOapply Users exist for that Constituent, the system will automatically create a GOapply user for the Primary Contact listed on the record and send the invitation to apply.
    • Advanced Form Builder:
      • We have removed the Copy and Add to toolbox options from dynamic panels to reduce submission and mapping errors.
      • The Interim Report and Final Report panels have been removed. Important: these panels will still be supported in existing forms. However, they will not be available on new forms.

GOfund
 
  • Bug Fixes
    • The GOfund Usage Metrics dashboard has been updated to include new views for recent grant, interfund, and scheduled distribution recommendations. These views point toward Request rather than GOfund Log.
    • We have fixed a bug in which some users were getting a 500 error when previewing GOfund Charts.
  • Enhancements
    • A new setting has been added to GOfund Settings to enable or disable the Recommendation Note field.
    • GOfund Usage Metrics dashboard:
      • This dashboard has been renamed to simply GOfund to better reflect its content.
      • This dashboard now includes Active GOfund Change Requests.
    • A new setting has been added to GOfund Settings called Default Start Date Mode. Users can choose Calendar Year or Fiscal Year. If Fiscal Year, the default start date for fund statements in GOfund will be the first day of your fiscal year start month as determined in Accounting Settings.
GOdonate
 
  • Bug Fixes
    • We have fixed a bug in which when gifts were split between multiple funds and made for different amounts, the sum of the gift fees was sometimes not adding up to the original gift fee amount.
    • We have fixed a bug in which recurring gifts that have failed to process for various reasons were not being marked for error, meaning neither the foundation staff nor the donor was alerted to the failure. If the transaction fails, the status will be set to Error and the donor will receive an email alerting them of this change.
  • Enhancements
    • The GOdonate Transaction form has been updated to include dedication information for each gift on the Fund Details tab.
    • The GOdonate Transaction form has been updated to include a lookup field to Recurring Gift that will populate when applicable.
    • The greeting has been updated in the GOdonate Email Verification email template to include first name rather than email.


 
Keywords: release notes, october 2025, product update notes