Issues Resolved In Version 4.97 Of Altru
Published
A list of resolved issues from version 4.97 of Altru, along with Knowledgebase article links pertaining to each issue.
Welcome to Altru 4.97. This readme lists the issues resolved in version 4.97 of Altru:
One of the biggest changes we have been working on in this release is Single Sign On (SSO) changes coming in our next release! This is an exciting change that will prepare Altru for Blackbaud Sky!
Everyone will need to prepare for SSO, so check out our recent blog post on action you need to take! Check back here regularly for future blogs about the upcoming SSO change!
| Description | KB Article Number |
| This fix resolves an issue where discounts that only apply during certain times may not apply properly around Daylight Savings Time. | 106400 |
| This fix resolves an issue where the Average Hourly Sales Report may have missing sales during a specific time frame around Daylight Savings Time. | 98367 |
| This fix resolves an issue where Altru may not allow tickets to be sold to Scheduled Events that have an on-sale period occurring around Daylight Savings Time. | 99707 |
| This fix resolves an issue where online orders may show for a different date when occurring around Daylight Savings Time. | 109281 |
| This fix resolves an issue where the patron quick search in Daily and Advance Sales may be producing more results than it should. | 111545 |
| This fix resolves an issue where an error may occur for patrons when entering an email address on the forgotten password page for webforms. Error: Please enter a valid email address. | 100951 |
| This fix resolves an issue where pledges may double count (count both the total amount of the pledge and the payments) on the Individual and Household Revenue Summary tabs of constituent records. | 101770 |
| This fix resolves an issue where an error may occur when running acknowledgements. Error: Error activating the marketing effort: An error occurred before executing the process ‘Marketing Effort Segment Record Count Calculation' : Error calculating the segment record counts: Invalid object name '##MKTSEGMENTATIONFIND_XXX. BBERR_ORIGINAL_ERROR:208 BBERR_ORIGINAL_PROCEDURE: BBERR_ORIGINAL_LINE_NUMBER:1. | 97364 |
| This fix resolves an issue where the recognition credit summary and history tabs on constituent records may not correctly show membership payments. | 74776 |
| This fix resolves an issue where the online pre-sale period was ending or beginning three hours earlier than it was set to begin or end. | 109719 |
| This fix resolves an issue where users may experience an error when refreshing OData in Excel or Tableau. Error: The following exception occurred while the managed IDbCommand interface was being used: The content of the data feed is not valid for an Atom feed.. An error occurred while processing table XXX. The current operation was cancelled because another operation in the transaction failed. | 111823 |
One of the biggest changes we have been working on in this release is Single Sign On (SSO) changes coming in our next release! This is an exciting change that will prepare Altru for Blackbaud Sky!
Everyone will need to prepare for SSO, so check out our recent blog post on action you need to take! Check back here regularly for future blogs about the upcoming SSO change!
News
Blackbaud Altru® Blog
07/31/2017 4:21pm EDT
Leave a Comment
It's a long time to wait to have OData back. :-(