The issues included in this report have been fixed since the 3.0 release and prior to the 4.0 release. All of these fixes are included in CRM 4.0.
Comment | Work Item | Knowledgebase |
---|---|---|
A 2.93 patch mistakenly added the Simple Appeal Data Form to the “Marketing & Communications View Only” role. This issue was fixed and “Simple Appeal Add Data Form” was removed from all security roles. | 299703 | BB742858 |
Correct header labels now appear on search pages when users access them from mobile devices. | 390696 | |
In a Chrome internet browser, this fix removes height restrictions from certain pages with summary views. This allows for easier and more streamlined viewing. | 315964 | |
In Blackbaud Internet Solutions, when you configure a Donation Form part for recurring gifts only and you clear the Allow donor to enter ending date checkbox, the end date field for the recurring gift no longer appears on the web page. | 280480 | BB741848 |
In Marketing and Communications, images that you resize for email marketing now display correctly in the preview and in the sent email. Previously, resized images displayed correctly in the sent email, but not in the preview. | 286478 | BB742208 |
In Prospects, this change applies to the Prospects and Plans tab of the “My Fundraiser page.” Previously, under “Prospect assignments,” a warning symbol displayed next to a prospect associated with a historic prospect plan where the last completed step was over 90 days old. With this fix, the warning symbol no longer displays. | 302106 | BB742982 |
In the webshell version of Blackbaud CRM, this change applies to an Enhanced Revenue Batch when a constituent is added through the “Lookup ID” field. Previously, on the Main tab of the batch data entry screen, the “Go to” option was disabled on the toolbar. With this fix, the “Go to” option is enabled. | 292225 | BB742526 |
Incorrect text was removed from the Security Guide which indicated the program's audit trail could show when a System Administrator opted to "run as" another user. | 415951 | |
Now when an Infinity SDK addin is enabled or disabled on a data form, the changes are immediately applied to the form. Previously, the changes were not applied until the web server cache was recycled. | 391289 | |
Now when users scroll down a page and click a shortcut link, the top of the new page appears. Previously, the new page appeared in the scrolled down position from the previous page. | 349301 | |
On the Communications tab of a constituent record, the Channel filter was missing a Phone option. With this fix, you can now filter communications by Phone channel. | 392032 | |
On the Communications tab on a constituent record, processes without packages (correspondence, receipts, tribute acknowledgements, and planned gift acknowledgements) were incorrectly listed with a “Mail” channel. With this fix, the assigned channel is blank for these communications and they only display when you filter by “All” channels. | 398972 | |
Previously, an address marked as 'do not mail' could incorrectly be used when you wrote a letter to a constituent. When you used the write a letter option on a constituent record, the primary address would automatically load, even when it was marked as 'do not mail.' | 317708 | BB744238 |
Previously, content on the Revenue tab of a planned gift record did not display correctly. With this fix, content on the Revenue tab displays correctly. | 345659 | BB746813 |
Previously, if you had a constituent with an existing spouse and tried to update the spouse information through a Constituent Update Batch, the information was not updated. | 411331 | |
Previously, if you used advanced spouse name formats for a marketing effort, you had to run the Calculate segment counts process during activation to ensure data for the marketing exclusions report was generated. Now, you can disable the Calculate segment counts process during activation if you have already calculated counts at least once. | 374839 | |
Previously, in an Enhanced Revenue Batch, when a constituent record was edited from within the batch, an error displayed upon save. Even though an error displayed, the information continued to update successfully. With this fix, the error no longer displays. | 304933 | BB743263 |
Previously, in an Enhanced Revenue Batch, when a pledge or recurring gift was entered with a zero amount, recognition credits did not automatically populate for the transaction. With this fix, recognition credits automatically populate correctly. | 235554 | BB736296 |
Previously, in an Enhanced Revenue Batch, when you entered a last name in the “Constituent” field and pressed “Tab” on your keyboard, the “Batch Revenue Constituent Search” screen did not automatically load. With this fix, the search screen loads correctly. | 256849 | BB739246 |
Previously, in an Enhanced Revenue Batch, when you entered a value in the Amount field and another value in the Receipt amount field, the Receipt amount field reverted back to the Amount field's value. This issue occurred when the amount fields were populated prior to the Date field. With this fix, the fields populate correctly. | 383685 | |
Previously, in Batch, the receipt amount did not calculate correctly for certain exchange rate values. With this fix, we modified the calculation to ensure correct receipt amounts display regardless of the exchange rate value. | 409861 | BB751396 |
Previously, on the Details tab of a major giving plan step record, the "Expected date" did not display correctly based on regional settings. With this fix, regional settings are respected and the "Expected date" displays correctly. | 334258 | BB746309 |
Previously, queries based on the Blackbaud Data Warehouse did not appear in ad-hoc query searches or in the Microsoft Excel add-in. To take advantage of this fix, you must reinstall the Microsoft Excel add-in. | 398987 | |
Previously, stewardship plan steps were incorrectly replicated when editing pending steps or adding completed steps with a frequency other than “Single Occurrence.” With this fix, the plan steps replicate correctly. | 398688 | |
Previously, the age of a deceased constituent appears inconsistently on the constituent record, planned gift record, and in a query. With this fix, the age appears as zero on a planned gift record an in a query, and appears as a blank field on the constituent record. | 383681 | |
Previously, the ETL process for the Blackbaud Data Warehouse could sometimes fail when the ETL maximum parallelism was set to 4. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 368942 | |
Previously, the Owner and Status fields on an Interaction add form did not autopopulate for groups, households, or committees. | 390942 | |
Previously, the program did not record the ChangeAgentID in the SQLFUNCTIONCATALOG table when users changed address formats from the Manage countries page in Administration. With this fix, database administrators can now include user information when they create reports outside of the program that detail address format changes. | 260400 | BB739632 |
Previously, the Search button on the constituent search screen on the web dashboard was located on the far right of the screen, so you sometimes were not able to see it. With this fix, the button is now located at the bottom of the first column on the screen. | 394877 | |
Previously, when a batch had a user message, users got an error when they tried to save the batch without navigating to the page with the message. You can now save the batch without errors, even if you do not first navigate to the page in the batch that contains the user message. | 267312 | BB740571 |
Previously, when a Constituent Update Batch was imported without mapping the Constituent field, existing Constituencies were erased. | 267901 | BB740469 |
Previously, when a custom revenue batch was deleted, data in the batch continued to display in the control report. With this fix, the batch data no longer displays. | 273392 | BB741063 |
Previously, when a donation or constituent update was downloaded from Blackbaud Internet Solutions into an Enhanced Revenue Batch or Signup Transaction Batch, the Address Capitalization and Address Standardization rules did not work correctly for the following fields: First name, Last name, Address, and City. With this fix, the Capitalization rule is applied correctly. | 352716 | BB747692 |
Previously, when a fundraising purpose was edited, the public name was deleted and users were unable to edit or add a new one. With this fix, the public name persists after editing a fundrasing purpose and is able to be modified. | 389250 | BB750088 |
Previously, when a user navigated from one constituent’s Recognition History page to another constituent’s Recognition History page, the value initially selected for the Recognition filter field changed. With this fix, the value for the Recognition filter field remains the same when moving through multiple constituent records. | 389820 | |
Previously, when an import process ran using a batch template with the Enable auto-save setting selected, the batch that was generated from the import process did not retain the Enable auto-save setting. With this fix, the setting is retained. | 389812 | |
Previously, when editing the frequency of an existing stewardship plan’s pending step, an additional step was created upon save. With this fix, the edit saves correctly to the original pending step and no additional step is created. | 383458 | |
Previously, when linking an opportunity to a pledge (from the Revenue field) on the “Add a naming opportunity recognition” screen, an error displayed. With this fix, the error no longer displays. | 400532 | |
Previously, when prospect constituency information was edited, the audit time displayed 12:00 AM instead of the correct, posted time. With this fix, we modified the code to store values in a datetime datatype rather than date. The posted time now displays correctly. | 436188 | BB752974 |
Previously, when searching for a matching gift organization through batch or manually through the Matching Gifts tab on a revenue record, an error displayed upon selecting an organization. With this fix, the error no longer displays. | 383598 | |
Previously, when splitting payments for event registrations added through an Enhanced Revenue Batch, the Receipt preference field defaults to Consolidated. With this fix, the Receipt preference defaults to Per payment. | 414856 | BB751771 |
Previously, when the Matching Gifts tab was accessed on a revenue record, the tab did not load in an acceptable timeframe. With this fix, the tab successfully loads without a delay. | 352292 | |
Previously, when the “Mark payment for re-receipt” option was selected, deselected, and selected again on a payment transaction record, the option remained deselected. With this fix, the program correctly displays the chosen option. | 262241 | BB739841 |
Previously, when users chose the increasing amount values that make up an ask ladder, they could not enter an ask amount of zero. With this fix, users can now enter an ask amount of zero in the Ask 1 column if they select the "Add" option in the Type column. | 298300 | BB742746 |
Previously, when viewing applications associated with payments for sponsorship recurring gifts and sponsorship recurring additional gifts, an error displayed. With this fix, the error no longer displays. | 283229 | BB742059 |
Previously, when viewing major giving management dashboards, the dashboards included plans from sites to which users did not have security rights. With this fix, we implemented site security to ensure rights are accurately respected. | 389819 | |
Previously, when you attempted to deploy the data mart after upgrading to version 3.0 of Blackbaud CRM, you received an error. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 361046 | |
Previously, when you changed the title for a constituent, the gender could sometimes change to 'unknown,' even though the constituent had previously had a gender assigned. | 309939 | BB743392 |
Previously, when you created a group and chose to copy the address from the primary contact, the address formatting was sometimes lost. This happened when the address of the primary contact had special formatting. With this fix, the address is formatted exactly as the primary contact's address. | 382856 | |
Previously, when you dissolved a household, communications sometimes still got added to those households, even though the households no longer existed. This happened when a constituent had been a member of a household that later got dissolved and was now a member of a new household. When a communication was added for that constituent, it was mistakenly included in both households. | 262604 | BB739910 |
Previously, when you set up a new relationship with a reciprocal relationship, the reciprocal type only auto-selected to the first value you chose. Subsquent choices did not automatically update the reciprocal type. | 231652 | BB735721 |
Previously, you received an error when you clicked the Planned Giver constituency code link on the Interactions page of a constituent record. We have moved this information to the constituent record, where you can access this link in the summary section of the constituent record. | 382832 | |
Previously, you sometimes got false positive results during the Blackbaud Data Warehouse validation process. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 380075 | |
Previously, you sometimes received an error when deploying the Blackbaud Data Warehouse if source codes included apostrophes. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 276611 | |
Technical Change: Previously, the program incorrectly allowed you to assign the same role to a group member with overlapping dates. With this fix, you can now no longer assign the same role to the same group member with dates that overlap. When you apply this fix, any identical roles with overlapping dates will be combined. The resulting role will use the earliest start date and the latest end date. If you do not want those roles to be combined, before you apply the update, change the start and end date for the roles so they do not overlap. | 382819 | |
Technical Change: This fix addresses a security error that sometimes allowed users to see constituents they did not have security rights to see in query results. This could happen when a user was in multiple security roles that had different permissions. With this fix, the role that grants the user permission to see the query is the same role the program considers to determine which constituents are included in the query results. | 429941 | |
The account locked out message that appears when a website user repeatedly enters the wrong username and password credentials now reads "Please enter a valid Login name and Password." Previously, the message read "Account has been locked due to repeated failed logins" which may indicate to a malicious user that the username is valid. This fix applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 346796 | |
The Blackbaud Internet Solutions Communication Preferences form no longer displays old addresses and email addresses that are listed as former contact information with a past end date on the constituent record in Blackbaud CRM. This previously occurred when you used the General Correspondence element on the form. | 268779 | BB740720 |
The Constituent Lifetime Giving smart field no longer excludes planned gift payments. After you run the update and process this smart field, its value will include all revenue given prior to the process date. However, the smart field includes only future planned gift revenue; it does not include planned gift payments that occurred before the last run date. To include planned gift payments made prior to the last run date, you will need to create a new Constituent Lifetime Giving smart field. | 414845 | |
The constituent member page displays up to four benefits for the membership. If there are more than four benefits, the View all button includes a count of the total number of benefits, such as “View all 5.” Previously, there was no visual indication that there were more than four benefits to view. | 268798 | BB740725 |
The error message that appears when a user's session times out now includes updated text to specify that the user may need to click the browser's refresh button. Previously, the error message did not include the word "browser." | 370117 | |
The Gift Reference Number and Reference Date were missing from the Constituent Gift node when users created a new Constituent type export definition. With this fix, the Gift Reference Number and Reference Date now appear. | 278325 | BB741669 |
The Next transaction date field is now editable on a recurring gift, even when the next transaction has already been partially paid. Previously, you could not change the date of the next transaction if it was partially paid. | 273736 | BB741104 |
The option for editing any type of existing letters did not appear on the Update template screen. With this fix, the option to edit letters now appears. | 281339 | BB741890 |
The Summary Section Appeal caption field is now spelled correctly on the XML specification for the Marketing Effort Page. | 289183 | BB742325 |
This change addresses an issue for Multicurrency users. The summary area of a list segment record displayed the wrong currency for rental and exchange costs. The program now respects currency settings and displays the correct currency. | 383967 | |
This change applies to a Constituent Update Batch. Previously, when importing new addresses to existing records and marking some addresses as primary, the new addresses marked as primary did not display as the primary address. With this fix, primary addresses are marked correctly after batch committal. | 275731 | BB741341 |
This change applies to a Multicurrency environment. Previously, when a user changed the constituent on an existing payment and saved the record, recognition credits in the Transaction summary section changed from the original currency to a new currency format. With this fix, the currency remains unchanged. | 383670 | |
This change applies to a Multicurrency environment. Previously, when editing the spot rate from the “Edit recurring gift” screen, an error displayed upon save. With this fix, the message no longer displays upon save. | 365571 | |
This change applies to all batches. Previously, certain fields enabled or disabled inconsistently. With this fix, batch fields now enable and disable correctly. | 432227 | |
This change applies to an Enhanced Revenue Batch when a constituent is added through the “Lookup ID” field. Previously, from the “Add matching gift claims” screen, you could not add a new relationship record from the “Relationship” field. With this change, you can add new relationships. | 290841 | BB742423 |
This change applies to an Enhanced Revenue Batch where a finder number is required. Previously, when the finder number was missing, an error displayed during validation, but no exception message displayed in the batch data entry grid. With this fix, exception messages display correctly. | 267546 | BB740606 |
This change applies to an Enhanced Revenue Batch. Previously, when a payment was applied to a commitment and an additional recognition associated with the same designation, an error displayed upon committal. With this fix, the error no longer displays upon committal. | 383679 | |
This change applies to an Enhanced Revenue Batch. Previously, when recognition credits and amounts were added in a batch and then the amount was updated before saving the batch, no message displayed to prompt a user to update the recognition credits. With this fix, when an amount is updated, the message "Would you like to reset recognition credits to default for the new amount" displays. | 423010 | BB752197 |
This change applies to constituent records associated with both a major giving prospect constituency as well as a response-pending opportunity. Previously, from the “Edit prospect constituency” screen, when you selected a date in the “Date to” field that was previous to the current date, an error correctly notified you that the constituency had a response-pending opportunity. With this fix, an error now displays when any date is added to the “Date to” field to notify you of a pending opportunity. | 297275 | BB742630 |
This change applies to constituent records associated with sponsorship recurring gift payments where different exchange rates are applied. Previously, when sponsorship data results were exported from a correspondence business process, duplicate data was exported. With this fix, no duplicate data is exported. | 266000 | BB740367 |
This change applies to donor constituency criteria configured on the Constituencies page in Constituents. With this change, organization currency displays correctly. | 323141 | BB745051 |
This change applies to geocoding addresses with PO boxes. Previously, when a user right-clicked a constituent’s address and selected Geocode, an error displayed. With this fix, the error no longer displays. | 383682 | |
This change applies to pledges with posted and non-posted payments when edited directly through a Revenue Update Batch. Previously, when a pledge’s Revenue category field was updated, the field only updated on non-posted payments associated with the pledge. With this fix, both posted and non-posted payments are updated correctly. | 403533 | |
This change applies to the "Add Stewardship Plans Process Report." Previously, when a prospect plan already existed, the report displayed a message that the plan existed, but did not display the constituent associated with the plan. With this fix, the constituent name also displays. | 322927 | BB744975 |
This change applies to the "Edit stewardship plan step" screen for a constiutent. Previously, on the Details tab of a stewardship plan step page, when you selected to edit details, the "Target date" on the Details tab did not match the "Target date" on the "Edit stewardship plan step" screen. With this fix, the dates match. | 345307 | BB746825 |
This change applies to the "Generate step update batch" screen accessed from the "Generate Step Update Batch Process" tab on the Manage stewardship plans page in Prospects. Previously, when fields in the "Updates" grid were blank and the process ran, an error displayed. With this fix, the error no longers displays. | 319408 | 11806861 |
This change applies to the "Loyal donor" constituency criteria configured on the Constituencies page in Constituents. Previously, a constituent who paid consecutively for more than the specified time period did not receive the "Loyal donor" constituency. With this fix, the constituency is applied when the time period is met or exceeded. | 326391 | |
This change applies to the Campaigns tab of a planned gift record. Previously, a campaign was displayed by its Lookup ID number. With this fix, the campaign is now displayed by its name. | 321293 | BB744721 |
This change applies to the Probate status field when editing a planned gift. Previously, for planned gift vehicles that did not display a Probate status field on the edit record (such as Life insurance), the field incorrectly displayed a Pending status in a revenue query. With this fix, the Probate status field now correctly displays no status in a revenue query. | 383635 | |
This change applies to the Prospects and Plans tab of a fundraiser record. Previously, when you viewed the RSS feed and clicked the green arrow under a constituent name, multiple error displayed. With this fix, errors no longer display. When you click the green arrow, you are taken to the constituent record. | 312063 | BB743693: |
This change applies to the recognition process when the “Consider recognition credits in donor constituency definitions” checkbox is selected when editing donor constituency criteria from “Constituents.” Previously, when the checkbox was selected, "Major donor" and "Loyal donor" constituencies were not properly assigned to constituents who should have received revenue recognition. Also, these constituencies were not using the reporting filter default to determine which gifts count toward constituencies. This fix corrects both issues. | 310727 | BB743065 |
This change applies to the transaction summary section of a planned gift revenue record. Previously, when “Living trust” was selected as the planned gift vehicle or when the vehicle was changed to “Living trust,” the “ Planned gift vehicle” field in the summary section of the planned gift revenue record appeared blank. With this fix, the field populates correctly. | 348102 | BB747077 |
This change applies to the “Add prospect plan” screen accessed from the Plans tab of a major giving prospect record. On the Steps tab, when you clicked “Edit additional details,” added a new step, and clicked “OK,” the step did not appear until you clicked inside the grid. With this fix, the step appears in the grid immediately after adding it. | 272474 | BB741005 |
This change applies to the “Edit sponsorship expiration” screen accessed from a sponsorship record. Previously, when you entered an expiration date that was prior to the next transaction, selected a reason, and clicked “Save,” an unhelpful error message displayed. With this fix, a useful error message displays that informs the user of the invalid action. | 318835 | BB744310 |
This change applies to the “Field changed” column in a Constituent History Report. Previously, when a new education record was added that included an institution and status, the Constituent History Report displayed a constituency status code field with a value of “Unknown.” This field could not be changed and had no context in the report. With this fix, the field does not display. | 275763 | BB741351 |
This change applies to the “Merge two constituents” tasks on the Duplicates page in Constituents. Previously, when “Delete source constituent” was selected on the “Merge two constituents” screen and the source constituent was associated with an outstanding matching gift claim, an error displayed. With this fix, the error no longer displays. | 276394 | BB741443 |
This change applies to the "Fundraisers" query. With this fix, we added the "Date to" and "Date from" output fields to the query so that users can filter data more precisely. | 326622 | BB745580 |
This fix address an issue with auction purchase payments. Now, when the auction item purchased is marked as “Do not post,” you can still post and make adjustments, such as gains and losses against the fair market value of the item, to the auction purchase payment. Changing the post status on the auction item will still cause multiple distributions to be created on the posted auction purchase payment. | 286621 | |
This fix addresses a filename length issue. When the filename length is over 255 characters (including path), the file failed to export when users selected Merge on a Marketing Effort Acknowledgment export output. To solve this issue, a file length error message now surfaces telling users to resolve the issue by shortening the length of their letters or mailing name. | 414248 | |
This fix addresses a formatting issue in the Constituent Profile Report. Previously, the report left unnecessary blank space before the recognition programs section. | 303971 | BB743135 |
This fix addresses a performance issue that occurred on the History tab of the Import process page. Previously, a timeout message sometimes appeared before the data was available. | 367572 | |
This fix addresses a performance issue that occurred on the Revenue History and Recognition History data lists. Previously, a timeout message sometimes appeared before the data was available. | 422517 | |
This fix addresses a performance issue that sometimes happened for relationship trees with a large number of relationships. Previously, when you tried to expand a constituent in a relationship tree with a large number of relationships, sometimes the process timed out and did not complete. | 420835 | |
This fix addresses a performance issue with the Post to GL process when using a Revenue selection. Previously, some users may have experienced trouble logging into the system when the process was running due to the performance issue. | 380681 | |
This fix addresses a problem viewing member roles on the Members tab of constituent records. Previously, if the tab had a large list of groups, the roles associated with those groups were indented and not viewable on the screen without having to scroll across the page. | 300595 | BB742911 |
This fix addresses a problem when you tried to consolidate member information for all members of a committee. When you create a committee, you can choose to consolidate group member data starting on a specific date or for all dates. Previosuly, when you chose to consolidate data for all dates and then viewed the details for a specific committee member, the 'Consolidate member data as of' date was incorrect. | 267344 | BB740577 |
This fix addresses a problem when you tried to filter constituent interactions by status in WebUI. Previously, the status filter for constituent interactions was not available in WebUI. | 284649 | BB742099 |
This fix addresses a security issue with functionality on the Memberships page. Previously, users with limited rights could see tasks they did not have rights to. | 345906 | BB746886 |
This fix addresses an error in the ETL process in the Blackbaud Data Warehouse. The error occurred when you had more than one attribute on a membership and the attributes were marked as 'Allow only one per record.' In this scenario, when you included the membership attributes in the Blackbaud Data Warehouse, the ETL process failed. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 394692 | |
This fix addresses an error that occurred when a user clicked "Update projected totals" in a Membership Dues Batch and then tried to save it. The error occurred when the batch included the "Send renewal to" field as hidden and the default value for it was blank. Now we automatically set the "Send renewal to" field to "Giver" if it is blank in the batch. | 433049 | |
This fix addresses an error that occurred when you tried to access the Constituent Data Review screen. Previously, when you accessed this screen, you sometimes received the following error: 'An unknown error occurred during the request. This could indicate a request to an invalid endpoint or a problem with the web server configuration.' This error was related to a performance issue when loading the screen, and did not appear when you accessed the page again. With this fix, the page loads correctly and you do not receive the error. | 266296 | |
This fix addresses an error that sometimes occurred when changing the amount of a pledge installment. Previously, when you attempted to change the amount, you received an error that the installment splits must balance to the pledge and had to edit the pledge in order to save the change. With this fix, the error no longer displays and you will not need to edit the pledge a second time to save changes. | 292347 | BB742535 |
This fix addresses an error that sometimes occurred when you tried to edit a smart query. Previously, you sometimes received the error 'Error: Simple datalist entry could not be translated. Error converting data type nvarchar to uniqueidentifier.' This occurred when the user-defined data list filters included a drop-down field in its list of fields available for filtering and the value was blank. | 407354 | BB751223 |
This fix addresses an error which occurred when merging two constituents who were registered for the same event. If no payments are associated with the event registrations, the constituents will now be merged with the event registration of the target constituent. The constituents will not be merged if both constituents have registrations for the same event and either registration has an event registration payment or an event registration payment pending in an uncommitted batch. Depending on the situation, if the constituents were merged, the target constituent could mistakenly have an over- or under-payment of the event registration or the target could have duplicate revenue for the event registration. | 290327 | |
This fix addresses an error which occurred when using the event search field on the Events page. Previously, if you changed the Event Work Center Event Search to use a different event search using Search List Replacements in Administration, you received an error when you tried to use the event search field. | 334713 | |
This fix addresses an inconsistency for how finder numbers are displayed in the program. Previously, finder numbers included commas when you saw them on the Origin tab of a constituent record's history, but without commas when you saw them on the Details tab of the revenue record associated with the constituent. With this fix, finder numbers do not include commas in either view. | 281288 | BB741875 |
This fix addresses an issue an issue with the Assign seats functionality for events. Now when you assign seats for event registrants, you can sort the list of registrants by the host’s name, not just the registrant’s name. | 298347 | BB742755 |
This fix addresses an issue introduced in service pack 8 when running the Blackbaud Data Warehouse validation process. Previously, when you ran the validation, you received an exception indicating that there were null values on the Online System ID column. This happened because that column did not have default values. With this fix, we have added default values to the column so the exception no longer appears. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 404549 | |
This fix addresses an issue on the History tab of a Credit card processing business process. The start and end times for each process run are now included with the start and end dates. Previously, only the dates were displayed. | 294901 | BB742522 |
This fix addresses an issue saving recognition credit settings for relationships. Previously, when you added a relationship to a constituent record and selected recognition credit options, these options sometimes did not save to the related constituent. | 249625 | BB738291 |
This fix addresses an issue that occurred when a user attempted to browse the records for a revenue application type ad-hoc query. Previously, when a user created a revenue application type ad-hoc query and selected the Browse button, an error message would display. Now, the page definitions display correctly. | 331430 | BB746116 |
This fix addresses an issue that occurred when rescheduling the remaining installments for a pledge. Previously, the new installment schedule would not display under Installment activity after the updated schedule was saved. Now, the updated schedule displays. | 414492 | |
This fix addresses an issue that sometimes happened when updating addresses using a Constituent Update Batch. Previously, when you updated addresses using the batch for members of a household, and the address was marked as 'Copy address to household members,' the batch did not update the address for all household members. | 382793 | |
This fix addresses an issue that translated change agents to app users incorrectly, making it difficult to determine app user audit information. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 278714 | BB741715 |
This fix addresses an issue when assigning registrants to seats for an event. You can now use drag-and-drop to assign a registrant to a seat or to change a seat assignment for a registrant. | 278025 | BB741645 |
This fix addresses an issue when importing spouse information in a Constituent Update Batch in WebUI. Previously, the batch included a spouse name that did not match the spouse name on the record, the batch updated the spouse name and the field was grayed out so you could not make a manual change after the import. With this fix, when the spouse name on the batch does not match the spouse name on the record, you receive an error before you can import the batch information. | 345016 | BB747072 |
This fix addresses an issue when running a Constituent Recognition Process for a recognition program with a level set up to use "Set future minimum amount" with a future "Effective date" for processing. Previously, recognition programs and levels were not correctly assigned to constituents. | 303643 | BB743091 |
This fix addresses an issue when trying to edit existing roles for a constituent from their committee membership information. Previously, the role editing functionality did not work when you were viewing the constituent as a committee member. | 262563 | BB739894 |
This fix addresses an issue when you have default gift fees enabled and set up in Revenue. When you edit a default gift fee on the Gift Fees tab of a fundraising purpose, the DESIGNATIONLEVELGIFTFEESTRUCTURE field in the audit table shows this information as being deleted and re-added, instead of edited. | 333444 | |
This fix addresses an issue when you searched for a constituent using constituencies. Previously, sometimes using constituency as a search parameter did not return complete results. | 279451 | |
This fix addresses an issue where finder file imports were failing when user fields, such as City, were longer than 255 characters. With this fix, the finder file now imports successfully. | 426837 | |
This fix addresses an issue where users were being denied access to a data list. Previously, if a constituent ID was null, the user was denied access to the data list even if the user normally had rights to access that data list. Now, users can access the data list if a constituent ID is null and the user has proper access rights. | 276129 | BB741406 |
This fix addresses an issue where you could not assign registrants to some seats for an event when the Assign seats screen was maximized. | 278671 | BB741704 |
This fix addresses an issue which occurred when editing a matching gift claim payment. Previously, the Description field for the application details was blank. | 351923 | BB747586 |
This fix addresses an issue which occurred when editing the registration of an invitee for an event. Previously, when you edited the registration for the invitee and added an additional constituent to the registration, the original invitee was mistakenly listed twice on the Invitees tab of the invitation. | 279648 | BB741762 |
This fix addresses an issue with editing the designations of a posted pledge. Previously, if the designations were deleted and the exact same designations were re-added, the posted pledge's status would be set to "Do not post." Now, a correct adjustment generates and the post status is set to "Posted (activity pending)." | 401093 | |
This fix addresses an issue with email addresses not being marked as primary for relationship records. This happened when you added an email address to a constituent and marked it as primary and then selected to copy the email address to the household and its members. Even though the email address was marked as primary in the original constituent, the shared address was not marked as primary for the relationship records. | 263729 | BB740043 |
This fix addresses an issue with end dates for phone or email contact information. Previously, when an email address or phone number had an end date that had already passed, the program did not flag that email address or phone number as 'Do not contact,' so users had to mark them manually if they wanted to avoid contacting an outdated email address or phone number. With this fix, when the end date passes for an email address or phone number, they are automatically marked as 'Do not contact.' | 347495 | BB747071 |
This fix addresses an issue with gift fee information in the database. Previously, the TRANSACTIONAMOUNT field in the FINANCIALTRANSACTIONLINEITEM table did not reflect changes made to gift fees after they were edited using the Edit gift fees task on the payment record. | 322936 | BB744981 |
This fix addresses an issue with Group Sales. Previously, from the Reservations List tab when you clicked Add and then Add payment, the Add a payment screen was not displayed. | 392263 | |
This fix addresses an issue with revenue reversals being incorrectly pulled into the post process and being included in the pre-post report. Previously, a deleted payment with "Not posted" adjustments could be erroneously linked to a deposit. Now, deleted payment adjustments will no longer appear as unlinked payments. | 380462 | BB749385 |
This fix addresses an issue with running the credit card process when there is a problem with a credit card token not being present in either CRM or in the Blackbaud Payment Service. Previously, users were not necessarily made aware there was an issue and the credit card transaction was not processed. Now, when there is an issue with the credit card token, the batch row error message states, “The donor’s current credit card information cannot be used to successfully process this payment. Please contact the donor to get updated credit card information. You will need to update the credit card information in the batch row to process the current payment. You will need to update the credit card information on the original revenue commitment record in order to process future payments. | 373968 | |
This fix addresses an issue with setting a default value for the membership “Term” field in Membership Dues Batch. Previously, if a default value was included for the “Term” field, an error occurred. | 275405 | BB741297 |
This fix addresses an issue with the Assign seats screen. It is now, once again, resizable. | 278680 | BB741710 |
This fix addresses an issue with the Credit card processing business process. When you set the process up so that it creates a new batch, you select the account system to use for the transactions. You cannot change the account system after the credit card process has been saved. | 373520 | |
This fix addresses an issue with the ETL process when your database had a large number of fundraiser teams. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 418925 | |
This fix addresses an issue with the Event Seating Summary report when sorted by tables. Previously, the tables were sorted incorrectly (to display as 1, 10, 2, and so on) instead of numerically (to display as 1, 2, 3, 4, and so on). | 278678 | BB741709 |
This fix addresses an issue with the length of the Creditor ID field for bank accounts with "Europe (SEPA)" selected as the banking system. Previously, the Creditor ID field was limited to 11 characters, even though the SEPA banking standard allows for 35 characters. The length of the field now matches the SEPA banking standard. If necessary, you can edit the Creditor ID field for existing bank accounts on the SEPA Information tab of the bank account record. To access bank accounts, from Treasury, click Manage bank accounts. | 369766 | |
This fix addresses an issue with the Membership Dues Batch. Previously, if you selected the membership program, you could not edit the Send renewal to field. | 291851 | BB742493 |
This fix addresses an issue with the Purpose type field on the Add a purpose and designation screen in Fundraising when using the WebUI version of the program. The purpose types are now sorted alphabetically. | 290293 | |
This fix addresses an issue with the way committee memberships are calculated for a constituent. Previously, when you looked at a constituent's committee memberships, the program included sub-level committee roles in the committee count for that constituent. With this fix, the committee memberships total only includes first-level committee roles. | 276087 | BB741393 |
This fix addresses an issue with using Microsoft Word merge with the constituent Write a letter functionality when the export definition fields to merge include event start date and start time. Previously, when you clicked Save on the Write a letter screen, an error occurred. | 291270 | BB742454 |
This fix addresses two issues with event lodging options. The first issue addressed was that the Lodging Options tab of an event was not displaying the correct value for “Assigned” for lodging options. The second issue addressed was that the lodging option value for “Assigned” was not updated correctly when event registrants with lodging options were deleted from the event. | 275529 | BB741308 |
This fix corrects a misspelling on an error message which appeared when setting up a membership renewal notice. | 262941 | BB739971 |
This fix corrects an issue where certain drop-down lists would not refresh correctly after changing pages in a batch. This affects only the WebUI version. | 373412 | |
This fix corrects an issue with the Outlook.com button (formerly the Windows button) on the event details web page when you use an Event Calendar part on your website. When users click the button to export the event to their Outlook.com calendar, they are now successfully redirected to their Outlook.com account and prompted to add the event to their calendar. Previously, the redirect did not work because it attempted to access Microsoft's retired Hotmail and MSN accounts. This fix applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 423184 | |
This fix corrects an issue with the UIModel in the Blackbaud Infinity SDK that caused Blackbaud CRM to not function. The issue occurred when the DataForm UIModel called the RefreshModel subroutine and repopulated the Summary section of a page that did not include other sections. | 369812 | |
This fix eliminates an issue with the eReceipt PDF icon display on a Transaction Manager part on your Blackbaud Internet Solutions website. Previously, the PDF icon disappeared from the web page after the transaction commitment (via batch) to the constituent record in Blackbaud CRM. Now, the PDF appears on the page before and after the commitment. This issue was caused by the required variable UNIQUERECEIPTNUMBER which has been updated to account for both committed and uncommitted batches. | 273227 | BB741055 |
This fix improves performance of export and queries for non-system administrators. | 435310 | |
This fix improves the performance of queries associated with revenue selections that include receipt dates and receipt numbers. | 223745 | BB734551 |
This fix includes SQL connection updates to eliminate a possible 'current executing request' message in the event log on your web server. | 289143 | BB748480 |
This fix prevented an error message that occurred in a revenue batch when you are using the "Apply to commitments" screen. Previously, if you entered a donation and the constituent had a matching gift relationship which made the donation eligible to be matched, the error occurred if you tried to delete the donation from the "Apply to commitments" screen. | 427188 | |
This fix prevents the ability to map organization records to website users when you import a list of website users in Blackbaud Internet Solutions. When this occurs, the program now creates a "Website users may not be linked to organization records" exception. | 320352 | BB744598 |
This fix prevents "1/1/0001" from displaying in the System Value column for a blank educational involvement date in a BBIS Profile Update Transaction Batch. Now, the cell correctly remains blank when there is no value for an educational involvement date. | 373507 | |
This fix removes the check constraint error CK_EVENTREGISTRANTPAYMENT_VALIDAMOUNT when you commit a BBIS Event Registration Transaction Batch and the batch includes a registration overpayment for an event from your Blackbaud Internet Solutions website. Previously, the error occurred when the constituent’s account balance was paid in full, and the overpayment caused a negative amount due. Now, the batch commitment can handle the overpayment and proceed without error. | 395349 | BB748072 |
This fix resolves a styling issue that appeared on mobile pages when users clicked the Blackbaud CRM Mobile back button. Previously, a blank blue bar was inserted on a page each time a user click the back button within the application. Now, a blue bar only appears for a page's header. | 360073 | |
This fix resolves an error that occurred when certain users tried to add Recognition Program queries. | 387973 | BB749968 |
This fix resolves an issue that allowed you to use the same name for multiple smart query definitions. The issue occurred when you created the definitions from ad-hoc queries or the Infinity SDK. | 413839 | |
This fix resolves an issue that caused an error message to appear when users attempted to sort ad-hoc query results by a system record ID when the record ID included the COUNT summary function on the Select filter and output fields tab. | 387712 | |
This fix resolves an issue that caused an error to appear when "today's date" was selected as the default value for a field from the program's design mode. | 297789 | BB742696 |
This fix resolves an issue that caused an error to appear when an ad-hoc query that included a field from the Selections node was used to create a data list and that field was available as a filter for the data list. | 418624 | |
This fix resolves an issue that caused an error to appear when an import selection was created from a CSV file of audit table records. | 391286 | |
This fix resolves an issue that caused an error to appear when new table entries were added to code tables in Administration. | 407394 | |
This fix resolves an issue that caused an error to appear when you reused the names of deleted attribute categories. The issue occurred when the deleted categories included the "Make available in lists" option and were in use when you removed them. Previously, when you deleted attribute categories, the program did not remove them completely until you used the Query View Add Attribute Extension Business Process in a queue. However, the process did not delete categories that were in use so they remained in the program and you could not access them. Now when you delete attribute categories, the program immediately removes them or a message appears to explain the reason. To completely remove attribute categories that were previously deleted but continue to cause errors, contact support to obtain a script. | 405683 | |
This fix resolves an issue that caused an error to appear when an instance of a user defined smart query was edited or the results were exported. The error occurred when the smart query definition included a blank value for a drop down filter option. | 289192 | |
This fix resolves an issue that caused drop down arrows to sporadically appear next to queries marked as "favorites." Previously, when an arrow was selected, the program did not display other options and removed the arrow from the page. | 266134 | BB740421 |
This fix resolves an issue that caused hyperlinks to appear in ad-hoc query results when the Narrative field from the Prospects node was included in the output. The issue occurred when the field value length required the output to include a scroll bar. | 290238 | BB742372 |
This fix resolves an issue that caused resized datalist columns to revert back to their original sizes when you sorted the data. The issue occurred for datalists with mulitple pages of relational information that appeared in a tree view. | 289942 | BB742357 |
This fix resolves an issue that caused spaces to change to underscores in the filenames of exports when you used "Multiple files" option to download the output. | 288918 | |
This fix resolves an issue that caused the "Do you want to save the changes to this ad-hoc query?" message to appear when an unchanged ad-hoc query was saved. | 264274 | BB740146 |
This fix resolves an issue that caused the "Save as" option in ad-hoc query and export definitions to function in Altru. | 419115 | |
This fix resolves an issue that caused the column order in existing export definitions to change when additional fields were added to them. | 268654 | BB740682 |
This fix resolves an issue that caused the History tab of process status pages for queue, credit card, and multiple batch commit processes to not include start and end times. | 292204 | BB742522 |
This fix resolves an issue that caused the Last run column on the Commit Multiple Batches page to disregard computer regional settings and always use the date format for the United States. | 292206 | BB742523 |
This fix resolves an issue that caused the program to change the name of the Application Details node when fields from it were added to an export definition. Previously, after an export definition that included Application Details fields was closed and then reopened, the name of the node changed so that other fields could not be added under it. | 269279 | BB740774 |
This fix resolves an issue that caused the program to remove the "Browse," "Export to CSV," and "Export to Excel" options on the New Smart Query screen when you resized or maximized it. | 411380 | |
This fix resolves an issue that caused the program to sort fuzzy date columns in search lists alphabetically. | 380457 | |
This fix resolves an issue that caused the program to stop responding when you attempted to select the "Edit actions" or "Properties" options from the action group sections of pages in design mode. | 367685 | |
This fix resolves an issue that caused the status column of the Registrations tab in Events to show incorrect results. The issue occurred when multiple invitations were sent to the same constituent and the statuses for them were different. Now, if the constituent is registered, "Registered" appears as the status. If not, the status from the most recent invitation appears. | 389798 | BB750153 |
This fix resolves an issue that caused the event calendar to briefly appear on the Events page when the collapsed setting was enabled in design mode. | 328429 | |
This fix resolves an issue that disabled the "Browse" option for ad-hoc queries when they included summarized calculations and the system record IDs for their source views under "Result fields to display." The issue occurred when the queries were saved and then reopened. | 367686 | |
This fix resolves an issue that intermittently caused the data in the rows of the Recognition history grid to not align with the column headers. The grid appears under the Recognition history tab in constituent records. | 395336 | |
This fix resolves an issue that invalidated user-defined data lists for feed alerts such as email alert processes. Previously, if the "Create RSS feed" checkbox was not selected under Alert options on the Set save options tab of the user defined data list screen, the program cleared the "Allow this datalist to be used for feed alerts" option whenever users opened the screen. | 415943 | |
This fix resolves an issue that occurred when SDK developers changed the casing of field names in custom query views. Previously, when users edited ad-hoc queries created from the custom views after the casing was changed, an error message appeared. | 391291 | |
This fix resolves an issue that occurred when you added a matching gift claim to a payment that was applied to multiple commitments with different designations in Enhanced Revenue Batch or Revenue Update Batch. Previously, the designations from the commitments did not appear as the default designations for the matching gifts. | 383607 | |
This fix resolves an issue that occurred when you added fixed width import file templates to the Import page in Administration. Previously, an error appeared when the CSV file included spaces in the header row. | 381285 | |
This fix resolves an issue that occurred with Add, Edit, and View forms in Blackbaud CRM Mobile. Previously, when the forms included extensions, the extensions were not formatted for mobile devices. You can add extensions to data forms from Administration or with the Infinity SDK. | 365014 | |
This fix resolves an issue that occurred when multiple installations of the program existed on a single server and the Aspose.Words license expired. Previously, when the program downloaded the updated version of the license from www.blackbaud.com, an error appeared for some of the installations. | 438783 | |
This fix resolves an issue that prevented users with SQL Server 2014 from using Report Builder to edit ad-hoc query report layouts. | 426493 | |
This fix resolves an issue that required certain users to always use the drop down option for fields instead of the type-ahead functionality. Type-ahead enables you to enter the first few letters of a field value to narrow a long list of options. The issue occurred for users with roles that do not include permission to add code table entries to the database. | 400597 | |
This fix resolves an issue that sometimes caused incorrect values to appear for drop down options in grids on forms. | 357333 | |
This fix resolves an issue that sometimes caused the program to remove registration information when a registrant was added to an event. Previously, when a registrant’s name was selected from the Registrant column of the Add a registrant form, but information was not selected from the other columns, the program removed the registration information when the form was saved. | 349558 | BB747376 |
This fix resolves an issue with constituent recognition. Previously, when a constituent was awarded a recognition level for an annual giving recognition program, the expiration date for the recognition level would be set according to the recognition program settings. However, if you changed the "Date achieved" on the constituent recognition to a date in a prior year, the "Expiration date" field in Query was not updated. This caused a mismatch and the constituent was, according to Query, still an active member of the recognition program and level. | 413322 | BB751671 |
This fix resolves an issue with dates in the descriptions of batches generated from job schedules for the Generate Payments process. Previously, these dates always used the United States date format. With this fix, the date format is now based on the web browser configuration of the user who created the job schedule. To apply this fix to your existing job schedules, you must edit and save them. | 320663 | BB744661 |
This fix resolves an issue that disabled the option to go to a constituent record directly from a committed batch. | 266561 | BB740478 |
This item is associated with BB740743. When a batch includes new payments made to a matching gift claim where the claim is fully paid before the batch is committed, an error correctly displays during the commit process. Existing payments must be deleted and re-added. Alternatively, if you edit the payment instead of deleting and re-adding, you receive the following error “you must have at least one application.” | 268949 | BB740743 |
Users experienced an increase in the completion time of the revenue acknowledgement process. We made enhancements to the process performance, which now runs 8% faster. | 401651 | |
Users experienced an increase in the completion time of the tribute acknowledgement process. We made enhancements to the process performance, which now runs 5-10% faster. | 418853 | |
Users received an error message when trying to download and view creative attachments. With this fix, the error no longer occurs. | 407159 | |
Users received an object reference error because the export definition add form was allowing users to save the form with duplicate Constituent node paths or fields. An error message now appears if two nodes have the same viewpath and alias. | 417103 | |
We added the ability to send emails for sponsorship efforts. The Email marketing page now includes an Add a sponsorship email task. You can also select an email package from a sponsorship effort. | 322155 | BB744869 |
We fixed an issue that occurred when you included a selection output field after another output field in an export definition. When you saved the definition, the name of the selection overwrote the name of the other output field. When you edited the export definition, the selection output field seemed to be duplicated because its name appeared twice. This no longer occurs. | 380602 | |
We fixed an issue with site security that occurred when you added a payment using the finder number for an acquisition list member. If you do not have access rights to all sites, you received an error that said “The current user does not have rights to use this feature in the context of this specific record." We fixed this issue and now when you enter a finder number for an acquisition list member, the list member is added as a constituent and assigned to the same sites as you. | 386487 | |
We have added two new columns to the Blackbaud Data Warehouse. The REVERSEDLINEITEMID column from FINANCIALTRANSACTIONLINEITEM is now represented on FACT_FINANCIALTRANSACTIONLINEITEM via the new REVERSEDFINANCIALTRANSACTIONLINEITEMSYSTEMID and REVERSEDFINANCIALTRANSACTIONLINEITEMFACTID columns. These columns allow you to write reports that link reversals to their original transactions. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 430571 | |
We have corrected a problem that sometimes occurred with pledge balances in the Blackbaud Data Warehouse. Previously, the TRANSACTIONBALANCE column on the FACT_FINANCIALTRANSACTION sometimes showed inaccurate pledge balances for pledges with write-offs. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 430572 | |
We have updated the caption that appears on the constituent attribute gloval change. Previously, this global change had the caption "Remove value from unqualified records." The new caption, "Remove attribute from unqualified records," makes it more clear that the value to be removed by the global change is specifically an attribute. | 367801 | |
When a constituent qualifies for a recognition program, the program appears on the constituent’s Recognition tab. The “Member since” date is now calculated based on the actual date the constituent qualified, instead of being calculated just based on the calendar year the constituent qualified from the program. | 262243 | BB739843 |
When a header file based on an export definition was generated for receipts, the header file included fields that were not part of the export definition. We fixed this issue. | 360302 | |
When a non-admin user attempted edit the package or channel on the Source code tab for a marketing effort segment, the changes did not save. We fixed this issue and edits now save correctly for all users. | 274105 | BB741156 |
When a website user selects "This donation is on behalf of a company" after entering an email address and a phone number on a Donation Form on your Blackbaud Internet Solutions website, the checkbox selection no longer removes the email address and phone number the user entered on the form. | 297943 | BB742716 |
When a website user selects a gender on the Donation Form part on your Blackbaud Internet Solutions website, the gender ("Male" or "Female") now processes correctly from the Enhanced Revenue Batch to the website user's constituent record in Blackbaud CRM. Previously, the gender appeared correctly in batch, but appeared as "Unknown" on the constituent record. | 264206 | |
When attempting to export the members of a segment from the Current members tab, only the first 500 members downloaded to the export file. We fixed this issue and the full list exports correctly. | 374505 | |
When processing reminders, the program mistakenly allowed you to select an export definition as the Output type with the Output grouping set to 'Constituent.” When you ran the process with these settings, the program failed to process any pledges. We fixed this issue and Export definition no longer appears as an output type option in these circumstances. | 265034 | BB740294 |
When running a Revenue Marketing query, the Date field under the main Revenue Marketing node did not reflect the date on the revenue record. With this fix, both the Date field under the main Revenue Marketing Node and the Revenue\Date field now display the same value. | 384799 | |
When selecting a message for an email package, messages with brackets [ ] in the subject line would not appear in the search results. We fixed this--brackets no longer cause issues when used in subject lines. | 338749 | BB746698 |
When selecting a source code part for a record, for example a segment, the code field included all segment source code parts used in source code layouts, including inactive layouts. Now, the source code part field displays only parts used in active source code layouts. | 325160 | |
When the receipts were processed “per payment” using the Gift detail, Email gift detail, or Formatted mail gift detail output formats, the program incorrectly pulled "consolidated" revenue instead of "per payment." We fixed this issue. | 370476 | |
When two website user accounts are affiliated with the same email address and one of the users selects to reset the password, the User Login part now correctly displays the username in the drop down that appears on the password reset web page. Previously, the user's name (for example, first name) appeared in the drop down. This fix applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 384460 | |
When you assign seats for event registrants, the registrants are now listed by "Last name, First name" on the Assign seats screen, which is consistent with how the registrants are displayed on the Registrations tab of the event. | 273422 | BB741070 |
When you assign seats for groups of event registrants and you attempt to assign the group to a single seat, you are now prompted that there are not enough seats. You can select for more seats to be added for the group. | 272067 | BB740946 |
When you attempt to open an email from the Emails page (accessed from Marketing and Communications, Email marketing), the error message 'The current user does not have rights to use this datalist' no longer appears intermittently. To resolve this, we have updated the NetCommunityTemplateEdit.vb load procedure. | 324650 | |
When you browse the results of a Constituent query using the “Membership Page” page definition, an older version of the constituent membership page was used. This fix corrects that issue so that the current constituent membership page is used. | 275346 | BB741294 |
When you download constituent attributes with a Yes\No value from a Profile Update form on your Blackbaud Internet Solutions website into a BBIS Profile Update Transaction Batch, the program now recognizes and displays Yes\No values. Previously, these appeared as True\False in batch and added unnecessary updates to the Constituent attributes tab. | 353832 | |
When you enable single sign-on, you can now successfully enter multiple custom authenticated application users on the Bulk Add Custom-Authenticated Application/CMS User Add form at the same time. Previously, a 'Data could not be saved. Violation of PRIMARY KEY' error message appeared when you tried to add multiple users at once and you had to enter them individually. | 316595 | BB743866 |
When you use a Profile Update Form in Blackbaud Internet Solutions, custom captions now display after you save them for the Primary Address Block advanced properties (under Contact Information.) | 261919 | BB739797 |
When you use Blackbaud Internet Solutions or Blackbaud NetCommunity, this fix removes invalid characters in URLs to comply with Request for Comment (RFC) standards. | 268757 | BB740713 |
When you use Blackbaud Internet Solutions, the Designation field on the Transaction Manager part no longer displays incorrect characters for a designation public name that includes an apostrophe. Previously, ''' appeared in place of the apostrophe. | 415131 | |
When you use Blackbaud Internet Solutions, the load time for the Transaction Manager part has been reduced. To improve this performance, the program now queries the tables directly and limits querying the views. | 353335 | BB747734 |
When you use Blackbaud Internet Solutions, this fix resolves an issue with the Tests lists field for an email message when you use Internet Explorer 11. Previously, when you clicked the binoculars in the field and selected a list of recipients, a different list appeared in the Test lists field when you returned to the email message design page. To resolve this so the list you select appears in the field, a rowindex attribute has been added to the code that now selects the list. | 440898 | |
When you use Blackbaud Internet Solutions, this fix updates the Transaction Manager part to display the date the last payment was made for a recurring gift. Previously, the part displayed the recurring gift's last scheduled payment date on the web page. For example, the last scheduled payment date was July 20, but it was paid on the July 18. With this fix, the part displays July 18 instead of July 20. | 415128 | |
When you use responsive design on your website, it was possible for the edit image gear icon to appear large. To fix this issue, the icon width and height has been set so it is no longer impacted when you use custom css on a page. This fix applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 392674 | |
When you use the Academic Catalog in Blackbaud CRM and integrate the data with a Profile Update Form in Blackbaud Internet Solutions, the College/School, Division, Department, Sub Department, and Degree type fields now display for affiliated schools on the profile update web page. Previously, Blackbaud Internet Solutions did not display affiliated school information. | 379848 | |
When you use the Business Phone merge field on the Profile Display part on your Blackbaud Internet Solutions website, the primary business phone number now appears on the Directory search results. Previously, the first business phone number on the constituent record appeared in the search results which made it possible for an inactive business phone number to appear. To fix this issue, the order clause is now introduced on ISPRIMARY field in stored procedure dbo.USP_BBNC_CONSTITPHONEOREMAIL. | 405217 | |
With this change, "Fundraiser" constituencies can be deleted even when the fundraiser is associated with a prospect, as long as at least one additional "Fundraiser" constituency exists. | 327538 | BB745664 |
With this fix, the fundraiser title on a fundraiser record now always displays the fundraiser’s current position title. | 352202 | BB747608 |
With this fix, when duplicate records exist in a Constituent batch, a constituent’s middle initial or middle name now displays in the summary information on the “Duplicate record check” screen. | 299109 | BB742784 |
Installer filename | SHA-1 Hash |
---|---|
BlackbaudInstaller.exe |
Comment | Work Item | Knowledgebase | Patch |
---|---|---|---|
A date and time error no longer appears on a constituent's CRM record for non-US formats in the Birth date, Email address, and (phone) Number fields when the record includes data submitted from the Profile Update form on your Blackbaud Internet Solutions website. This error previously occurred when the profile form did NOT include these fields. A standard date format is now used for all applicable fields to eliminate the error message on the constituent's record. This also ensures date formats are consistent between Blackbaud CRM records and the form in Blackbaud Internet Solutions. Note, the standard date format was previously applied only to fields that were included on the form. | 323061 | 24 | |
A number of query views were changed in such a way to make them incompatible with ad-hoc queries and export definitions created prior to the changes. These query views have been corrected so that those queries and exports will continue to function properly. The following query views were impacted: Application User Alert Settings, Application User Alert Type Setting, Blackbaud Internet Solutions Client Users, Event Donor, Order Payments, Sales Orders, Sponsorship, WealthPoint Affluence Indicators, WealthPoint Biographical, WealthPoint Business Ownership, and WealthPoint Private Foundations. | 278836 | BB740645 | 15 |
A payment to a matching gift claim in Enhanced Revenue Batch now maps to a general ledger account during batch validation. | 291049 | BB741369 | 15 |
A pending email address for a website user now appears on the Profile Display part in Blackbaud Internet Solutions. A pending email address occurs when a profile transaction exists in Blackbaud CRM, but it has not been processed to the constituent record. Previously, pending email addresses did not display on the Profile Display part until the transaction was processed to the constituent record. | 423402 | BB750381 | 53 |
Activation no longer fails for a marketing acknowledgement created from a template with a rule that includes a name format override that uses Advanced name options for spouses. I.e, Override address processing / name format rules is selected on the Address Processing tab for the template rule and the selected name format option uses Advanced name options for spouses ("The spouse does not qualify or is excluded from the process" or "Both spouses will be mailed separately within the process" is selected on the Joint name formats tab of the name format option). | 333268 | BB746247 | 28 |
Ad Hoc Query processing will now fail if any fields have been removed due to changes in query views. | 275789 | 9 | |
Add Donations button on the Donations tab of a Blackbaud Friends Asking Friends event record now appears so offline donations can be added. | 284156 | 15 | |
Add required field validator for email when multi address is off. | 277782 | 13 | |
Add site security to adjustment report. | 303805 | BB742438 | 20 |
Added compatibility handling for Event Registration Form parts created before 6.53. | 268189 | 3 | |
Added missing delete permissions to the merge constituents processes. | 305276 | 20 | |
Address a divide by zero error that can occur under circumstances where a finder file import sets the rental quantity on a marketing effort segment and the underlying list segment has a rental quantity of 0. | 268242 | BB740553 | 13 |
Addressed an issue with the formatting of ask ladder multiplier values under regional settings where the decimal separator is not a period. | 267235 | BB740545 | 13 |
Addressed subquery and performance issue when loading the Constituent Revenue history tab. | 273491 | 13 | |
Addressed summation and performance issue for Total Giving. | 273492 | 13 | |
Addresses permission error when running the Constituent merge and Merge two constituents processes. | 304128 | 20 | |
Addressing issue where attribute categories flagged for delete are still available to be added to records. | 277991 | BB740740 | 13 |
Addressing issue where attribute categories flagged for delete are still available to be added to records. | 277991 | BB740740 | 13 |
Addressing timeout issue when submitting wealth screen. | 276076 | BB741304 | 13 |
Adjust Fundraiser Sync to work with additional BBNC sites. | 275730 | BB741335 | 8 |
Adjust the rejoin/renew/join calculations on the Membership Retention KPI and the Membership renewal report so they use the same criteria and display the same results. | 274047 | BB734699 | 28 |
After a website user submits educational institution data on a Profile Update form on your Blackbaud Internet Solutions website and you view the data on the Educational histories tab in the BBIS Profile Update Transaction Batch before you commit the batch, the program now correctly matches and updates the data on the user's constituent record. Previously, educational institution data duplicated on the constituent record. To correct this, logic has been added to the back end so the program matches the data instead of creating a duplicate. | 356215 | 37 | |
Allow finder number to be passed in the query string to a membership online part. | 275363 | 13 | |
Allow membership discounts to be queried upon. | 268594 | BB740583 | 13 |
Allow memberships to be added with a payment type of credit card but without the card information. The revenue record is still created. | 268766 | BB740446 | 13 |
Allow the output of correspondence processes and some marketing effort processes to be deleted via global change. | 266063 | BB738393 | 1 |
An error message and process failure no longer occur when the "Anonymous email subscriber matching" process runs in Blackbaud Internet Solutions when it encounters a matching constituent email address in Blackbaud CRM that is marked "Do Not Email." Now when the process encounters a match for an anonymous email address with one that is marked "Do Not Email", it continues successfully and a "Read more" message informs you the program did not match the addresses because the Blackbaud CRM email is marked "Do Not Email." | 325453 | BB745469 | 34 |
An error message no longer appears and an extra tab no longer displays in BBIS Profile Update Transaction Batch when a user updates the Country or State field on the deprecated Profile Form part on your Blackbaud Internet Solutions website. To correct this issue, field mapping between Blackbaud CRM and Blackbaud Internet Solutions for countries and states has been updated. | 364502 | 37 | |
An error message no longer appears when non-US date formats are used for date fields in the BBIS Profile Update Transaction Batch in Blackbaud CRM. A standard date format is now used for profile transactions from Blackbaud Internet Solutions to make sure date formats in the batch display the same format used in Blackbaud CRM. | 302359 | BB740867 | 24 |
An error no longer appears in Enhanced Revenue Batch when you use Multicurrency in Blackbaud CRM and a website user submits a donation on your Blackbaud Internet Solutions website in a currency that is not in your default account system in the batch assignment. To correct this, the USP_BBNC_GETCURRENCIESFORBATCHDOWNLOADBYACCOUNTIDFORUSERID has been added to use the default currency set in Blackbaud CRM to check the available currencies when a default account is not defined. | 324956 | 41 | |
As part of the AddressFinder process, you get a file back from Blackbaud with address information. On this step, if your data tune-up settings indicate that address data should not be abbreviated, you could sometimes get an error for certain types of addresses. For example, this error could occur for addresses in Washington, DC that had two spaces or a period followed by a space preceding a single letter, or for addresses with two spaces or a period followed by a space preceding the word 'Via.' This fix allows you to process such addresses without error, even if your data tune-up settings are set to not abbreviate. | 328686 | BB744047 | 24 |
As per the functionality of Advanced Donation Form, the system should allow using Direct Payment and Payment 2.0 part as well. But in the existing implementation, the code is written to log error messages when payment is to be done through Direct Payment only. In the new implementation, checks to log error for payment done using Payment 2.0 part has been added. | 391105 | BB750210 | 53 |
Assign letters process fails when validating selections. | 271775 | 13 | |
Avoid displaying the "This constituent might be a duplicate" error twice in Enhanced Revenue Batch. | 272154 | 13 | |
Because of a change introduced in a recent patch, sometimes business processes time out before they can finish running. This happens because the default timeout is incorrect when running from a business process. This fix corrects the timeout for business processes. | 329377 | BB743673 | 24 |
Blackbaud Internet Solutions now includes an application setting key, ApplicationBypassPath, to allow application security and routing to bypass the application path so the custom Shibboleth ISAPI filter for IIS can capture and handle requests. This fix addresses a unique issue for a customer. | 292170 | BB742518 | 37 |
Business Process Duration KPI lookup is now limited to only looking for business process duration KPI instances that measure the executing business process. | 277801 | BB704130 | 9 |
Business processes that involve site security, could sometimes be slow to run. This fix addresses slow performance for those business processes. | 319378 | BB743396 | 24 |
Calculate gift fees based on the receipt amount rather than the transaction amount. | 278571 | BB741570 | 15 |
Change an error message to be more informative during an issue where, when the credit card process fails, cards might have been charged, but CRM has no knowledge of the state of the process. Message now reads, "No authorization codes from the payment processor exist for credit card transactions in the batch. Either the credit card process has not been run or it failed to complete. If it failed to complete, check with the payment processor to determine whether the payments have been processed before you run it again." | 278741 | 15 | |
Change application detail smart field to search for Financial Transaction Line Item queries. | 290934 | BB742376 | 15 |
Change Installment Plan Payment Query record type from Revenue Application to Financial Transaction Line Item. | 291972 | 15 | |
Change Revenue Application record type to Financial Transaction Line Item when you import selections. | 278901 | BB740438 | 15 |
Change the payment's debit account if linked to a deposit when editing the application detail. | 290834 | 15 | |
Changed the site filter dialog to only auto expand in IE and Firefox if there are a reasonable number of sites. | 297845 | BB741711 | 18 |
Changes made to images by a user with full image rights, are now approved if "Require approval for all images uploaded by users" is not checked. | 320667 | BB744663 | 33 |
Checking for existing client to organization relationship before commiting the batch. | 279602 | 13 | |
Child Age should show 0 when less than 1 not N/A in BBIS sponsorship search. | 275040 | BB741256 | 13 |
Code table security will now be properly respected for all code tables which have it enabled. | 280330 | BB741286 | 14 |
Constituent History Report now displays the correct date format for international regions. | 304220 | BB743188 | 20 |
Constituent merge process no longer fails when a user chooses not to merge stewardships. | 282383 | BB741986 | 15 |
Constituent Profile pervasive search in the ClickOnce version now correctly launches the search screen with the search parameters you entered along with the refreshed results. | 292036 | 15 | |
Constituent Smart Queries now respect site security if it is enabled. | 285873 | BB741701 | 14 |
Constituents ad-hoc query now respects "Is primary contact" field when you use the "Households Belonging To\Household Constituent\Household Members\Is primary contact" filter criteria. | 282041 | BB741419 | 15 |
Constituents inactivated during the merge process should not be included in the possible duplicate constituents results. | 289219 | BB739553 | 15 |
Correct a cosmetic issue on the Recent and upcoming activities section on the Summary tab of the Constituent page when the Details field contains a very long string. This fix applies to the SmartClient only. | 311515 | 20 | |
Correct a cosmetic issue on the Recent and upcoming communications section on the Summary tab of the Constituent page when the Details field contains a very long string. This fix applies to the SmartClient only. | 306336 | BB739482 | 20 |
Correct an error in Constituent Update Batch when trying to update a constituent that has duplicate phone numbers or email addresses. | 276096 | BB740821 | 13 |
Correct an error that would occur when merging two constituents that were both secondary solicitors on that same prospect plan. | 297681 | BB742203 | 15 |
Correct an issue when performing Word merges that can be caused by the way that different versions of Word format merge fields. | 268487 | BB740470 | 9 |
Correct an issue with mail merges that can be caused by using newer version of Word to open the merged document. | 274373 | BB741058 | 9 |
Correct an issue with mail merges that can be caused by using newer version of Word to open the merged document. | 272756 | BB741044 | 9 |
Correct issue in BBIS where the 'Do not email' was not honored unless an email start date was set for the constituent record in CRM. | 272762 | BB740643 | 13 |
Corrected record type on the Interaction Edit Form to allow attribute data form extensions. | 269338 | BB740810 | 15 |
Correcting issue with email links. | 268265 | 4 | |
Corrects upgrade failure for accent insensitive databases when populating the address standardization translations table. | 273393 | 6 | |
Created a feature where Email data from Luminate Online can be reported on through Blackbaud Data Warehouse (BBDW). | 367893 | 41 | |
Currently, when you leave your browser open and idle, the page automatically logs you out after a set amount of time. However, if you leave your browser open but close the tab that the program is in, the page does not log you out. This fix addresses the issue so that you are logged out of the system in both of these scenarios. | 322044 | BB744850 | 24 |
Default tribute letter field is now appropriately disabled when the constituent is marked deceased or not specified when adding or editing a tribute. | 319537 | BB742720 | 24 |
Deleted pledge recognitions are getting displayed on the recognition history tab of the constituent, so after this fix they will not be shown. | 304598 | BB743031 | 24 |
Documents in menus shown only to those with permission. | 275444 | BB741097 | 10 |
Drop down fields displayed on mobile data forms are now displayed next to the field caption, rather than overlapping the field caption. | 279232 | 13 | |
Due to a previous bug, batch payments processed successfully for terminated sponsorship recurring gifts. This resulted in the activation of previously terminated sponsorship recurring gifts. With this fix, data is corrected and re-activated sponsorship recurring gifts are set back to terminated. | 302134 | BB742940 | 28 |
Duplicate phone numbers no longer appear in a BBIS Event registration batch when an event registration form is submitted on the website. This only occurred when a constituent had a phone number with a different type than the one mapped to for "Home" in Sites & settings in Blackbaud Internet Solutions. | 289223 | BB741811 | 15 |
During batch validation, we no longer display a row error for rows which have a credit card token, but do not have an authorization code. The error will now be displayed only when you attempt to commit the batch. | 402360 | 53 | |
During batch validation, we no longer display a row error for rows which have a credit card token, but do not have an authorization code. The error will now be displayed only when you attempt to commit the batch. | 401008 | 41 | |
During the validation and commit process, this fix addresses the creation of duplicate address records after information is imported into a constituent update batch. For example, if the address from an import file is the same as an existing address for a constituent, no duplicate address is created. The problem occurs when the program does not recognize that the address in the import file is currently an existing address in the database and, therefore, creates a new address record. With this fix, after the import runs, the validation and commit processes update the existing records appropriately. | 275756 | BB741350 | 24 |
Editing a pledge with posted payments will create less unnecessary payment adjustments. Previously, if one posted payment required an adjustment due to editing the pledge all posted payments were adjusted. | 300522 | BB742000 | 20 |
Enhanced revenue and revenue update batches should correctly determine if the constituent lookup ID search found an existing constituent. | 302216 | BB742423 | 20 |
Enhanced revenue and revenue update batches should correctly set the batch row's context when using the constituent lookup ID search. | 305289 | BB742526 | 20 |
Enhanced revenue batch can now automatically display the Apply to commitments form when a constituent is chosen via finder number. | 297785 | BB740739 | 20 |
Enhanced Revenue Batch now commits successfully when recognition credits are added for a new constituent. | 290861 | BB742308 | 15 |
Enhanced revenue batch should not force redefault an application when the amount is set to its initial value. | 291789 | BB742478 | 20 |
Enhanced Revenue Batch's Apply to commitment form can now apply amounts to sponsorship commitments in the ClickOnce version of the program. | 284172 | BB741437 | 15 |
Ensure that canceled registrants do not show up in the event seating assignment list. | 284787 | BB741205 | 15 |
Ensure that event registrants are removed from their seating assignments when they are marked as "Will not attend" or "Canceled." | 284788 | BB741067 | 15 |
Ensuring that Receipt is added and available to processed transactions in Transaction Manager part. | 275448 | BB741055 | 13 |
Ensuring that SQLSnap2006 does not fail due to manifest errors. | 279874 | 11 | |
Error no longer occurs on the Add or Edit availability screen accessed from the Availability tab of a volunteer record when using a locale with a day-month-year date format. | 285164 | BB742148 | 24 |
Exception batches for Enhanced Revenue Batch now respect constituent duplicate match parameters. | 272153 | 13 | |
Fix a download error for ad-hoc query results. Previously, when you downloaded an ad-hoc query's results to Excel or .csv format, you sometimes received an error and the file did not download. | 325208 | 24 | |
Fix a performance issue that caused the Uncommited batches screen to load slowly. | 319185 | 24 | |
Fix a performance issue when adding an organization or group/household as an event registrant. Previously, when you added the organization or group as the registrant and then selected the registration options, the drop-down field to select the registrant for each registration option would time out if there were many constituents associated with the organization or group. Now the drop-down field includes the first 100 constituents, sorted alphabetically by last name. However, you can still click Search to select any constituent. | 317573 | BB743304 | 28 |
Fix a performance issue when merging constituents in large databases. | 301635 | 24 | |
Fix a timeout issue with the Revenue summary section on the Summary tab of a group or household constituent record, when the group had many members with many revenue transactions. | 297920 | BB742711 | 20 |
Fix an "Invalid URL" error that occurs when publishing a website for a Blackbaud Friends Asking Friends event in Blackbaud Internet Solutions. | 284050 | 15 | |
Fix an error in Revenue Update Batch in the ClickOnce version of the program when you edit installment designations on a pledge. Now when you edit the installment designations, the correct receipt amounts are placed in the installments grid on the Edit Installments screen. If you have any existing Revenue Update Batches with pledges in the ClickOnce version, you should remove and re-add those to the batch before you edit the installment designations. | 306458 | BB743351 | 17 |
Fix an error that prevented users from deleting matches on the Preview Merge tab of a Constituent Merge process. | 290258 | BB740953 | 15 |
Fix an error when attempting to import multiple benefits for a membership in Membership Dues Batch. | 279880 | BB741782 | 20 |
Fix an error with the R68 Update revenue records process, which is part of the Gift Aid functionality for the UK. The error prevented this process from completing successfully when revenue transactions in the process were marked as "Do not post." | 326872 | BB745607 | 22 |
Fix an error with viewing the standardization table in Global Data Entry Settings. | 285163 | BB742147 | 15 |
Fix an issue displaying the Do not mail reason code. Previously, when an address had an end date, the Do not mail reason code was disabled. It is now enabled regardless of the end date on the address. | 321566 | 24 | |
Fix an issue identifying sponsorship children in the data warehouse. Previously, the ISCONSTITUENT column showed a 1 for sponsorship children. These records now have a value of 0 in the ISCONSTITUENT column on the BBDW.DIM_CONSTITUENT table. | 320540 | 24 | |
Fix an issue in EmailFinder batch. This fix ensures that the correct email address is marked as primary given the email address(es) present on the constituent record, the EmailFinder process settings, and the email addresses being processed by the batch. One email address for a constituent should always be marked as primary. If no email address exists on constituent record, the one from the EmailFinder process is automatically marked as primary. When the EmailFinder process has an updated email address for a constituent, the updated email address is marked as primary if the old email address was marked that way. | 274035 | BB740653 | 20 |
Fix an issue in Enhanced Revenue Batch in the ClickOnce version of the program where the Apply to commitments screen was not automatically displayed if a constituent with commitments was selected using a finder number. | 277988 | BB740739 | 15 |
Fix an issue in Enhanced Revenue Batch when adding a second payment for an event registration. Previously, if a payment for an event registration had been added in Enhanced Revenue Batch and then, in a separate Enhanced Revenue Batch, you attempted to add an additional payment for the event registration, you would receive an error because the program was attempting to create a duplicate event registrant. This fix ensures the error no longer occurs. It also includes a revision to remove any invalid duplicate event registrants. | 305143 | BB742324 | 28 |
Fix an issue in the display of currency data on user-defined data lists created from ad-hoc queries. Previously, user-defined data lists created from ad-hoc queries that included currencies other than the organization's currency did not use the correct currency symbol. The currency symbol now displays correctly in these data lists. | 321702 | BB744800 | 24 |
Fix an issue related to object reference error on updating a fully paid pledge amount multiple times. | 276370 | 15 | |
Fix an issue so that Enhanced Revenue Batch properly saves new constituent bank account names on commit. | 287016 | BB742241 | 15 |
Fix an issue so that event invitees who were excluded from the last invitation process now show up correctly as "Excluded from last send." | 317576 | BB743614 | 28 |
Fix an issue that causes the page scroll bar to move up or down when you switch between tabs on a screen when using Internet Explorer. | 299285 | BB741668 | 15 |
Fix an issue that sometimes happened when creating an ad-hoc query. Previously, when you created an ad-hoc query, you were able to see smart fields that you might not have security rights to see. If you used any of these smart fields in your query, you got an error when you tried to save the query. This fix prevents users from seeing smart fields that they do not have security rights to see, so this type of error no longer occurs. | 324953 | BB734941 | 24 |
Fix an issue that was causing slow performance when you searched for a constituent by phone number. | 321802 | BB744028 | 24 |
Fix an issue to now set the registration type and registration status correctly for guests in Event Registrant Batch. Previously, you could set the registration type and registration status for event registrants; however, when a guest was added, the guest automatically had a registration type of "Preregistration" and a registration status of "Registered" regardless of what was specified for the event registrant. Now when you add a guest to an event registrant in Event Registrant Batch, the registration type and status for the guest match what was specified for the event registrant. In addition, you can mark the guest as attended; however, if the event registrant has a registration status of "Registered (will not attend)" or "Canceled," we do not save the attended status for the guest because we assume that if the event registrant is not at the event, the guest of registrant will not be there either. | 289157 | BB742318 | 20 |
Fix an issue when calculating the expiration date when rejoining a membership where the membership term "Is fixed (based on calendar year, etc.)" and the membership has an expiration date with a "push to next period after" expiration date specified. | 274057 | 15 | |
Fix an issue when refunding a recurring gift installment payment by editing or adjusting the payment amount to zero when the recurring gift still had one or more future installments which had also been paid and adjusted to zero. The foreign key constraint error "FK_RECURRINGGIFTINSTALLMENTPAYMENT_RECURRINGGIFTINGTALLMENTID" no longer occurs. | 291917 | BB742032 | 24 |
Fix an issue when running a smart query created from an ad-hoc query. Previously, when a user ran a smart query based on an ad-hoc query that was created by another user, the query results were based on the security rights of the user who originally created the query. Now, query results reflect the security rights of the user running the query. | 306400 | BB741701 | 28 |
Fix an issue when sponsorship Gift Aid was claimed after changing the original individual constituent on the revenue record to an organization, group, or household. Now only individual constituents are eligible for sponsorship Gift Aid, which matches how non-sponsorship Gift Aid works. | 317888 | 20 | |
Fix an issue when the receipt amount of an event registration did not match the receipt amount of the event registration payment. Previously, when an event registration option included a price and a cost, the receipt amount displayed correctly on the event registrant record, but when the payment for the event registration was entered, the payment receipt amount did not match the event registration receipt amount. Now the payment receipt amount matches the event registration receipt amount. | 310600 | BB743151 | 20 |
Fix an issue when updating constituent addresses to set more than one as the primary address in Constituent Address Update Batch. | 284775 | BB740895 | 15 |
Fix an issue when updating household phone numbers and email addresses shared with household members in Constituent Update Batch. | 284968 | 15 | |
Fix an issue when users attempt to view the Planner calendar filtered to "This Year" when marketing plans have a partial start date, such as month and year only, rather than a full date. | 280381 | BB741833 | 15 |
Fix an issue when you edit a recurring gift with no "Next transaction" date in a Revenue Update Batch. Now if you add a "Next transaction" date for the recurring gift in the batch, the date of the next transaction will save correctly when you commit the batch. | 317454 | BB743400 | 28 |
Fix an issue when you filter ad-hoc queries by date fields that do not require a month/day/year value. Previously, when you used these fields as filters, sometimes the query results were not correct. | 320271 | BB744573 | 24 |
Fix an issue where a lifetime member did not show up in a Constituent search when the "Member" constituency was used as a filter. | 273688 | BB740712 | 15 |
Fix an issue where an error was shown for the member cards data list on a constituent’s member view page. Now, when you go a constituent’s Memberships tab and click on a membership, you can view the member view page without an error. | 300658 | BB743136 | 20 |
Fix an issue where benefit mappings could be applied incorrectly. | 297484 | BB742646 | 20 |
Fix an issue where event receipt amount was not being recalculated properly when editing benefits on a registration. | 281972 | BB741677 | 15 |
Fix an issue where event receipt amount was not being recalculated properly when editing benefits on a registration. | 274038 | 15 | |
Fix an issue where events were duplicated on the event calendar for each coordinator listed on the event. Events now show once on the event calendar regardless of how many coordinators there are. | 299513 | BB741732 | 20 |
Fix an issue where membership attributes created before a membership program did not appear in queries or export definitions under Membership Programs. Now, all membership attributes appear and are available in new queries and export definitions. If you have existing queries or export definitions and want to include all membership attributes, you can edit them, select the membership attributes, and re-save them. | 316570 | BB742942 | 28 |
Fix an issue where pledge receipt amounts were being incorrectly calculated after adding more installments to a partially paid pledge. | 274063 | 28 | |
Fix an issue where solicitors were not being displayed on the Solicitor tab of the Matching Gift Claim record, but the header/summary indicated there was a solicitor. | 276380 | 15 | |
Fix an issue where some of the fields on the add or edit an event form would be pushed off of the form. This occurred when using Chrome and when the event was associated with one or more sites. | 304159 | BB743032 | 20 |
Fix an issue where Step 2 (Get file from Blackbaud) of the PhoneFinder process did not respect phone number format settings and created PhoneFinder batches with unformatted numbers. Now, when the PhoneFinder batch is created in Step 2, each phone number will be formatted according the format specified for the country used on the address of each record in the submission file. Phone formats for countries are defined on the Countries and states page in Administration. If a country does not have a phone format specified, no formatting is applied to those phone numbers in the PhoneFinder batch. If you have existing PhoneFinder batches, the numbers will not be formatted. New batches created in Step 2 of the PhoneFinder process will have phone numbers formatted. | 271420 | BB740439 | 20 |
Fix an issue where you cannot adjust or edit a payment for an inactive recurring gift using Revenue Update Batch. | 301741 | BB742939 | 24 |
Fix an issue which caused the dates shown in the marketing planner Gantt chart to be off by a month. | 284462 | BB742080 | 15 |
Fix an issue which prevented a user from being able to download the paperless mandate instructions file for the paperless mandate process in a UK system. | 324419 | 24 | |
Fix an issue with constituent mail preferences when changing a mail type after mail criteria has been entered. Criteria fields are now cleared when they are not applicable to the selected mail type. | 278381 | BB741332 | 15 |
Fix an issue with editing a posted revenue transaction that has an associated Gift Aid claim. Previously, the GL distributions were not being created for the Gift Aid claim when the revenue designations were changed. This issue occurred only when there was no default account system set up on the General Ledger Setup page in Administration. | 350438 | BB747370 | 34 |
Fix an issue with linked custom reports. Previously, when a custom report was linked to another custom report with a parameter, drilling into the linked report caused an error. The linked report's parameter section is now displayed when you access the linked report from the other report. | 320508 | 24 | |
Fix an issue with Mobile Constituent Search so you can search for constituents by ZIP Code. | 281886 | 15 | |
Fix an issue with the auto-save functionality in batches. When you have this option enabled and there is an error in a batch row, such as a required field left empty, you get an error. Previously, even after you fixed the problem, the row still showed an error, so the row was not saved. | 320621 | 24 | |
Fix an issue with the way results are displayed when running a smart query from an ad-hoc query. Previously, when you created a smart query from an ad-hoc query that included aggregated data and chose to exclude an output field, the results did not show the data aggregated as indicated. For example, you might create an ad-hoc query that includes revenue amounts and dates. When you create a smart query from this ad-hoc query, you can select not to include the dates, so as to show total amounts aggregated by constituent, rather than showing each individual donation received for each constituent. Even when you selected not to include the date, the results did not display the date column but still showed a separate entry for each date. With this fix, the resulting smart query respects your output type selections and, in this example, would only show one row per constituent with an aggregated revenue amount. | 318363 | 28 | |
Fix an issue with the way the standard acknowledgement output format in Marketing and Communications. Previously, it would not handle custom name formats for constituents. | 280213 | 15 | |
Fix an issue with vertical and horizontal scroll bars that are sometimes not visible. This happens when you maximize a Search screen to full screen. | 280127 | BB741807 | 15 |
Fix Blackbaud Friends Asking Friends issue with email notifications not being sent to participants when donations are made on their pages. | 283180 | BB738780 | 15 |
Fix database revision 141415 to avoid revision set 1300 failing during upgrade to Blackbaud CRM 3.0, Service Pack 2. | 297609 | BB742667 | 15 |
Fix database revision 6225 to account for imported list segments without a record type. | 287044 | BB742247 | 15 |
Fix Direct Marketing ad-hoc queries based on the "Constituent (RE7)" record type with fields from the Membership node. | 297636 | BB742672 | 15 |
Fix error passing credentials to SSLAutolog.ashx when trying to edit a Blackbaud Friends Asking Friends event in CRM. | 283178 | BB739301 | 15 |
Fix error when importing a revenue record type selection. | 291602 | BB718736 | 15 |
Fix issue encountered when you use the "Formatted mail tribute acknowledgement output" format with name formatting for Tribute Acknowledgement process. | 290802 | BB742412 | 15 |
Fix issue related to payment adjustments being created when increasing the original posted pledge amount. | 281345 | TC-10056260 | 15 |
Fix issue so an anonymous newsletter recipient, who signed up on the Anonymous Newsletter Subscription part, successfully opts out of a newsletter when selecting the global opt-out checkbox on the email preferences web page. This applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 284976 | BB741970 | 15 |
Fix issue so revenue attributes for Blackbaud Internet Solutions donation transactions successfully download into a batch. | 281760 | BB741944 | 15 |
Fix issue so that the business unit on an appeal will display on an event registration payment when the payment includes that specific appeal. | 273515 | BB740574 | 15 |
Fix issue when application and applied amount information for a recurring gift payment in Enhanced Revenue Batch was removed from the transaction when the batch was opened by a user with different Internet Explorer language settings. | 276257 | BB741378 | 15 |
Fix issue when gift fee adjustments update all gift fee line items in the database. An adjustment to the gift fees on one payment no longer affect the gift fees on any other payment. | 279654 | 15 | |
Fix issue where application field on grant award payment displayed as blank in Revenue Update Batch. | 276372 | 15 | |
Fix issue where business units associated with appeals on planned gifts did not copy over to the planned gift revenue. | 276374 | BB736724 | 15 |
Fix issue where write-off amounts on the Revenue History tab of a constituent display as greater than the actual write-off amount when the write-off occurred for a pledge with multiple splits. | 286035 | BB742194 | 15 |
Fix issue with adjustments when changing a sold stock's median price. Adjustments should be created if the amount, fees, or units sold change. | 279671 | 15 | |
Fix issue with code table not auto-completing correctly in batch. This function was using Val and RawVal interchangably but only one was set. | 298320 | BB742750 | 20 |
Fix issue with security and blank sites which prevented users who are not system administrator's from seeing data in the Prospects Without Recent Activity tab on the Prospects page in Major Giving Management. | 280520 | BB741737 | 15 |
Fix missing constituent names in exported Excel files. Previously, when you exported query results to Excel and the query results included constituent names, the Constituent Name column sometimes appeared blank. | 325207 | 24 | |
Fix missing sponsor constituency for the target constituent of a merge from a reassigned sponsor. | 296855 | BB742398 | 15 |
Fix revenue constituent lookup ID search to default to only exact matches. | 282364 | 15 | |
Fix revision issue when upgrading from 2.94 to 3.0. | 280389 | 11 | |
Fix several issues surrounding address validation in Constituent Batch and Constituent Update Batch. Correct a cosmetic issue on the Address validation form shown when validating an address in batch. Previously if an address was invalid, a message appeared on the batch row indicating the problem. You could click on the message to view the Address validation form. The form had an unnecessary warning icon with a blank error message at the top. Now the warning icon no longer appears when you view the Address validation form. Correct an issue where ZIP code/Postcode was not being copied from the batch row to the Address validation form. Correct an issue where validation did not support multiple addresses in Constituent Update Batch. Multiple addresses can now be validated, although they must be done one at a time. Validation will need to be run again in Constituent Batch and Constituent Update Batch if these issues have previously prevented successful address validation. | 302072 | BB742971 | 20 |
Fix so that the Type of gift field in Blackbaud Friends Asking Friends Donation form is required. | 284169 | 15 | |
Fix stack overflow exception in Revenue Update Batch in the ClickOnce version of the program when modifying currency fields after the type code is changed. | 281780 | BB741924 | 15 |
Fix the "Insert Hyperlink" dialog used by the Direct Marketing email editor to include special pages (privacy policy, home, etc.) from all Blackbaud Internet Solutions sites. | 292251 | BB742533 | 15 |
Fix timeout issue for the Revenue History page when you click History under More information for a revenue transaction. | 276962 | BB740458 | 15 |
Fix timeout issue in the KPI dashboard. Previously, when you tried to load the KPI dashboard using WebUI, you received a timeout error and the dashboard failed to load. | 317569 | BB744215 | 24 |
Fixed a bug on the Individual-Spouse-Business add form where a newly-added spouse got a duplicated address when address validation was used. | 264389 | BB740030 | 13 |
Fixed a revision failure when database contains a segment with a consolidated list member and a constituent member in the same segment. | 273738 | 13 | |
Fixed an error in the Name Format Query. It no longer occasionally inserts "{CONDBREAK}" into the name format. | 305353 | BB742170 | 20 |
Fixed an error that can occur when downloading membership transactions for constituents without an address. | 274048 | 13 | |
Fixed an error with mid-term upgrades in membership dues batch. | 274061 | 13 | |
Fixed an exception in Enhanced Revenue Batch when paying two matching gift claims to the same organization in the same batch. The revenue for the first claim is processed and the second transaction goes into an exception batch. | 266320 | BB739877 | 13 |
Fixed an issue for clients upgrading from a pre 2.94 version of BBDW to a 3.0 or higher version. BBDW will need to be redeployed for this to take effect. | 279587 | BB741747 | 14 |
Fixed an issue preventing users from adding a new membership if a previous one had been canceled. | 267619 | BB740536 | 13 |
Fixed an issue that could cause errors when entering membership dues after a membership installment plan has been edited. | 278075 | 13 | |
Fixed an issue that prevented BBDM/RE7 clients from refreshing marketing efforts that use finder files. | 302204 | BB743007 | 20 |
Fixed an issue when adding new benefits to an existing record. | 277767 | BB741566 | 20 |
Fixed an issue when posting with specific bank accounts. | 311180 | 20 | |
Fixed an issue where errors can occur on KPI dashboards that have multiple tabs. | 267263 | BB739789 | 9 |
Fixed an issue where household data cached for use by marketing functionality wasn't being updated correctly when households were dissolved. The cache will be rebuilt to address any existing instances of this problem. | 268684 | BB740620 | 13 |
Fixed an issue where recognition types were not being applied to membership dues. | 268390 | BB740443 | 13 |
Fixed an issue where the Account System was grayed out when adding an event registration or recurring gift transaction in Enhanced Revenue Batch. | 272661 | 13 | |
Fixed an issue which caused extra carriage return / line feed characters to be appended to the address blocks of constituents created from marketing list members using a finder number. | 298322 | 20 | |
Fixed an issue with adding an attribute to an existing batch row when the batch template does not contain the comment for the attribute. | 310475 | BB743479 | 18 |
Fixed an issue with batch export timing out in ClickOnce. | 268781 | BB729596 | 9 |
Fixed an issue with designation not being available as a find and replace field in batch. | 276309 | BB741353 | 9 |
Fixed an issue with DisplayPromptArea attribute for reports not being respected in ClickOnce. | 316248 | BB743662 | 18 |
Fixed an issue with expiration date calculations when mid-term upgrading a membership. | 274059 | 13 | |
Fixed an issue with exporting batches in ClickOnce. | 289916 | BB742212 | 14 |
Fixed an issue with primary member switching when renewing a membership. | 269075 | BB740400 | 13 |
Fixed an issue with site security on the Recognition History tab of a constituent record. | 266111 | BB740396 | 13 |
Fixed an issue with the Constituent Profile report. From a group member's report, the prospect plans section now shows information for the constituent's group. From a group's report, the section shows information about prospect plans for the group members. | 304011 | BB742219 | 24 |
Fixed an issue with using custom images. | 305536 | BB743311 | 18 |
Fixed Application Info field being disabled in Enhanced Revenue Batch in ClickOnce when we are trying to make a payment for another constituent's commitment. | 268661 | BB740448 | 13 |
Fixed bug in enhanced revenue batch where a finder number of zero was trigger a search and populating unwanted values on the row. | 266024 | 13 | |
Fixed clearing of Application field when applying 3rd party commitments. | 278417 | 13 | |
Fixed correspondence process to accommodate longer state abbreviations. | 272469 | BB740979 | 13 |
Fixed Enhanced Revenue Batch bug where recognition credits were not defaulting during import of revenue row with empty revenue stream values. | 268719 | 13 | |
Fixed graying out of the Appeal field in the ERB Batch when Application Info is changed. | 269318 | 13 | |
Fixed incorrect transaction currency defaulting in membership dues batch. | 273714 | BB741102 | 13 |
Fixed issue in membership online BBIS part when using legacy membership programs. | 274052 | 13 | |
Fixed issue related to changing amount on a posted pledge with a single designation, previously the user would be prompted with "The installment splits must balance the pledge". | 276104 | 13 | |
Fixed issue related to the hierarchical display of campaigns on the Revenue Summary tab of a constituent's Revenue and Recognition page. | 268579 | BB738967 | 13 |
Fixed issue where editing a posted payment timed out. | 273200 | BB737715 | 13 |
Fixed issue with creating the consolidated marketing query view. | 272205 | 13 | |
Fixed issue with determining the ask ladder entry amount based on a smart field. | 273829 | BB741025 | 13 |
Fixed issue with incorrect join between Installment and Installment Payment. The Raiser's Edge data mart will need to be redeployed and refreshed for this change to take effect. Any dynamic selections using the Installment Payment query view will then need to be re-saved. | 310148 | 20 | |
Fixed javascript issue with single quotes in educational names in Educational histories and Educational involvements elements for a BBIS Profile Update Form. | 266114 | BB740054 | 13 |
Fixed record type error when creating a smart query from the ad-hoc query add form. | 272389 | BB740987 | 9 |
Fixed smart query date comparison to ignore time. | 274541 | BB741099 | 9 |
Fixed sponsor query returning multiple results when different exchange rates are applied to payments for a sponsorship recurring gifts. | 272155 | BB740367 | 13 |
Fixed sponsorship constituencies to calculate correctly after two constituents are merged. | 273720 | BB740857 | 13 |
Fixed the marketing effort exclusion report to take segmented house file segment members into account. | 276285 | BB741396 | 13 |
Fixed the marketing effort refresh to properly update vendor managed list finder numbers. | 276395 | BB741142 | 13 |
Fixed timeout error for ad-hoc query selection save process. | 291765 | BB741152 | 14 |
Fixes a performance issue on the Current Group Members list on Committee pages. Previously, the list was slow to load on the page and could time out. | 306379 | BB743340 | 24 |
Fixes a performance issue that caused intermitent timeouts on the Import Processes screen. | 318871 | BB744316 | 24 |
Fixes a problem transferring prospect plan status data on the prospect plan dimension to the data warehouse. You must redeploy the Blackbaud Data Warehouse (BBDW) and complete an incremental refresh before changes take effect. | 297997 | BB742721 | 18 |
Fixes a time-out error when processing email alerts. Previously, email alerts sometimes generated a time-out error. This fix prevents those time-out errors when sending email alerts. | 314485 | BB743597 | 24 |
Fixes a timeout issue when assigning feature permissions in ClickOnce. Previously, when you assigned feature permissions and several features existed, the process could time out. | 316682 | BB713540 | 24 |
Fixes an error loading user-defined datalists. Previously, when you generated a user-defined data list from an ad-hoc query, and you used a lookup field as a filter with a blank value, you sometimes got an error when loading the data list. | 317403 | BB744161 | 24 |
Fixes an error when committing constituent batches. Previously, if a constituent batch included a new constituent with a spouse and all address fields other than the Country field were blank for that constituent, the batch commit process threw an exception. | 318664 | BB742625 | 24 |
Fixes an issue viewing the Relationships tab on a constituent record in ClickOnce. Previously, the relationships list could sometimes be blocked from view. | 306369 | BB743339 | 20 |
Fixes an issue when running a query that includes constituency date fields. Previously, in rare cases, this could result in an error when you previewed the results of the query. | 320588 | BB742861 | 24 |
Fixes an issue where importing records into Membership Dues Batch would fail to find the bill to constituent. Now, you can use constituent ID, lookup ID, or name to import records. | 297130 | BB741176 | 20 |
Fixes an issue where the BBDW_FACT_EVENTREGISTRANT package can fail when duplicate user names are encountered. BBDW will need to be redeployed, reset and complete a full refresh for this to take effect. | 278723 | BB741715 | 14 |
Fixes an issue where the member services page would not refresh after changing the installment plan schedule. | 274946 | 13 | |
Fixes the conversion error for nvarchar value getting overflowed for the column in Stewardship Plan process | 305068 | BB743158 | 20 |
Fixing a bug in constituent update batch where aliases were created in cases when they should not have been. | 276265 | BB740628 | 13 |
Fixing an issue where using the constituent lookup ID search in click-once revenue batches could clear the constituent field. | 304820 | BB743109 | 20 |
Fixing auto save in batch in Webshell | 310906 | BB743528 | 18 |
Fixing call to save constituent information when duplicate matching in Enhanced Revenue Batch. | 273767 | 13 | |
Fixing Enhanced Revenue Batch error when no account field is present in the batch row. | 273769 | 13 | |
Fixing error that shows in BBIS transaction manager. | 282927 | 13 | |
Fixing error with dynamically-generated SQL when copying FAF events. | 303828 | BB738757 | 16 |
Fixing issue where menu items containing external links for BBIS and BBNC are not showing for users that are not logged in. | 282479 | BB741990 | 12 |
Fixing performance around installment balance when loading revenue batches. | 270644 | BB739618 | 13 |
Fixing runtime error when no participant attributes are present. | 266002 | 1 | |
Fixing the deployment of the Word and Excel add-ins. | 281661 | 14 | |
For the "Constituent appeal count," "Constituent appeal years," and "Last constituent appeal name" smart fields, when you selected a business unit on the Parameters tab, the fields would not produce output. This issue was fixed. After running the update, clear the results of any existing instances of these smart fields and then re-process them. | 310259 | BB743436 | 24 |
Force state list to always refresh when country is changed on BBIS Profile Update Form. | 273187 | BB740191 | 13 |
Forgotten password emails for Blackbaud Friends Asking Friends now direct website users to the forgotten password page. Previously, the emails directed users to an error or login page. | 327683 | BB745688 | 34 |
Friends Asking Friends users can now search for a company or team using any part of its name. Prior to this fix, only searches that included the first 20 characters of a company or team’s name returned relevant results. | 326172 | BB745496 | 34 |
Generate Revenue Update Batch process now copies the credit card information from recurring gifts into the Revenue Update Batch. | 297183 | BB742544 | 15 |
Honor server cookies in ClickOnce by using a CookieContainer object on SOAP calls and pushing those cookies to the click once application as well so that they are honored in UIModel calls. | 273701 | BB738781 | 9 |
If a Raiser's Edge user was assigned more than one BBNC client ID, you received this error when you refreshed the datamart: Violation of PRIMARY KEY constraint 'PK_BBNCTEAMFUNDRAISING'. Cannot insert duplicate key in object 'RE7.BBNCTEAMFUNDRAISING. After you redeploy the datamart, this issue will no longer occur. | 276363 | BB726363 | 34 |
If the most recent payment to a pledge spanned multiple installments, the program incorrectly calculated the Last payment amount field in the "Formatted mail pledge reminder output - extended" output format for reminders. The program now outputs the Last payment amount correctly. | 319656 | BB744471 | 24 |
If you calculated segment counts for a non-activated effort with test segments, and then edited the source code value on a segment, the source code did not update properly on the corresponding test segment. While the value displayed correctly on the marketing effort, when you activated and exported the effort, the test segments included the wrong source code in the export. We fixed this issue so the source code exports correctly. | 390442 | BB724329 | 41 |
If you have an international database and you map the State field in Blackbaud CRM to the City drop down field in Blackbaud Internet Solutions, website users can now successfully edit their address when the City drop down field contains an apostrophe (for example, Hawke's Bay in New Zealand). This change prevents the apostrophe in the drop down field from interfering with the JavaScript responsible for displaying all elements on the page. There are no changes to data in the back end. | 321508 | BB744758 | 24 |
Implement basic web health events in RE7Service. | 267518 | 2 | |
Implement name, address, city, state, zip, phone, and contact merge fields on the BBIS Event Registration Form part. | 271838 | BB740922 | 13 |
Improve date validation for employer relationship in the Blackbaud Internet Solutions Profile Update form. | 289225 | BB741200 | 15 |
Improve intermittent performance issues with batch datalist. | 337269 | BB741555 | 34 |
Improve performance of Enhanced Revenue Batch when constituents in the batch are also event registrants. | 282594 | BB741400 | 15 |
Improve performance of the Summary tab for a constituent for users who are not system administrators. Information on the tab was slow to load for non-system administrators who were assigned to multiple system roles in Security. | 280078 | BB740527 | 15 |
Improve the accuracy of the Marketing Effort Exclusions Report with regard to email address processing applied to segments with email packages, when address processing is enabled for that segment. Previously, the constituent could appear in the exclusions report twice: once because of the exclusion segment, which is correct, and once because the constituent had a mail preference of "Do Not Send," which is incorrect. | 277600 | BB741574 | 15 |
Improved performance for queries using the loyal donor and major donor constituencies. | 276079 | BB739004 | 13 |
Improved performance when posting deposits. | 302293 | BB741387 | 20 |
Improved the performance of the Assign Letters Process when multiple letters are included. | 270723 | BB737270 | 13 |
Improved the performance of the batch row delete record operation to avoid deadlocks between the credit card processing process and the batch commit process. | 268342 | BB739031 | 13 |
Improved the performance of the BBDW_FACT_EVENTREGISTRANT package during the ETL process | 288929 | 14 | |
Improving add/edit query form performance for non-admin users. | 297331 | BB742186 | 14 |
In a BBIS Profile Update Transaction Batch, educational involvement date fields are no longer blank for previous date values with incorrect month and year formats. This occurred when a website user's online profile information included a date value with an incorrect format on the constituent record in Blackbaud CRM. This fix updates the transaction display so that the dates appear in the batch. | 380159 | 37 | |
In a UK environment, when you change a constituent with a posted payment from an individual constituent to an organization, the Gift Aid refund will now be properly created for the original individual constituent. | 300656 | BB742931 | 20 |
In an Enhanced Revenue Batch, this change applies to individual constituents with matching gift relationships. Previously, when a pledge was added and saved for a constituent through the "Apply to commitments" screen, the following error displayed – "One or more designation amounts is invalid." With this fix, the error no longer displays. | 381109 | 37 | |
In Blackbaud Direct Marketing, we fixed an issue introduced in service pack 7 that caused the Gift amount smart field to fail to deploy. | 410013 | BB751415 | 53 |
In Blackbaud Direct Marketing, we fixed an issue introduced in service pack 7 that caused the Gift amount smart field to fail to deploy. | 409822 | 53 | |
In Blackbaud Friends Asking Friends, an "Arithmetic overflow" error message no longer appears when you deliver an email that includes fundraising group total amounts greater than $999.99 and use the merge fields Group total amount goal, Group Page URL, and Event login URL. This fix correctly converts the decimal number to a monetary value to eliminate the message. | 337999 | 28 | |
In Blackbaud Friends Asking Friends, an error message no longer appears for an uncompleted Fundraising Group Summary business process. This occurred because group donation totals and the number of members did not update during the process. To resolve this, the USP_FAFGROUP_CALCULATE_GROUPSANDMEMBERS stored procedure has been updated to select the necessary data from a pre-organized temporary table instead of organizing the data while selecting it. | 324933 | BB745402 | 24 |
In Blackbaud Friends Asking Friends, an error message no longer appears when you add and edit sponsor information under the event record Sponsor tab. | 284759 | 15 | |
In Blackbaud Friends Asking Friends, an issue has been fixed to properly save social network sharing configuration changes on the Communications tab of the Configuration page. To correct this, the back end configuration list, PROVIDERLIST, has been set to correctly save all changes. | 317085 | BB744019 | 24 |
In Blackbaud Friends Asking Friends, email templates no longer time out when participants click Ask Now under Send Emails in their personal headquarters. | 282867 | BB742017 | 15 |
In Blackbaud Friends Asking Friends, the Event Comparison report now displays the correct revenue totals for Friends Asking Friends events with donations. To correct this, the program now uses both the EventAppeals table and the appeal ID for an event to compare and calculate revenue totals. | 323138 | BB745047 | 24 |
In Blackbaud Friends Asking Friends, the fundraising goals household leaders enter now appear on the website. | 284667 | 15 | |
In Blackbaud Internet Solutions, the correct event name now displays when you customize the event name to display on the Event Registration Form part and associate it with Payment 2.0 and Payment Summary 2.0 parts. Previously, the Payment 2.0 and Payment Summary 2.0 parts displayed the event name from Blackbaud CRM. To correct this, a line was removed from the Sales Order Item Event Registration Add Data Form save procedure that used the event name in Blackbaud CRM. | 333243 | BB743036 | 28 |
In Blackbaud Internet Solutions, the Location field search binoculars on a web page with a Sponsorship Search part now includes locations for opportunities. | 286546 | BB742213 | 15 |
In Blackbaud Internet Solutions, when a user selects a profile field as private, the Directory part no longer returns the user in search results when another user searches on the same field. | 273188 | 13 | |
In Marketing and Communications, images that you resize for email marketing now display correctly in the preview and in the sent email. Previously, resized images displayed correctly in the sent email, but not in the preview. | 305364 | BB742208 | 20 |
In revenue queries, the UK Gift Aid fields "Gross amount" and "Tax claim amount" are now displayed correctly with the appropriate value instead of being blank when Gift Aid does not exist for a revenue type. | 317095 | BB744025 | 37 |
In Revenue Update Batch, update the current totals for the batch in the Batch Property window when an existing transaction is replaced. | 276377 | 15 | |
In the Standing Order Import process, flag an exception when attempting to match payments to written off pledges. | 268247 | BB740440 | 15 |
In the web.config file for Blackbaud Internet Solutions, the new appSetting "AllowDirectDebitForOneTimeGifts" exists so you can allow direct debits for one-time gift custom processes. In Blackbaud Internet Solutions 3.0, Service Pack 4, direct debits were prevented to avoid a reconciliation conflict in the program that occurred between recording the gift in Blackbaud CRM and actually receiving payment from the direct debit transaction. This remains the default functionality for the program. This setting should only be used for your organization’s custom processes that allow direct debits for one-time gifts. | 337266 | 27 | |
In the webshell version of the program, users received an error when trying to edit a marketing effort batch if they did not have security rights to the site associated with the segment. This error no longer occurs. | 337596 | BB746522 | 34 |
In version 3.0 and higher, you could not select a revenue application selection created in 2.91 to use on a revenue smart field. | 338052 | BB747074 | 34 |
In Web UI, when you are working on the Edit Query screen, the program now looks up selections by ID rather than name. This way, if the name of a selection changes, the change is reflected in this screen. Previously, if the name of a selection changed and you used that selection on this screen, you received an object reference error when you tried to edit the query. | 331307 | BB746092 | 28 |
Index out of bounds error no longer occurs when editing a pledge amount in the ClickOnce version of Revenue Update Batch. | 297878 | BB742704 | 15 |
Letter and label template file names on the correspondence process form are now links that allow those files to be downloaded from the server. | 275836 | BB741162 | 13 |
List expenses are no longer duplicated on the Budget/Expenses tab of a marketing effort when two list segments from the same list are included in the marketing effort and you override list expenses after the first segment is added and again after the second segment is added. | 320211 | 24 | |
Lookup designation guid using integer ID when necessary. | 273746 | 13 | |
Manage adhocquery folder fix for restricted user. | 272005 | BB740656 | 9 |
Marketing effort exports no longer fail when using an export definition built from the consolidated query view. The consolidated query view is used only after an imported list segment is added to the consolidated list. | 340282 | 27 | |
Migrate BBIS email records during merge regardless of whether they already exist for target. | 275607 | 13 | |
Name format processing in exports places the addressee for an individual in the “Addressee” field, while the addressee for a household, group, or organization appears in the “Contact Addressee” field and the “Addressee” field contains the name of the household, group, or organization. To provide consistency, we added an additional field to the export called "Contact Addressee/Addressee” which provides the addressee results for all types of constituents. | 340225 | BB724220 | 34 |
New Feature: A new "Copy" option is available for export definitions in the webshell version of Blackbaud CRM. On the Export definitions page, click the double arrows beside the export definition to expand the row. From the action bar, click "Copy". After you confirm the selection, a copy of the export definition appears in the list. This change allows you to copy existing definitions so you can use them as templates for new definitions. Previously, you recreated definitions when you needed new versions of them. This enhancement reduces the number of steps to update existing definitions so you can work more efficiently. | 354243 | BB747806 | 37 |
New Feature: Blackbaud Internet Solution's Directory part now includes the End date field in the Primary Alumni and Education History nodes under Available Fields. This field, plus the Start date fields in the same sections on the part, always appear; they do not depend on the Academic Catalog in Blackbaud CRM. On a directory web page, each date field is limited to four numerical digits that require a 'yyyy' search. When you use the fields in the directory display window, the entire date, for example, 10/12/2015, appears. This change is related to the new features in work item 361208. | 367574 | 37 | |
New Feature: Blackbaud Internet Solutions now includes API endpoints that allow custom parts to use Blackbaud’s secure payment page. For example, a customization can pre-populate the Blackbaud secure payment page with biographical information entered on the custom part to improve data entry speed for donors. A customization can also store a donor’s credit card information. The new endpoints include: BBNCExtensions.Parts.CustomPartBBSPEditBase, BBNCExtensions.Parts.CustomPartBBSPDisplayBase, and BBNCExtensions.API.NetCommunity.Utility.SecurePayments. The BBNCExtensions.API.NetCommunity.Utility.SecurePayments endpoint also includes StoreCardInfo, CardNotPresent, TransactionResponse, and Redirect. For information about the new API, see the SDK/API online user guide. | 277594 | 28 | |
New Feature: In Blackbaud Internet Solutions, employment fields on the Directory part have been updated to match field names in Blackbaud CRM. The Position field has been renamed to the Job title field and the Profession field has been renamed to the Job category field under the Primary Business and Employment History nodes. In addition, the part has been improved to properly handle these fields when website users interact with them on your website. For example, users could previously use the Position and Profession fields to search employment history only. With this release, users can now use the Job title and Job category fields to search both primary (or current) employment and employment history. Also, the Industry field has been updated to search properly for both primary employment and employment history. | 361198 | 37 | |
New Feature: Irregular Installments for Membership Installment Plans. For memberships paid with installment plans, we have added the ability to set irregular installment schedules, similar to irregular pledge installment schedules. You can set up the membership installment plan with an irregular installment schedule when you add the membership. But you can also set up the membership with a regular installment schedule, such as monthly, and then change the schedule to irregular later, if needed. This functionality gives you the flexibility to accommodate members in the case where a member may request to make a smaller payment one month. To make an existing membership installment schedule irregular, from the constituent's membership record, click Change installment plan schedule. Or from the membership revenue transaction record, click Edit membership installment plan under Tasks or click Reschedule installments on the Installments/Write-off Activity tab. You can then select a frequency of "Irregular" and change the dates and amounts of the remaining installments. To add a membership with an irregular installment schedule, select a frequency of "Irregular" and enter the dates and amounts of the installments. | 274043 | 13 | |
New Feature: Membership installments can now be included in the generate direct debit files process, the credit card processing process, and the generate payments process. Previously, these processes could include only pledges and recurring gifts. Now when you run these processes set up for membership installments, any memberships with outstanding installments which meet the criteria are included in a new membership dues batch. When you run a generate payments process for membership installments, the only batch templates available are membership dues batch templates which include the required fields: Receipt amount, Account, Reference number, Reference date, Authorization code, Name on card, Card number, Card type, and Expires on. | 323363 | 24 | |
New Feature: Previously, when you included encrypted fields, such as Account number, in an export, the fields appeared blank. Now, when you include these fields, the data appears on your export unencrypted. | 330560 | 24 | |
New Feature: Previously, when you ran a mail merge, constituent addresses could sometimes include additional spacing between lines. When you create a mail merge outside of Blackbaud CRM, you might find that address lines have these additional spaces. If this happens, you can change the line break settings so they work best with the mail merge tool you are using. To do this, from the business process you are using, click Set format options under Tasks. On this screen, navigate to the Export tab. On the Line break characters field, select either CR, LF, or CR + LF. The correct option for your needs depends on the details of your mail merge, so if you experience issues with line spacing, select a different option than the one that was selected before and run your mail merge again. Note that these options affect the business process instance only, so if you have multiple business processes or multiple instances of the same business process, you need to adjust these options for each instance. | 390886 | BB749251 | 53 |
New Feature: The European banking industry, with the joint support of the European Commission and the European Central Bank, has implemented the Single Euro Payment Area (SEPA) to help streamline cross-border euro payments between SEPA countries. You must follow the SEPA standards if your organization has a bank account in the euro area which accepts direct debit transactions from constituents with other euro-area bank accounts. With this release, Blackbaud CRM provides the tools you need to process SEPA banking system transactions, including the ability to track information about SEPA mandates for constituents as well as a new direct debit transmission file format for SEPA banks. | 321554 | 24 | |
New Feature: The R68 online submission file includes the postal code and first line of the address for constituents with UK addresses. International addresses include the full address as a single line, but are truncated after 40 characters. This information can be used to help identify any missing, incomplete, or incorrect addresses before the files are submitted to HMRC. | 291782 | 15 | |
New Feature: The R68 process generates tax claim refunds under certain scenarios. Previously, the system would generate refunds whenever there was a change to the original revenue, even though refunds and re-claims were not always necessary. Now, when the revenue application is changed but the site, declaration, charity claim reference number (CCRN) and payment amount are the same as previously claimed, the Tax Claim Number will be assigned to the new application(s) and a tax claim refund will not be generated. | 291784 | 15 | |
New Feature: The R68 Report and R68 Refund Report include the postal code and first line of the address for constituents with UK addresses. International addresses include the full address as a single line, but are truncated after 40 characters. This information can be used to help identify any missing, incomplete, or incorrect addresses before the files are submitted to HMRC. In addition, "User ID" on the Gift Aid Settings page and "Submitter" on the R68 process are now "HMRC User ID." We also added web.config settings for three HMRC gateway URLs (local test service, HMRC test gateway, and Live HMRC gateway) so that you can make changes to the URLs if needed. | 291783 | 15 | |
New Feature: This fix addresses an issue that would occur when merging organizations with the "Grantor" constituency. Previously, when attempting to merge organizations that gave grant awards, an error would occur and the merge would fail. Now, a Foundations merge task exists in the Constituent Merge Configuration which will allow grantors and their grant awards to be merged. The Foundations merge task will be enabled by default for all pre-existing merge configurations. | 382967 | BB749558 | 53 |
New Feature: To address performance issues with queries that include Gift Aid information, a new Gift Aid refresh process is available so the program can pre-calculate Gift Aid eligibility and tax claim information for the revenue in your database. The pre-calculated data from the process appears in the ad-hoc query screen in the existing fields under Revenue > Gift Aid and under Revenue > Application details > Gift Aid. To include Gift Aid values in a query that are not pre-calculated, use the new fields under Revenue > Gift Aid-Calculated and under Revenue > Application details > Gift Aid-Calculated. After you upgrade, to pre-calculate values in existing queries that include Gift Aid information, create an instance of this new process and run it. Note: We recommend you schedule the process to run daily during after-hours, such as overnight. | 413067 | 53 | |
New Feature: Tribute Search by Tributee Lookup ID. You can now search for a tribute using the tributee lookup ID. In the Tributee lookup ID field, enter the lookup ID of the constituent recognized by the tribute. You can enter the entire ID or only the beginning digits. For example, if you enter "1", all tribute lookup IDs that begin with the number 1 appear. Before you could search by constituent last name and constituent first name. This additional search option can help you quickly locate records. To access the Tribute Search screen, select Search for a tribute on the Tributes page in Constituents. | 267782 | 13 | |
New Feature: When a timeout occurs in Blackbaud Merchant Services or Blackbaud Payment Services, you can now enter the text to display to donors on your website. You enter the text on the Donation Form part's Language tab, under the Validation Messages category in the new Card processing timeout row. This change applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. Note: This message first appeared with the release of patch 26 to inform donors their transactions are still processing so they do not attempt to resubmit them multiple times. | 337571 | 34 | |
New Feature: When a website user navigates from the Blackbaud secure payment page to the Payment 2.0 page on your website, a new message now appears on the Payment 2.0 page when it is necessary to remind the user to click the Check out button. For example, this message displays when a user spends too long on the secure payment page and their session times out on your site. It also displays when the request to return to your site is handled by a different web server and the user's information no longer appears. This helps make sure each credit card payment has a corresponding donation transaction to process in the back office, which does not occur when the user neglects to click Check out. You can enter the text you want to display for the message on the Payment 2.0 part's Language tab, under the Payment category, in the new Processed payment pending order message row. This applies to Blackbaud Internet Solutions\Blackbaud CRM and Blackbaud NetCommunity\The Raiser's Edge. | 321819 | 34 | |
New Feature: When an event is part of a multi-level event hierarchy, you can view the event hierarchy from the individual events in the WebUI version of the program. From an event, click Event hierarchy on the right edge of the page. The Event hierarchy view appears. You can use this view to move quickly between events in the hierarchy. Previously, you could do this in the ClickOnce version of the program. | 335322 | BB741761 | 37 |
New Feature: When someone purchases a lifetime membership with installments on your website, the membership transaction is now downloaded into CRM with the credit card payment token information. This allows future membership installments to be included in the CRM generate payments process and credit card processing process. Previously, the website user could purchase the membership and make the first installment payment on the website, but then had to be contacted by back-office staff about making the additional membership installment payments. | 333218 | 28 | |
New Feature: When you add a Data Provider KPI part to a web dashboard, you can now filter KPIs by name using the new KPI instance name field. Previously, you only saw a list of 500 KPIs and could not select additional KPIs, so if you had more than 500 KPIs, you could not always see the one you were looking for. | 405788 | BB747913 | 53 |
New Feature: When you have custom dataform extensions on the Add a payment screen, it is possible that errors with information entered in the extensions may have resulted in the credit card being processed and charged without the revenue transaction being saved to the database. Now, if the transaction cannot be saved, the credit card is processed and the user receives an error message: “The credit card was charged but the revenue transaction was unable to be saved to the database. Credit card-related fields are now disabled to prevent duplicate charges. Please check the information in the other fields and make any necessary edits to try to save the transaction again.” If the user attempts to save the revenue transaction, but it still cannot be saved, then another error message appears: “The revenue transaction is still unable to be saved to the database. If the transaction cannot be saved, click Refund to cancel the transaction and refund the credit card charge.” At this point, the user can click Refund (instead of Cancel) on the Add a payment screen to refund the credit card charge. | 367948 | BB748597 | 37 |
New Feature: When you integrate the Payment 2.0 part with an Event Registration Form part to provide shopping cart functionality for registration tickets, Blackbaud Internet Solutions now identifies whether the event capacity has been met before allowing a website user to submit the transaction. When event capacity has been met, a message now appears to inform the user that the transaction cannot be submitted. Note: When a user attempts to submit a transaction for a higher number of tickets than available, the program rejects the transaction. For example, if the user attempts to submit the transaction for two tickets and only one is available, the message appears and the transaction cannot be submitted. You can customize the text to appear for the message on the Language tab for the Payment 2.0 part. Under the Validation Messages category, the new Event sold out message row appears. In the Text field, you can enter custom text to appear or you can use the 'There are not enough registrations available to complete this request' default message. | 422952 | BB752340 | 55 |
New Feature: When you search for a constituent by lookup ID in the quick find field in the navigation bar, you now see search results for records that match the lookup ID exactly. Previously, results included partial matches. For example, if you enter "123" as your search criteria, the search results now only include records with a lookup ID of "123," but do not include results for a record with a lookup ID of "1234." The search results do include records with a name that begins with or matches your search criteria. In the example above, the search results would include a record with a name of "123 Organization," for example. For more information, see the Service Pack New Features chapter in the CRM 3.0 New Features Guide. | 333136 | 37 | |
New Feature: When you use the Academic Catalog in Blackbaud CRM and create or edit a Directory part in Blackbaud Internet Solutions, an Education Fields section now appears on the part. In this section, select whether to include academic information from affiliated educational institutions only or both affiliated and unaffiliated institutions for the search and results filters. To improve search performance, include only affiliated institutions. Note: After you save the part, you cannot change your selection. In addition to this new section, new fields appear for you to use on the Directory part to support integration with the Academic Catalog in the new Primary Alumni Additional Information and Education History Additional Information nodes. These fields include College/School, Division, Department, Sub Department, and Degree type. These part enhancements also include the ability to use the existing Program and Degree fields under the Primary Alumni and Education History nodes to search and display this data for affiliated and unaffiliated institutions. | 361208 | 37 | |
New Feature: When you write a letter to a constituent, you can now edit the contents of the letter and save the updated version on the interaction. From the Write a letter form, in the new Edit letter section, you can download the letter, make edits, and upload your changes. When you complete and save this form, you now navigate to the Documentation tab on the constituent interaction. Previously, you navigated to the Interactions tab on the constituent's record. | 334447 | 28 | |
New Feature: With this release, you can now import financial account and financial institution information through Batch. New fields are available when you create financial imports using the Enhanced Revenue Batch. For financial accounts, the following fields are now available: Financial institution, Account number, Account type, and Account name. For financial institutions, the following fields are now available: Financial institution name, Banking system, Branch name, Routing, BIC, Sort code, and Bank code. Note that when working with financial information, you must use the routing field associated with your selected banking system. | 327783 | 24 | |
New Feature: You can now assign an owner to a letter that you send to a constituent. If your user account is tied to the constituent, the new Owner field defaults to you, but you can assign a different user as the owner of the letter if you need to. To write a letter to a constituent, from the constituent record click Write a letter under Tasks. | 334853 | 28 | |
New Feature: You can now edit roles for a committee from the Committee page. On the Members tab, click Edit roles to edit existing roles for the committee. Previously, you could only edit roles from the Constituent page for the committee. You can also now add roles from the Constituent page of a Committee. On the Members tab, click Add role. | 321786 | BB739894 | 24 |
New Feature: You can now specify the text to appear when a Blackbaud Internet Solutions website user's session times out on the direct debit screen of a transaction. You enter the text on the Payment 2.0 part's Language tab, under the Session category in the new Session timeout message row. Previously, a message did not appear and the program created blank batches for transactions with expired sessions. | 383323 | 53 | |
New stylable Routing Number and Account Number merge fields are available in Blackbaud NetCommunity and Blackbaud Internet Solutions when you configure confirmation screens for Payment 2.0 parts that accept direct debit transactions. Also, new style sheet classes are available for the fields when you use the program's Style sheet section to add part styles. The new fields enable website users in the United Kingdom to view the fields in a format that is compliant with the Bacs payment system. | 415186 | 49 | |
New user email opt-in setting in Blackbaud Internet Solutions is fixed so that, when unmarked, new users will not receive the opt-in email message. | 276566 | 15 | |
Non-administrative users in system roles with rights to all records no longer receive an error message when they select an appeal with a different site when editing or activating a marketing effort. | 384942 | 41 | |
Non-administrative users in system roles without permissions to the Fundraising Efforts \ Appeals \ Appeal Edit Form 2 no longer receive an error message when they select an appeal on the Activation tab of a new or existing marketing effort, or on the marketing effort's Edit activation criteria form. | 316958 | 24 | |
Non-constituents are not included in the possible matches returned by the Duplicate Resolution screen in batches where you add constituents or in the possible matches returned when you add constituents one at a time. | 283197 | 15 | |
On a constituent's Correspondence page, in the list of appeals, if the appeal was associated with a public media marketing effort, the "Go to mailing" action would not work. This has been fixed. | 316482 | BB743810 | 20 |
On a Friends Asking Friends participant website, the "Import More" option has been enabled so you can import additional contacts from the same source (for example, from Yahoo). Previously if you selected "Import More" after you just added contacts from Yahoo, the "Yahoo! is unable to process your request" error message appeared. | 304710 | BB743236 | 20 |
On the Constituent Interactions and the Group Interactions pages, you can now filter interactions by status when you are using WebUI to access the program. Previously, you could only do this when using ClickOnce to access the program. | 304291 | BB742099 | 20 |
On the Profile Update Form in Blackbaud Internet Solutions, you can now select whether to make constituent attribute fields editable. Previously, the Editable element was not available for constituent attributes that were restricted to allow only one per record. When the Editable element is set to "Yes" for a constituent attribute, web users can modify the attribute value on their profiles. | 349536 | BB747303 | 32 |
Only send test emails to test recipients and not those attached to the email's appeal. | 277095 | BB741164 | 13 |
Per changes in 303573 when two constituents are linked to two CMS accounts for Blackbaud Internet Solutions and you merge the two constituents to one in Blackbaud CRM, the oldest CMS account deletes from the database. This fix prevents a sign up request from generating for that deleted account when it is viewed by selecting the "Deleted" search filter on the User page in Blackbaud Internet Solutions. | 316892 | 24 | |
Performance improvements in Blackbaud Internet Solutions and Blackbaud NetCommunity when the program runs security checks for non-Supervisor users accessing functional areas, such as Image library. | 278023 | BB741127 | 15 |
Platform instrumentation search run event fix. | 268175 | 9 | |
Prevent BBIS membership transactions from inclusion in the pending transactions count when they have already been downloaded to a batch. | 273185 | 13 | |
Prevent donation transactions from failing to download to CRM by ensuring that donor ID is set when BBIS donation is for an existing application. | 268844 | BB735474 | 13 |
Prevent duplicate constituents from appearing in "Who else should be included on this membership?" section when renewing a membership. | 267616 | BB740319 | 13 |
Prevent Gift Aid revenue query from returning multiple rows when different users update the applications and add splits on revenue. | 281672 | BB741623 | 15 |
Prevent transaction download error when an existing address with a start date is marked inactive on the BBIS Profile Update Form. | 278162 | 13 | |
Prevent unchanged primary business information from showing as changed in BBIS Profile Update Batch. | 273183 | 13 | |
Prevent unsubscribing from from all appeal types in BBIS when a single appeal is unsubscribed from. | 273186 | 13 | |
Preventing the creation of unnecessary payment adjustments when editing pledge amount. | 272306 | 13 | |
Preventing the creation of unnecessary payment adjustments when pledge is adjusted. | 272372 | 13 | |
Previously an error occurred in a multicurrency environment when you attempted to delete a revenue transaction which used a spot rate to determine a British pounds sterling (GBP) amount for the transaction. If the revenue transaction had a Gift Aid claim and you attempted to delete the original payment, you received an error because the spot rate associated with the original payment could not be deleted. It was still needed in order to process the Gift Aid refund. Now when you delete the original payment, the spot rate information is still maintained in the database so a Gift Aid refund can be processed. | 337948 | BB746586 | 34 |
Previously in ClickOnce, when you used the ZIP code lookup feature in constituent batches, you sometimes got a timeout error. This happened when the State field was blank and only for certain ZIP codes. | 345407 | BB745354 | 34 |
Previously in WebUI, when you created an Organization Position Holder smart query and a position had previously changed holders, you did not see the updated constituent for that position. This fix corrects that problem, so that when you browse for a position you now see the most current position holder. | 331952 | 34 | |
Previously you received an error message when you attempted to merge a constituent that was a marketing vendor with services entered on their Services tab. Now you can merge these constituents without issue. | 319865 | BB744198 | 24 |
Previously, a change in the matching algorithm for the duplicate detection process caused Constituent Update Batches to perform slowly during committal. With this fix, we changed a stored procedure query to improve process performance during committal. | 390686 | BB738961 | 38 |
Previously, a constituent revenue application amount smart field would double count the application amount for revenue records with recognition for multiple household members. Now, the constituent revenue application amount smart field will properly sum up the revenue amounts, regardless of the number of household members being recognized. Please be aware, to best utilize this fix, customers should run the smart field process for the Constituent revenue application amount smart fields that process for household member revenue recognition. | 315949 | BB743338 | 20 |
Previously, columns with dates since the current date were not properly updated during refresh. For example, 'Years since' would not change when the current date changed. You must redeploy the Blackbaud Data Warehouse (BBDW) before changes take effect. | 346067 | BB747804 | 34 |
Previously, editing or committing an Enhanced Revenue Batch would truncate stock symbols to four characters. Committing a Revenue Update Batch would also truncate stock symbols to four characters. With this fix, stock symbols with more than four characters are no longer truncated. | 324047 | BB744611 | 24 |
Previously, errors displayed for the Giving Summary Update Batch and Model Scores and Ratings Update Batch during the commit process. This was due to an earlier bug fix that passed matching threshold values to a constituent search list. The two batches that do not use the thresholds were being passed values to the search lists, but had no mapping to a value. This fix creates those mappings so the errors no longer display. | 326393 | 24 | |
Previously, event registrant information did not always match up correctly with event price in the Blackbaud Data Warehouse. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 415105 | BB751787 | 53 |
Previously, for a group constituent, data on the Recognition Summary and Recognition History tabs displayed inconsistently. The Recognition Summary tab included gifts with revenue data between the fiscal year. The Recognition History tab, with the same criteria, exported based on the revenue date, but included gifts recognized outside the fiscal year. With this fix, data displayed on the Recognition History tab is based on the recognition effective date instead of the payment date. | 347255 | BB746794 | 37 |
Previously, for Blackbaud Internet Solutions, an error displayed when a gift sponsorship was made to an individual with a United Kingdom address. The error occurred because no counties were associated with the United Kingdom in BBIS. This fix prevents an error from displaying even when there are no counties associated with the address. | 322669 | BB744840 | 24 |
Previously, from a user’s Sponsorship Status page in Blackbaud Internet Solutions, a user had the ability to email a sponsored child even when the sponsored child was associated with a gift sponsorship. Now, only the recipient of the gift sponsorship has the ability to email the sponsored child. | 322674 | BB744454 | 24 |
Previously, from the "Possible duplicate matches" screen, constituent records (including contact information) associated with a Constituent Security Group displayed for users without rights to that Constituent Security Group. Now, only constituent records associated with the user’s Constituent Security Group display on the "Possible duplicate matches" screen. | 299177 | BB742787 | 24 |
Previously, if a constituent was both an alumnus and a student and you queried on their constituency, they did not appear on the results as a student. This happened for constituents who have an alumnus constituency because they graduated from one institution, but also have a student constituency because they are currently attending another institution. | 346806 | BB715273 | 34 |
Previously, if you edited a posted payment to add a benefit and then you changed the constituent for the payment, the benefit was removed. Now when you change the constituent, the benefit remains on the payment. | 349283 | BB747280 | 34 |
Previously, if you used advanced spouse name formats for a marketing effort, you had to run the Calculate segment counts process during activation to ensure data for the marketing exclusions report was generated. Now, you can disable the Calculate segment counts process during activation if you have already calculated counts at least once. | 374848 | BB748972 | 37 |
Previously, if you waived the gift fee on a payment that already had a pending amount/gift fee adjustment, the reversal and new gift fee GL entries would show on the GL Distribution tab, even though the new gift fee GL entries should not have been created since the gift fee was waived. Now if you waive a gift fee on a payment with a pending amount/gift fee adjustment, the new GL entries for the waived gift fee will not appear. Only the gift fee reversal GL entries appear. | 279972 | 15 | |
Previously, in a Revenue Update Batch, when editing a donation associated with a paid matching gift claim, an error displayed upon validation. With this fix, we updated batch metadata, stored procedures, and handlers so that the matching gift claim or payment is not updated when a payment exists. | 392254 | BB747843 | 41 |
Previously, in an Enhanced Revenue Batch, when a zero-dollar transaction associated with a campaign was added, the campaign did not appear on the transaction record. With this fix, the campaign appears. | 357431 | BB748142 | 37 |
Previously, in Blackbaud CRM, an error displayed when editing sponsorship opportunities. The error was due to lingering records in the "SalesOrders" table used by Blackbaud Internet Solutions. Expired sponsorship sales order records were not deleted when they were unlocked. With this fix, we made changes to the "Unlock online sponsorship opportunity transactions" global change to delete the lingering sales order records. Sponsorship opportunities can now be edited without error. | 382740 | BB749539 | 41 |
Previously, in Blackbaud Internet Solutions (BBIS), when transactions were committed through a batch, recognition credits did not update correctly on constituent records where the constituent was changed manually or through duplicate matching in the batch. This same behavior also existed for non-BBIS transactions through an Enhanced Revenue Batch. With this fix, recognition credits update correctly in all scenarios. | 360284 | BB748272 | 37 |
Previously, in Blackbaud Internet Solutions, recurring gifts created from sponsorships used the base currency of the default currency set instead of the currency chosen by the donor. With this fix, for recurring gifts created from sponsorships, the currency on the merchant account is used as the transaction currency and the currency on the associated account system is used as the base currency. It is important to note the following situation: When the currency on a merchant account is not included in the currency set for an account system, resulting transactions may include incorrect data. To ensure your transactions include correct data, you must properly configure currency sets. Proper configuration ensures that the currency on the merchant account is included in the account system that is referenced in BBIS sponsorship form parts. Note that in a future release, currency set validation between recurring gifts created from sponsorships and the merchant account will be implemented. | 328174 | 24 | |
Previously, in Blackbaud Internet Solutions, recurring gifts created from sponsorships used the base currency of the default currency set instead of the currency chosen by the donor. With this fix, for recurring gifts created from sponsorships, the currency on the merchant account is used as the transaction currency and the currency on the associated account system is used as the base currency. It is important to note the following situation: When the currency on a merchant account is not included in the currency set for an account system, resulting transactions may include incorrect data. To ensure your transactions include correct data, you must properly configure currency sets. Proper configuration ensures that the currency on the merchant account is included in the account system that is referenced in BBIS sponsorship form parts. Note that in a future release, currency set validation between recurring gifts created from sponsorships and the merchant account will be implemented. | 324674 | 22 | |
Previously, in Blackbaud Internet Solutions, when a sponsorship had not been fully added to the Payment 2.0 cart, the sponsorship continued to show in the Payment 2.0 summary part. This occurred even though the Payment 2.0 part was blank. With this fix, the sponsorship does not appear in the Payment 2.0 summary part. | 328510 | BB742501 | 34 |
Previously, in the Sponsorship query, "Expired" did not display as an option in the sponsorship’s Status field. With this fix, "Expired" is now available. | 338055 | BB746541 | 37 |
Previously, non-admin users experienced slow performance when opening and editing any enhanced revenue batch. With this fix, we implemented several backend changes to improve performance. | 319913 | BB744513 | 28 |
Previously, on the Add stewardship plan template screen, when you entered negative dates in the Days from start column, the program displayed an exception message when the plan template was imported into the Add Plans and Steps process. With this fix, the program accepts the negative dates and allows the Target date field to be set accordingly. | 326263 | BB745039 | 41 |
Previously, on the Payment tab of the "Reassign a sponsorship" screen, "Carry forward" fields did not appear. With this fix, the fields now appear. | 375275 | 37 | |
Previously, on the Transactions tab of a Sponsor page, the date under the Commitment column did not respect the computer's regional date format setting. Now, the date under the Commitment column displays according to the computer's regional date format setting. | 328376 | BB743621 | 28 |
Previously, payments added through an Enhanced Revenue Batch were accepted for recurring gifts with inactive designations. With this fix, the Enhanced Revenue Batch specification now includes a query to check that a recurring gift designation is active. When the designation is inactive, an error now displays (as it currently does with one-off payments and pledges) and the payment is no longer accepted. | 393032 | BB749216 | 41 |
Previously, pledge and recurring gift payments made through Batch were not honoring the system defaults for receipt preferences that users defined in Marketing and Communications Configuration. Now, pledge and recurring gift payments made through Batch honor those user-defined system defaults for receipt preferences. | 288446 | BB742268 | 24 |
Previously, Pledge subtype was not updating the GL Post Status correctly when gifts were entered using the Enhanced Revenue Batch. Now, the default post status is updated correctly when gifts are entered using the Enhanced Revenue Batch. | 320349 | BB744312 | 24 |
Previously, queries based on the Blackbaud Data Warehouse did not appear in ad-hoc query searches or in the Microsoft Excel add-in. To take advantage of this fix, you must reinstall the Microsoft Excel add-in. | 392683 | 53 | |
Previously, relationships could sometimes show incorrect end dates when the 'Set end dates for relationships between subsidiaries and intermediate/top parents when no longer valid' setting was enabled in your corporate relationship settings. If you have that setting enabled, you might notice that multiple relationships incorrectly show the same end date. This incorrect data can affect other areas of the program, such as matching gift claims and recognition credits. If you think you are affected by this issue, please contact Blackbaud Customer Support, who can provide steps for correcting your data. | 400300 | BB750340 | 53 |
Previously, reports based on ad-hoc queries could sometimes cause timeout errors to happen in other parts of the system while the report was running. This fix changes how reports are generated to prevent this issue. To take advantage of these performance gains you must regenerate the reports from the ad-hoc queries. | 349630 | BB746564 | 34 |
Previously, reports that included parameters were not displaying the parameters correctly in WebUI. Report parameters now display correctly in WebUI. | 350300 | BB736442 | 34 |
Previously, solicitor amounts for matching gift pledges were incorrectly calculated (at times) when matching gift claim conditions used the following fields: Max match per gift, Max match per year, and Max match total. With this fix, we changed the way solicitor amounts are calculated for matching gift pledges to ensure amounts display correctly. | 391184 | 53 | |
Previously, some constituents could show the wrong 'date from' information in their alumnus constituency if they had more than one education record. For those types of constituents, the calculation would use the earliest 'date from' available rather than using the earliest graduation date. This fix ensures that the calculation is based on the earliest graduation date for the constituent. | 289255 | BB742339 | 24 |
Previously, some customers received an error when they tried to submit data tune-up files to Blackbaud. If you receive this error, you can change your data tune-up settings. From Administration, click Data tune-up and then click Data tune-up settings under Configuration. We have added a new section to this screen where you can change your FTP configuration. Under Connection mode, click Passive and save. You can then submit the files to Blackbaud. | 378577 | BB725064 | 37 |
Previously, some of the error messages you received when submitting files for AddressFinder and EmailFinder were not clear enough to help you diagnose the problem. We have added more detail to some of these error messages to help you determine the cause of the error. | 354273 | 34 | |
Previously, Sponsorships with a partial balance were not getting translated properly from the Apply to Commitments form to the Application field in Batch. Now, the value is translated correctly and appears as an option in the Application field drop-down menu. | 320542 | BB744396 | 24 |
Previously, stewardship plan steps were incorrectly replicated when editing pending steps or adding completed steps with a frequency other than "Single Occurrence." With this fix, the plan steps replicate correctly. | 398697 | BB746988 | 53 |
Previously, the Adjustment post date on the Edit posted application details screen defaulted to the current date. It now defaults to the post date of the deposit, matching the functionality on the Edit posted payment screen. | 370485 | BB748759 | 37 |
Previously, the Affiliations summary section on the Affiliations tab of the Wealth and ratings page was slow to load and could sometimes time out. This fix addresses the issue so that the Affiliations summary section loads with the rest of the page. | 310217 | BB743428 | 24 |
Previously, the BBIS sponsorship opportunity search process was not respecting the Suppress duplicate rows option in the query definition used by the search part. With this fix, the Suppress duplicate rows option is respected and duplicates no longer display if pulled into the query. When query definitions include fields that display differing values for the same sponsorship opportunity, duplicates continue to display. Note that we changed the BBECQuery.vb class to set the Suppress duplicate rows option based on the underlying query definition. | 370506 | BB748761 | 53 |
Previously, the Communications tab on the Communications page of a constituent group sometimes timed out when trying to load. We have upgraded the Communications tab to the List Builder format, which improves performance and includes additional list features such as column selection and filtering. | 351351 | 53 | |
Previously, the Constituencies section on the Constituencies tab on Constituent pages was slow to load and could sometimes time out. This fix addresses the issue so that the Constituencies section loads with the rest of the page. | 323292 | BB745073 | 24 |
Previously, the constituent's age was not properly updating with their birthday every year in the data warehouse. You must redeploy the Blackbaud Data Warehouse (BBDW) before changes take effect. | 345664 | 34 | |
Previously, the Declarations button was not enabled when adding a new individual constituent using the Enhanced Revenue Batch. Now the button is enabled and the user can add a new tax claim declaration when processing UK gift aid. | 311268 | 20 | |
Previously, the Details tab on a prospect plan step page did not display localized dates. With this fix, dates are localized correctly. | 369221 | BB746309 | 37 |
Previously, the ETL process for the Blackbaud Data Warehouse could sometimes fail when the ETL maximum parallelism was set to 4. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 355106 | BB748028 | 37 |
Previously, the ETL refresh process failed when the package cost of a marketing effort was unusually large. We have increased the cost limit to avoid this error in the future. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 370811 | BB748776 | 37 |
Previously, the Letters field of an Enhanced Revenue batch was showing duplicate letters. If a letter was associated with multiple sites, it appeared in the drop-down menu for each of those sites. Now, users see the letter once, regardless of how many sites are on the letter. | 311776 | BB743454 | 24 |
Previously, the membership transaction counts in the OLAP cube were calculated incorrectly. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 358553 | 37 | |
Previously, the revenue receipt preference field was not available in the revenue query. Now, the receipt amount will be available in the revenue query. To make this fix, a column named RECEIPTTYPE was added to the V_QUERY_REVENUE view. | 316348 | BB743114 | 20 |
Previously, the segment refresh process sometimes returned an error when you were running an ad-hoc query as a scheduled job. This happened when the system settings and the user settings of the user creating the query did not match. This fix ensures that date filters for the query are converted correctly based on the culture the query was saved in instead of basing the date filters on the user's current culture settings. | 334251 | BB746307 | 34 |
Previously, the summary section on Educational institution pages was slow to load and could sometimes time out. This fix addresses the issue so that the summary section loads with the rest of the page. | 310991 | BB743544 | 24 |
Previously, user-defined data lists in WebUI sometimes showed duplicate information. This fix addresses the issue so that data only appears once for each data list. | 333258 | BB746243 | 28 |
Previously, user-defined data lists that included a field twice would show the same filter for the field, even when you selected different filters. For example, if you included a field twice, once with a 'less than or equal to' filter, and once with a 'greater than or equal to' filter, after you saved the data list and went back to it, both fields would have the first filter you used. | 304922 | BB743261 | 34 |
Previously, users who did not have rights to add or edit addresses, phone numbers, or emails, got an error when they tried to add or edit a relationship between an individual and an organization. This fix allows those users to enter relationships without security errors. | 328435 | BB744045 | 24 |
Previously, when a batch had a user message, users got an error when they tried to save the batch without navigating to the page with the message. You can now save the batch without errors, even if you do not first navigate to the page in the batch that contains the user message. | 333636 | BB746280 | 34 |
Previously, when a constituent was a member of multiple committees and you queried on their committee membership, the end date could be incorrect in the query results. If one of the committee memberships for the constituent had an end date and one did not, the query results showed the end date from the committee that had one. With this fix, if the constituent is still an active member in a committee, the query results show the end date as blank. | 347624 | BB747025 | 34 |
Previously, when a user edited a pledge that had a $0.00 payment, the $0.00 payment would automatically be unapplied from the pledge. Now, when editing a pledge with a $0.00 payment, the payment will remain applied to the pledge regardless of the change. | 316329 | BB742650 | 20 |
Previously, when a user reconciled a duplicate record in a sponsorship batch, the program did not remove the duplicate error message upon batch validation. With this change, the program now correctly saves the reconciled record and removes the duplicate error message during validation. | 320976 | BB744575 | 24 |
Previously, when a write-off was added to a pledge with a balance that included a decimal, and the option to 'Reduce recognition credits by write-off amount' was selected, the recognition credits would be left with a balance of the difference between the pledge balance and the next full dollar amount. For example, a write-off is added to a pledge with a balance of $19.97 and the option to 'Reduce recognition credits by write-off amount' is selected. The recognition credit will be left with a balance of $0.03 (the difference between $20.00 and $19.97). Now, when encountering the same scenario, the recognition credit is reduced by the full and correct amount. Existing data will have to be identified and fixed separately. Technical changes: the stored procedure USP_DATAFORMTEMPLATE_PRELOAD_ADD_PLEDGEWRITEOFF2's ORIGINALPLEDGEAMOUNT has been changed from a data type of 'decimal' to a data type of 'money'. | 310967 | BB743359 | 20 |
Previously, when adding a new pledge which is marked as anonymous and the payment towards that pledge is added in the ER batch then payment for that pledge is not getting marked as anonymous. This fix addresses this issue and now pledge payment will be marked as anonymous too. | 310686 | BB743023 | 24 |
Previously, when adding a sponsorship and selecting a sponsorship program, if the specified browser language used different currency delimiters, an error displayed. With this fix, we created a view form to display sponsorship program information in the correct format. We also updated the Sponsorship Add form and Sponsorship Batch Handler to use the new view form to surface information associated with the selected sponsorship program. | 395512 | BB750561 | 48 |
Previously, when an export definition used certain fields such as Birth date, running an export resulted in an error. | 337622 | 34 | |
Previously, when communication with the Blackbaud Payment Service was interrupted or failed during credit card processing, an error was displayed for affected credit card transactions in CRM. Now, the error message is more descriptive and indicates what action the user needs to take: "A communication error has occurred with the Blackbaud Payment Service. The authorization status of this credit card transaction is unknown. This transaction has been marked as a provisional rejection. Verify the authorization status of the transaction with the Blackbaud Payment Service to determine how to proceed." | 372432 | BB748876 | 37 |
Previously, when editing a pledge payment with solicitors, an error occurred if the payment had the same solicitor multiple times. The amount credited to the solicitor was not consolidated correctly. Now when you edit the payment, the adjustments to the solicitor amount are correct, whether revenue is applied to different designations or across multiple installments. | 281620 | BB741637 | 15 |
Previously, when editing a Sponsorship batch, the sponsorship amount changed back to the default value for the selected sponsorship program. With this fix, the amount does not change during the edit process. | 332011 | BB746187 | 28 |
Previously, when editing the designation amounts for a single installment on the Split designations form, it was possible to enter valid amounts that would result in the error "Percent cannot be less than 0," which would prevent the user from saving a valid selection. This fix addresses the rounding issues that caused the error. The user no longer receives an error message for valid entries. | 321908 | 24 | |
Previously, when loading an Enhanced Revenue Batch created in version 2.7 or prior, there were some cases when the designation did not load properly, prompting an error message. This issue occurred in batches created in version 2.7 or prior, which had been upgraded to version 2.94. Now, the designation loads and the batch opens correctly without an error message. | 302972 | BB742677 | 53 |
Previously, when saving information to the "Add a sponsorship" screen accessed from the Sponsor tab of a constituent record, the following error displayed: "A field was specified that does not exist in the form definition, CARRYFORWARDPASTDUE." With this fix, the error no longer displays upon save. This fix corrects an issue introduced in 375275 (SP 7). | 392788 | 41 | |
Previously, when searching for a constituent using Planned giver as the Constituency filter, the constituent would not appear in the search results, even though the associated planned gift had a matured status. Now, if a constituent has a planned gift with a matured status, it will appear in the constituent search results when you choose Planned giver as the search filter. | 301632 | BB730200 | 34 |
Previously, when selecting a constituent by their finder number in an Enhanced Revenue Batch the Constituent Window would not populate with their information. Now, selecting a constituent by their finder number will populate the Constituent Window. | 322133 | BB744862 | 24 |
Previously, when the constituent on a financial transaction was changed from A to B, the acknowledgee of any letters associated with the transaction remained as A. Now, if the letter's acknowledgee is A, it will be changed to B. However, if the letter has already been processed or acknowledged, the acknowledgee will only be changed if the "re-acknowledge revenue" setting is enabled. | 298337 | BB742528 | 20 |
Previously, when two separate instances of an Enhanced Revenue Batch were committed at the same time and one of the batches included a payment to a pledge, the commit process could deadlock. With this fix, the deadlock no longer occurs. | 322595 | BB742560 | 24 |
Previously, when users added payments to pledge commitments through Batch, the receipt amount was being incorrectly added as $0.00 when the Batch was committed. Now, the correct receipt amount displays on the payment record after the Batch has been committed. This issue affected clients on 3.0 only. For more information about which pledge payments may have been affected, see the linked Knowledgebase solution, BB744518. | 319903 | BB744518 | 24 |
Previously, when using a Constituent revenue application smart field for constituent revenue recognition with an application selection filter, no revenue application information is returned by the smart field process. Now, the selection filter will properly filter the correct revenue applications and return the correct revenue application information in the constituent revenue application smart field process. The USP_CONSTITUENTIDSMARTFIELD_REVENUESPLIT stored procedure was changed to filter based on the revenue split ID (instead of the recognition ID) when using a selection to filter. | 303802 | BB743034 | 20 |
Previously, when viewing payment application details for a gift associated with a donor challenge, an error displayed. With this fix, an error no longer displays. | 326935 | BB745622 | 34 |
Previously, when you accessed the Members tab in a constituent record in ClickOnce, the group members did not appear. | 373797 | BB748983 | 37 |
Previously, when you added a new email address for a constituent that was part of a household and chose to copy that email address to the household members, the email address was not identified as primary even if it was the only email address for the household members. | 373078 | BB747335 | 37 |
Previously, when you added a new phone number for a constituent that was part of a household and chose to copy that number to the household members, the phone number was not identified as primary even if it was the only phone number for the household members. | 364967 | BB748396 | 37 |
Previously, when you attempted to deploy the data mart after upgrading to version 3.0 of Blackbaud CRM, you received an error. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 367711 | 37 | |
Previously, when you changed the mail preferences for a constituent, sometimes the audit information for that change was incorrect. When a user edited existing mail preferences, the audit would incorrectly indicate that the user who made the last change was also the user who originally added the mail preference. The audit would also incorrectly indicate that the added date was the same as the last edit date. | 410858 | BB751503 | 53 |
Previously, when you committed a Constituent Update Batch, the Gender field was automatically reset to 'Unknown' when you committed the batch, even if there was a gender assigned to that constituent. This happened when you used lookup IDs to identify constituents in the batch and the batch did not include gender information. | 348651 | 37 | |
Previously, when you confirmed a constituent was a duplicate in the batch view of a Membership Dues Batch containing Blackbaud Internet Solutions membership transactions, the membership program was removed from the batch row for the constituent. Now when you confirm a constituent is a duplicate, the membership transaction row is maintained in the batch with the confirmed constituent you selected. You can now commit the batch and create the membership. | 421842 | BB750229 | 52 |
Previously, when you confirmed a constituent was a duplicate in the batch view of a Membership Dues Batch, the membership program was removed from the batch row for the constituent. | 391189 | BB750229 | 41 |
Previously, when you edited selections in a corporate structure, your selections for the parent organization did not automatically carry over to the child organization relationships. For example, if you checked or unchecked an organization that had sub-organizations in the corporate structure, the sub-organizations did not inherit the selection you made for the umbrella organization. With this fix, your selections for the parent organization are automatically applied to the dependent organizations. | 351371 | BB747479 | 37 |
Previously, when you edited the first field in certain grids, the field would default to the first entry in the drop-down menu, rather than defaulting to the entry that had been previously selected. This happened for the first field in a grid with a drop-down menu if the field was linked to a search screen. For example, it could happen in the Edit sites screen from the Security tab on a constituent record. This fix addresses the issue so that when you access the Edit screen, the first field in the grid defaults to the value that was last selected for that field, and not the first value on the drop-down list. | 327875 | BB745718 | 23 |
Previously, when you entered an end date on a prospect, the system would let you save the record, even when there was a response-pending opportunity. Now, when you enter an end date for a prospect with a response-pending opportunity, you cannot save the record. You receive an error message stating the constituent has a response-pending opportunity and therefore must remain a prospect. | 305292 | BB742630 | 34 |
Previously, when you exported ad-hoc query results to an XLSX file in the webshell version of Blackbaud CRM, attributes with "Yes/No" values exported as "No" when constituent records did not include the attributes. With this fix, the program exports blank values for those attributes. The change also modifies a subroutine in the Blackbaud AppFx web service. Previously, the method for Blackbaud.AppFx.Export, Blackbaud.AppFx.Export.XlsxDataWriter with the signature "Public Sub WriteFile(ByVal ms As IO.Stream, ByVal fields As IList(Of ListOutputMetaField), ByVal rows As IList(Of String()))" translated empty strings to "No" for Boolean fields. Now, they remain empty strings and appear as blank cells in Excel. | 369783 | BB748675 | 37 |
Previously, when you exported yes/no information from a query, the results all exported as 'No'. | 337647 | BB746530 | 34 |
Previously, when you imported a constituent's phone number, the phone number was incorrectly formatted according to the phone number's country. | 337994 | BB746609 | 37 |
Previously, when you loaded a custom report that contained extended characters (such as a dash), those characters were replaced with a question mark. Now, when you load a custom report, the system retains the extended characters. | 328593 | 24 | |
Previously, when you merged two constituents the resulting record could sometimes no longer identify the constituent as a primary member of a group. This happened when you merged a constituent who was a primary member of two different groups and included primary information data in the merge. After the merge, the resulting constituent was only the primary member of one group. | 392045 | 41 | |
Previously, when you ran a report based on an ad-hoc query, dates sometimes displayed incorrectly. When your report included variable dates such as birthdates, the report displayed the date unformatted. For example, if the report included a January 30th birthdate, the date would display as '00000130' instead of displaying correctly as '1/30.' | 345380 | BB746339 | 34 |
Previously, when you ran the "Unlock online sponsorship opportunity transactions" global change process, the number of records processed displayed incorrectly on the Recent Status tab of the global change process record. The number included both locked and unlocked sponsorship opportunities. With this fix, after the global change process runs, only the number of locked sponsorship opportunities displays in the total. | 324203 | BB745268 | 24 |
Previously, when you ran the Constituent Revenue Application smart field for a constituent's revenue recognition and used a selection to filter based on the revenue application, an error would occur. Now, the smart field will run with no errors regardless of the summarization options for the selection. | 333178 | BB744972 | 34 |
Previously, when you selected to edit a posted matching gift payment associated with a large amount of applications, the edit process timed out. With this fix, we implemented several backend changes to improve the edit processing time. | 338258 | BB746523 | 53 |
Previously, when you submitted a file to Blackbaud using EmailFinder through data tune-up, you sometimes received an error indicating that the file name was too long. This could occur depending on the length of the organization name, contact name, process parameters, or temporary file configuration. This fix allows longer file names to run without errors. If the process has already failed with this error, you must submit the file by clicking Start on Step 1: Create and submit file to Blackbaud. Clicking Resubmit file to Blackbaud will not correct the problem if the process already encountered this error. | 414974 | BB724718 | 53 |
Previously, when you transferred a sponsorship to a new opportunity and added a payment to that new sponsorship through an enhanced revenue batch, the Application field in the batch data entry row incorrectly displayed the older opportunity. This fix correctly displays the new opportunity in the Application field for the batch. | 325531 | BB745333 | 24 |
Previously, when you tried to deploy the data mart, you sometimes got an error. This happened when the deployment process compared version numbers incorrectly. | 351861 | 37 | |
Previously, when you tried to merge two constituents and the source constituent had an address that was included in an AddressFinder batch, you received an error and could not complete the merge. With this fix, if the batch is committed, the merge process will remove that row from the batch and delete the source constituent. If the batch is uncommitted, you will still receive an error message. As part of this fix, we have improved the wording on the message so that it is clear that you must commit the batch before the merge process can run. | 401242 | BB750870 | 53 |
Previously, when you tried to validate addresses in a Constituent Update Batch, you sometimes got an error. This surfaced when using the QAS validation service. | 347902 | BB747054 | 34 |
Previously, when you updated an existing email address on a Constituent Update Batch, you were able to mark the email address as not primary and commit the batch. This could result in a constituent having an email address on their record, but no primary email address. You now cannot do that if the email address is the only one on the constituent's record, because when a constituent has email addresses on their record, one must be identified as primary. | 357043 | BB748097 | 37 |
Previously, when you upgraded from 2.91 to any later version, the upgrade process mistakenly removed receipt stack short names from existing receipts. This issue is fixed and will not impact organizations that upgrade from 2.91 in the future. If you are installed on-site (not hosted), you must perform extra steps to enable this fix. Contact Support for more information. | 372389 | BB748798 | 37 |
Previously, when you uploaded an image, the program sometimes incorrectly rotated the image so that it appeared sideways. This corrects the issue. | 324879 | BB744759 | 24 |
Previously, when you used Page Designer in WebUI, you were not able to change Task Groups when using the product in a language other than English. To see your changes reflected in the product, when you change a task group you must also delete the task group resource key. | 350551 | BB747286 | 34 |
Previously, when you used the Educational institution name field as a filter in an ad-hoc query, the process of selecting an educational institution as a filter sometimes timed out if you had a large number of educational institutions in your database. This fix requires that you enter the educational institution you want to use as a filter instead of selecting it from a drop-down menu, which prevents it from timing out. Existing ad-hoc queries that include the Educational institution name filter will still return the same set of results as they did previously. However, if you edit an existing query that uses this filter and your database now has a large number of educational institutions, the process of editing the filter could time out. If this happens, delete the filter and re-insert it into the query. This applies to the Name field under the Educational Institution query node and the Educational institution name fields under the Primary Education and the Educational History query nodes. | 316578 | BB743852 | 24 |
Previously, when you viewed an event calendar in ClickOnce, you sometimes got an error indicating that the memory was corrupt. | 347653 | BB742984 | 34 |
Previously, you could not view marketing plan activities in the next year when viewing the planner calendar. To fix this issue, we added "Next year" as a date filter option for plan activities. | 401697 | BB750894 | 53 |
Previously, you received an error message in Enhanced Revenue Batch when the batch contained payments toward pledges and you attempted to save the batch. This issue occurred only in the ClickOnce version and is now resolved. | 338070 | BB746637 | 28 |
Previously, you received an error message in Revenue Update Batch when the batch contained payments toward any committment and you attempted to save the batch. This issue occurred only in the ClickOnce version and is now resolved. | 346884 | 28 | |
Previously, you sometimes got a timeout error when you accessed the Summary tab of a group constituent record. This happened when you were viewing a group with a large number of members. | 348709 | BB747192 | 30 |
Previously, you sometimes got an error when you entered an alternate lookup ID in a Constituent Update Batch. The error incorrectly indicated that the alternate lookup ID was not unique. | 352475 | BB747663 | 37 |
Previously, you sometimes got false positive results during the Blackbaud Data Warehouse validation process. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 380091 | 37 | |
Previously, you sometimes received an error when you used a data list that was created from an ad-hoc query against the Blackbaud Data Warehouse. The error occurred when you created a data list that used a filter. | 340092 | 34 | |
Previously, you sometimes received an error when you used a data list that was created from an ad-hoc query against the Blackbaud Data Warehouse. You must redeploy the Blackbaud Data Warehouse (BBDW) before changes take effect. | 336655 | 34 | |
Previously, you were sometimes unable to upload a picture to a constituent record. The 'Choose file' option did not work if you were using Firefox in WebUI. | 338217 | BB746648 | 34 |
Prior to this change, Stewardship plan recurring steps were not successfully created after marking the current step complete. Now, when you mark a recurring step complete, the next pending step is created automatically. | 317703 | BB744237 | 24 |
Prior to this change, the Revenue History Report would display an incorrect date/time that a gift was entered because the REVENUEPOSTED table’s DATEADDED was interpreted as the FINANCIALTRANSACTION’s DATEADDED. | 310950 | BB741341 | 20 |
Prior to this fix, membership installment plan transactions were not appearing in the FACT_REVENUE view in the Data Warehouse. With this fix, the FACT_REVENUE view includes membership installment plan transactions. | 321947 | 24 | |
Prior to this fix, when processing tribute acknowledgements that use an export definition with address processing fields selected under the Revenue \ Constituent node, few or no records would appear in the output. Now, the tribute acknowledgements process correctly. | 324765 | BB745096 | 24 |
Problems using finder numbers belonging to imported list segments with long names have been addressed. Existing list segments whose names are not unique within the first 43 characters should now work correctly when used in marketing efforts going forward. | 268974 | BB726990 | 13 |
Prompt to update gift fees on payments when they are edited and benefits now change the receipt and gift fee amounts. | 280151 | 15 | |
Recalculate gift fee when total payment amount is changed in Revenue Update Batch. | 276376 | 15 | |
Recognition credits were incorrectly created when you made adjustments to posted revenue transactions. The new recognition credits were created for the adjusted revenue applications, but the historical recognition credits also remained on the revenue transactions. Now the historical recognition credits are removed and only the ones for the adjusted revenue applications appear. Any incorrect recognition credits which resulted from this issue, which impacted version 2.93 and higher, will be deleted and will no longer appear on the posted revenue transactions. | 333160 | BB744380 | 28 |
Recognition credits will now generate for additional applications in an Enhanced Revenue Batch after changing the designation on an additional application. | 311163 | BB741699 | 20 |
Registering the batch dialog modal to invoke a prompt when a user closes an open batch. | 304286 | BB742395 | 18 |
Remove revisions that are not necessary to prevent time outs and reduce the time to run revisions. This applies to Blackbaud Friends Asking Friends, Blackbaud Internet Solutions, and Blackbaud NetCommunity. | 281429 | BB741867 | 15 |
Remove routing number validation from transaction manager so it is handled by the CRM Financial Institution validation, allowing international customizations to work. | 272551 | BB738940 | 13 |
Remove unnecessary time information from BBIS event registration start and end dates. | 278547 | 13 | |
Remove whitespace characters that break javascript from business process error messages | 274835 | 13 | |
Removed restriction ensuring the transaction amount agreed with the number of stock units multiplied by the median stock price. | 269300 | BB740038 | 13 |
Removing invalid constraint on funding types that would only allow one type across all plans or opportunities. | 294751 | BB742559 | 20 |
Removing timestamp process for ClickOnce application to stop Windows XP crashes. | 282631 | BB739420 | 14 |
Resolve an issue where USP_LOADSPEC would crash when page alterations include adding new actions into an existing, but empty, action group. | 277742 | BB741594 | 14 |
Resolve issue with multiple designations on donation form. | 273180 | BB741047 | 6 |
Resolved date format issues so that dd/mm formats are respected in BBIS Profile Update batches. | 272134 | BB740867 | 13 |
Resolved issue when trying to search on the campaign search dialog. | 274952 | 13 | |
Restored missing ignore button from duplicate resolution screen in ClickOnce batches. | 279677 | BB741644 | 13 |
Revenue application selections were not available in revenue queries. The Selections folder under the Application Details query node was missing. | 346834 | BB746938 | 34 |
Revenue update batch should load faster in certain situations within the click-once application. | 277729 | 20 | |
SAR data now caches correctly when smart field value group fields are used for marketing acknowledgements with multiple transactions per donor. | 292175 | BB742181 | 15 |
Save address captions for the Primary Address Block under Contact Information for the BBIS Profile Update Form. | 273182 | BB739797 | 13 |
Show all fields that are available on the Organization Record Add Form. | 276675 | BB741165 | 13 |
Site filtering not working correctly on the Recognition Summary and history tab for the constituent (Individual, Organization and Group) | 317254 | BB743690 | 24 |
Smart field feature access security fix in query. | 281666 | BB734941 | 14 |
Sold stock gifts were not being included on the Appeal Performance report. This has been fixed. | 311517 | 20 | |
Sponsorship payments from BBIS should show the proper system receipt type. | 274833 | BB741232 | 13 |
Support entering multiple address lines in batch. | 276610 | BB741490 | 14 |
Technical Change: In CRM 3.0, the USP_REVENUE_UPDATEPAYMENTDETAILS stored procedure inadvertently removed the 'BBPS Transaction ID' when a credit card transaction was edited in CRM. The 'BBPS Transaction ID' is used to identify a credit card transaction in the Blackbaud Payment Service and your payment processor, such as Blackbaud Merchant Services or IATS. As a result, the 'Refund card on save' option no longer appeared on the Edit payment or Edit posted payment screens for the transaction, and the transaction no longer appeared as reconciled on the 'Reconcile transactions and disbursements' page in Treasury. However, you could still refund the transaction directly through your payment processor and manually reconcile the transaction from Treasury. To resolve this issue, the stored procedure has been updated with additional parameters which should be set when the 'BBPS Transaction ID' for a credit card payment is edited. Any code that references this stored procedure but does not update the 'BBPS Transaction ID' can ignore the new parameters. | 320341 | 24 | |
Technical change: Direct debit payments can no longer be selected for one-time payment transactions in Blackbaud Internet Solutions. This prevents a reconciliation conflict that occurred between recording the gift in Blackbaud CRM and actually receiving payment for the direct debit transaction. This change impacts multiple areas in Blackbaud Internet Solutions. When you configure the Donation Form part and select the Allow one-time gifts checkbox, a message prompts you to select credit card as the payment option. On the donation web page, when a website user selects the One-time gift option, the direct debit payment option no longer appears on the page so the user cannot select it. When the gift is recurring and the website user selects today's date as the start date for the first payment, the gift is processed according to the recurring gift schedule and the EFT workflow process, instead of immediately being sent to Blackbaud CRM. Also, when a website user includes a one-time item in the shopping cart on a Payment 2.0 part, the direct debit payment option does not appear in the Payment Type field on the web page. When you configure a Donation Form part to integrate with a Payment 2.0 part, avoid selecting direct debit as the only payment option for one-time gifts. Otherwise, a message appears to inform users they cannot submit one-time payments. You can enter the text you want to display for the message on the Payment 2.0 part's Language tab, under the Payment category, in the new Direct debit for one-time gift(s) message row. As of Blackbaud CRM 3.0, patch 27, the web.config file for Blackbaud Internet Solutions includes the new appSetting "AllowDirectDebitForOneTimeGifts" so you can allow direct debits for one-time gift custom processes. By default, the program continues to prevent direct debits for one-time gifts. This setting should only be used for your organization’s custom processes that allow direct debits for one-time gifts. | 310918 | 24 | |
Technical Change: Previously, if an individual had a primary business, you could use Constituent Update Batch to edit the business’s contact information. If the business already had duplicate contact information, an error message prevented you from committing the batch. Now, if the individual's primary business is an existing organization, you cannot edit its contact information in the Constituent Update Batch. This fix makes the Constituent Update Batch handle an individual’s primary businesses the same way that the Constituent Batch does. To update the contact information for an existing business, update the organization’s record instead of the individual’s record. | 297599 | BB741817 | 15 |
Technical Change: Previously, the GL Accounts list on the Define GL Accounts page for a general ledger account system sometimes timed out when trying to load. We have upgraded the GL Accounts list to the List Builder format in WebUI, which improves performance, increases the data row limit, and includes additional list features such as column selection and filtering. If you have custom actions on this section, you must recreate those customizations for them to appear in WebUI. In addition, system roles that grant access to this data list will now also grant access to the GL Account Query used by the List Builder version of the page. | 426152 | BB752297 | 53 |
Technical Change: Previously, the program incorrectly allowed you to assign the same role to a group member with overlapping dates. With this fix, you can now no longer assign the same role to the same group member with dates that overlap. When you apply this fix, any identical roles with overlapping dates will be combined. The resulting role will use the earliest start date and the latest end date. If you do not want those roles to be combined, before you apply the update, change the start and end date for the roles so they do not overlap. | 398107 | BB727712 | 53 |
Technical change: This change optimizes how the database loads the email_recipient and emailjob_recipient tables during peak email activity to help avoid timeouts and failures. The optimization maximizes the availability of these tables for other processes. The following stored procedures include updates related this improvement: UFN_PROCESSCMSEMAIL_LOOKAHEAD, USP_EMAILJOB_ADDCONDITIONALCONTENTRECIPIENTS, and USP_EMALJOB_GETPREPAREDJOB. Also, the Email_Recipients.EmailRecipient_EmailID_OptOut_InvalidAddress table index was replaced with the Email_Recipients.IX_Email_Recipient_EmailID_OptOut_InvalidAddress_InvalidAccount table index. Note: Table sizes still affect the time it takes to process transactions and can continue to cause timeouts. If you continue to experience problems, configure the length of time to allow before a timeout occurs in the web.config file. | 357049 | 53 | |
Technical Change: This fix addresses a performance issue when you view the Revenue History for a revenue transaction. To improve performance, we copied the audit data from the historical RevenueAudit, RevenueSplitAudit, RevenueBenefitAudit, and RevenueGLDistributionAudit tables into the corresponding audit tables for the Financial Transaction Model: FinancialTransactionAudit, RevenueSplit_ExtAudit, RevenueBenefit_ExtAudit, FinancialTransactionLineItemAudit, Revenue_ExtAudit, JournalEntryAudit, and JournalEntry_ExtAudit. If you have a customization which queries the historical revenue audit tables, as well as the Financial Transaction Model ones, to get a comprehensive picture of the audit history, you will see duplicated audit data for revenue entered into the system prior to version 2.92. | 330451 | BB743149 | 28 |
Technical change: To optimize performance when you update your secure payment pages with the latest style sheet, layout, template, and page changes you make, the interval the program uses to push the updates to Blackbaud's secure payment server has increased from within the next 5 minutes to within 1 hour. When you make a content change that cannot wait up to an hour to appear on your secure payment pages, you can continue to manually update these pages by clicking the Update templates button in Administration, Sites & settings in Blackbaud Internet Solutions and Blackbaud NetCommunity. | 328388 | 21 | |
Technical Change: When you use API endpoints for custom parts with Blackbaud's secure payment page, the API no longer clears the part's content when the {content} placeholder does not exist on the page. To avoid exceptions when sending template updates for the secure page, you must update your custom code to handle clearing the custom part. This change applies to Blackbaud Internet Solutions. Note: See work item 412173 patch note for an update to this fix. | 409826 | BB741522 | 53 |
The "Could not download transaction with ID..." message no longer appears when downloading a Blackbaud Internet Solutions donation transaction that is on behalf of a company. | 285160 | BB742145 | 15 |
The "Could not download transaction with ID..." message no longer appears when downloading a Blackbaud Internet Solutions profile transaction for a constituent with an address that does not include a state. | 289921 | BB742352 | 15 |
The "Export marketing effort" form will no longer take a long time to load for clients with a large number of packages in their database. | 317842 | BB744253 | 24 |
The "Index was out of range" message no longer appears when printing an eCard for a gift sponsorship on a web page with a Sponsorship Form part in Blackbaud Internet Solutions. | 284829 | BB741776 | 15 |
The "Show inactive" filter has been restored to the Seed, Source Code and White Mail Segment data lists in the smart client. | 324713 | BB745341 | 28 |
The acknowledgement rules data list would not load if users set the browser locale to Finnish. With this fix, the acknowledgement rules data list now loads properly. | 418117 | BB751947 | 50 |
The Appeal, Source code, Effort, and Channel fields in an Enhanced Revenue Batch were editable on a row, even after providing a finder number. Users should not be able to edit those fields when a finder number is provided. With this fix, those fields remain grayed out and are not editable when a finder number is provided. | 319194 | BB744389 | 24 |
The Blackbaud Direct Marketing ETL data mart for The Raiser's Edge is now compatible with SQL 2012 server. To utilize SQL 2012 server: 1) install the patch, 2) install SQL Native Client 2008 R2 located at www.microsoft.com/en-us/download/details.aspx?id=16978, 3) Redeploy the data mart. | 372884 | BB748920 | 41 |
The Communications tab in Blackbaud CRM now displays links to external websites that a user clicks from a Blackbaud Internet Solutions email. Previously, this tab only displayed links to internal pages on your website from a Blackbaud Internet Solutions email. | 302130 | BB742727 | 20 |
The Constituent Lifetime Giving smart field no longer excludes planned gift payments. After you run the update and process this smart field, its value will include all revenue given prior to the process date. However, the smart field includes only future planned gift revenue; it does not include planned gift payments that occurred before the last run date. To include planned gift payments made prior to the last run date, you will need to create a new Constituent Lifetime Giving smart field. | 400431 | BB750799 | 53 |
The Constituent Profile Report will now format date and currency values correctly according to a user's language settings. | 291296 | BB742455 | 15 |
The Constituent recognition process now prevents multiple recognition levels from being awarded to a constituent in a single run of the process when only the highest level for the qualified revenue should be awarded. | 271128 | BB740137 | 24 |
The Create multiple segments screen was redesigned to fix performance issues that occurred in databases with large numbers of selections. Previously, the screen loaded all available selections for the source and then you chose which selections to add to the set. Now, the screen includes a grid that allows you to browse to or enter the name of the selections you want to add to the set. | 311647 | BB743686 | 24 |
The date fields for Changed from and System value in a BBIS Profile Update Transaction Batch in Blackbaud CRM now disable when a website user modifies a constituent attribute on a Profile Update form on a Blackbaud Internet Solutions website. The fields previously enabled for constituent attributes only. | 352244 | 34 | |
The donation transaction download process for Blackbaud Internet Solutions now correctly downloads the ID of the Blackbaud Payment Services transaction for single donations and first recurring gift payments to the Enhanced Revenue Batch. This allows you to use the "Refund card on save" checkbox on the Edit a payment screen for these gifts to properly refund payments in Blackbaud CRM. | 317086 | BB744020 | 19 |
The Email Subscribers page in Blackbaud Internet Solutions now displays an email address for a user when it is not assigned to a Blackbaud CRM site. This change only applies when the "Enable CRM security for linked CMS users" checkbox is selected in Blackbaud Internet Solutions Sites & settings. | 302115 | BB742817 | 20 |
The function document.querySelectorAll is now used to successfully upload documents in Files when you use IE8. Previously, the program used getElementsByClassName which is not supported by IE8 and below. This fix applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 319593 | BB744448 | 24 |
The group members list now allows searching by member name and sorting by first or last name. | 290847 | BB727143 | 20 |
The Mailings tab for an email appeal record in Blackbaud CRM now correctly calculates the total value of the appeal from your Blackbaud Internet Solutions website. To correct this issue, the stored procedure USP_DATALIST_APPEALBBISEMAIL has been modified to correctly calculate the total for complete transactions. | 352655 | 37 | |
The Merge button found on the Acknowledgements page (for revenue and tribute acknowledgements) and on the Reminders page is no longer disabled. | 317487 | BB744197 | 24 |
The message "The record specified does not exist for this data form" no longer appears in a Blackbaud CRM batch when you process a profile update from Blackbaud Internet Solutions with address updates. This message appeared when the address had been deleted on the constituent record before the batch was committed and the program attempted to compare the updated address with an address that no longer existed. This scenario is now handled by text in the batch to inform you an address does not exist for comparison and it also includes how to add the address as new. The text reads, "There is not an existing address to update. It may have been deleted on the constituent record after the initial review of this batch. To add this address as new, click Review transaction details on the Details toolbar. On the Review transaction data screen, select the address row and click View details. On the Review address data screen, select Create new address." | 372758 | 37 | |
The new "Data Admin" system privilege gives users rights to see all query results. When a user with data admin rights runs a query, the query process bypasses the check for the user's access to the records returned by the query. Previously, the process only bypassed this check for users with administrator rights. When a user with data admin rights runs a query, the system still checks for the user�s rights to individual records before the user is able to drill into any records in the query results. | 305478 | BB741313 | 24 |
The Pledge date and Last payment date fields in the pledge reminder output format "Formatted mail pledge reminder output - extended" and the Pledge date field in the pledge reminder output format "Email reminder output" now display dates in the correct format. | 319657 | BB744473 | 24 |
The Profile Update form in Blackbaud Internet Solutions now accepts fuzzy date entries (for example, mm/yyyy) for the Birth date field. Previously, the form only accepted full date formats (for example, mm/dd/yyyy) which prevented a website user from successfully submitting a profile transaction on your website. To resolve this, the DataForm types have been updated from Date to Fuzzy Date for the Profile Transaction Data Form. | 398181 | 53 | |
The Profile Update form in Blackbaud Internet Solutions now accepts fuzzy date entries (for example, mm/yyyy) for the Date to, Date from, and Graduation dates for "Educational histories" and "Educational involvements" fields when you use them on the constituent record in Blackbaud CRM. Previously, the Profile Update form only accepted full date formats (for example, mm/dd/yyyy) which prevented a website user from successfully submitting a profile transaction on your website. To resolve this, the DataForm types have been updated from Date to Fuzzy Date for the Profile Transaction Data Form. | 388850 | 53 | |
The program no longer times out when you delete a package from the packages list on the Packages page. | 386012 | BB749795 | 41 |
The RE7 Gift Amount smart field process no longer fails when it includes a constituent who gave a gift and received a soft credit on the same day. | 327812 | BB745707 | 37 |
The RE7_CONFIGINFO SSIS package was updated to set the proper data type for the Fiscal Year End Month variable. Redeploy and refresh The Raiser's Edge data mart to include this change. | 316546 | 20 | |
The receipting process will now properly handle the generation of consolidated receipts where both new and re-receipted transactions for the same constituent were included in the input. Re-receipted transactions will be output separately from new transactions, broken out by their previous receipt number. | 302070 | BB742970 | 24 |
The Salvation Army: In Blackbaud Friends Asking Friends, offline pending gifts now correctly adhere to the merchant account and designation selected on the Event Details tab when you configure a FAF event and select Enable designation by geography for the merchant account. Previously with this option selected, the gift erroneously credited to the designation for the FAF participant user's local corporation selected in their profile when the user skipped a prompt for the gift to credit the designation for the merchant account's local corporation. Now when the prompt is skipped, the designation selected for the FAF event is correctly credited for the gift. | 285674 | BB742184 | 24 |
The smart fields "Constituent Single Gift Consecutive Year Donors", "Constituent Lifetime Gifts On File" and "Constituent Years On File" were found to perform poorly when run for small numbers of constituents after being run for large numbers of constituents. This was due to SQL Server's caching an execution plan which, while efficient for large number of records, is not efficient for small numbers of records. These smart fields have been changed to disregard cached execution plans. | 316261 | BB724797 | 20 |
The User Login part now displays new user data on the New User Registration Email for all merge fields. This applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 299564 | 15 | |
The User Login part now displays the new user's first name on the New User Registration Email for the First Name merge field. This applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 290559 | BB742414 | 15 |
The validation for an empty cart has been removed to avoid an alert message when a website user clicks "Empty Cart" on the Payment 2.0 part. The validation is not necessary since the cart is empty, but it occurred for required fields on the part. To remove the validation, the CausesValidation property on the "Empty Cart" link has been set to false. This applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 310956 | BB739118 | 20 |
The webshell version of Blackbaud CRM now processes merge rules such as "If, Then, Else" statements in Word documents when you merge data from the program. The change allows you to include any of the rules available in Word except “Ask” and “Fill-in” because they require users to manually input data. Previously, you could only use the smart client version of the program to process these rules. | 285453 | BB742176 | 41 |
This change affects grant award payments added through an Enhanced Revenue Batch. Previously, when the GL Account included a Designation segment, an invalid error displayed during the batch validation process. This error displayed even when a valid account mapping existed. With this fix, the error no longer displays. | 320105 | BB744547 | 24 |
This change affects the ClickOnce version of the product and applies to an Enhanced Revenue Batch with the following configuration: The Revenue category field contains a default value and is required, and records are entered using the Finder number field. Previously, during batch validation, the value in the Revenue category field was removed and an error displayed stating that a revenue category was required. With this fix, the value in the Revenue category field is not removed during validation and no error message displays. | 333300 | BB745371 | 41 |
This change affects the ClickOnce version of the product. When using a Constituent Update batch to update a constituent with a high percentage of duplicate fields, an exception now correctly occurs to allow the user to either add the constituent as a new record or confirm that it is a duplicate. | 306830 | BB743374 | 20 |
This change affects the ClickOnce version of the product. When using an Enhanced Revenue batch to update a constituent with a high percentage of duplicate fields, an exception now correctly occurs to allow the user to either add the constituent as a new record or confirm that it is a duplicate. | 351367 | BB747090 | 34 |
This change affects the Webshell version of Blackbaud CRM. Previously, when you added a tribute associated with a zero amount through an Enhanced Revenue Batch, an error occurred. With this fix, you can successfully add the tribute. | 348892 | BB747375 | 37 |
This change affects the Webshell version of the product. Previously, from Administration, when a user attempted to expand an academic catalog associated with more than one thousand entries, an error displayed after a period of time. With this fix, an error no longer displays. | 310507 | BB743485 | 28 |
This change applies to a constituent record associated with a matching gift relationship in an Enhanced Revenue Batch. Previously, when the constituent was added to the batch and saved, the following error displayed upon validation - "one or more designation amounts is invalid." With this fix, the error no longer displays upon validation. | 372946 | BB748811 | 37 |
This change applies to a Constituent Update Batch in Blackbaud CRM. Previously, when a user searched for and selected a constituent record using the Lookup ID field, upon committal, the Gender field reset from either "Male" or "Female" to "Unknown." With this fix, the value in the Gender field does not incorrectly change upon committal. | 334622 | BB746363 | 34 |
This change applies to a constituent whose Former Address record includes an end date and is marked as Do not send mail to this address. Previously, when using an import to create a Constituent Address Update Batch (to change the address to primary), the address displayed in the batch without the primary flag, but still contained the end date and Do not send mail to this address selection. Upon committal, the address was not updated. With this fix, the address updates to primary, but the end date and Do not send mail to this address selection remain. An error now correctly displays upon committal. At this point, we encourage users to determine whether the existing address or imported address is correct, remove the incorrect information, and commit. | 379454 | 53 | |
This change applies to a non-administrative user in Blackbaud CRM where an Enhanced Revenue Batch has been created. In the batch, when a duplicate constituent record is detected and the user selects to resolve the duplicate by updating the record, an error appears and indicates that the user does not have rights to perform the action. Upon committal, no information is saved to the record. With this fix, the security check that happens when changing context to the matched constituent after resolution is handled correctly and the error no longer appears. | 353127 | BB747729 | 34 |
This change applies to a Revenue Update Batch. Previously, when payment method details were edited for posted pledges through a batch, the batch committed, but the payment method details did not update. With this fix, payment method details update correctly upon committal. | 398006 | BB750624 | 53 |
This change applies to a Revenue Update Batch. Previously, when searching from the "Revenue Update Batch Search" screen, an error displayed because the system role with permission to access the screen was not associated with the "Revenue Update Batch Get Revenue" permission. With this fix, the error no longer displays. | 387668 | 53 | |
This change applies to a Sponsor Batch. Previously, when the Sponsorship program field was hidden on the batch template and the payment method was direct debit, the following error occurred during validation: Cannot insert the value NULL into column SPONSORSHIPOPPORTUNITYTYPECODE, table dbo.BATCHSPONSORSHIP, column does not allow nulls. UPDATE fails. With this fix, the Sponsor Batch handler was modified to handle hidden fields on the batch template. The error no longer occurs. | 375752 | BB738424 | 53 |
This change applies to a Sponsorship Batch. Previously, when a value larger than a 32-bit integer (2,147,483,647) was entered in the "Finder number" field in a batch, the following error displayed: "Arithmetic overflow error converting expression to data type int." With this fix, we modified the "BatchSponsorship" table to accept up to a 64-bit integer (to be consistent with other batch types that use Finder numbers, such as Enhanced Revenue Batch). | 394779 | BB750448 | 41 |
This change applies to a Sponsorship Batch. Previously, when you added a new organization, group, or household constituent through the "Financial sponsor" field and clicked "Save" on the Add a constituent screen, an error displayed. With this fix, the error no longer displays upon save. | 375753 | BB749121 | 41 |
This change applies to an Constituent Update Batch. Previously, upon validation and committal, the primary flag was incorrectly removed from email or phone records when the following occurred: Two or more constituents had identical email addresses or phone numbers, and one of those constituents was auto-matched by an incoming constituent whose data included the same email address or phone number. With this fix, the primary flag remains upon committal. Note that this fix only applies to records created after the fix is implemented. | 387169 | BB749857 | 55 |
This change applies to an Enhanced Revenue Batch in the Webshell version of Blackbaud CRM. Previously, when a tribute was selected and saved on the Tributes screen in a batch, the value in the "Default designation" field for the tribute was not added to the "Designation" field for the associated batch row. With this fix, the "Designation" field updates correctly. | 373400 | BB748940 | 41 |
This change applies to an Enhanced Revenue Batch that includes a payment split multiple ways. For example, the payment could be split between one or more designations or between commitments or donations. Previously, upon committal, the payment did not display correct recognition credits on the revenue record. With this fix, the revenue record correctly displays the associated recognition credits. | 351429 | BB741699 | 34 |
This change applies to an Enhanced Revenue Batch used in both Blackbaud Internet Solutions (BBIS) as well as Blackbaud CRM. Previously, when donation transactions used auto-match to find an existing constituent, an error displayed. With this fix, the auto-match process locates the existing constituent correctly and the error no longer displays. | 384441 | 37 | |
This change applies to an enhanced revenue batch when an account system’s Unmapped transaction setting allows unmapped transactions to be created using the GL account. Previously, when a user entered a stock transaction in a batch, the transaction was not validated properly against the GL account. During the validation and commit processes, an error displayed. With this fix, proper validation occurs and an error no longer displays. | 337873 | BB746578 | 34 |
This change applies to an Enhanced Revenue Batch when applying a payment to a pledge. Previously, when the default for Receipt type was set to Consolidated, upon committal, the Receipt type was overwritten with the global receipt setting Per payment. With this fix, we made code changes to the stored procedure to ensure Receipt type is respected upon committal. | 409909 | BB751398 | 53 |
This change applies to an Enhanced Revenue Batch when used through Import, manual batch entry, and Blackbaud Internet Solutions. Previously, when a transaction associated with an existing constituent was entered through a batch and committed, the lookup ID of the spouse was overwritten. With this fix, the spouse lookup ID is not overwritten during batch committal. | 372112 | BB748830 | 37 |
This change applies to an enhanced revenue batch where currency exchange fields are used. Previously, a user applied a pledge to a tribute, and saved and closed the batch. When the user opened the batch for editing, the tribute values were incorrect because currency exchange had been applied twice. With this fix, currency values are correct. | 346033 | BB746916 | 34 |
This change applies to an Enhanced Revenue Batch. Previously, a matching gift payment displayed the incorrect business unit when the original payment that generated the matching gift claim was entered using the "Finder number" field in a batch. With this fix, we made changes to the revenue split business unit specification file to ensure the correct business unit displays for the matching gift payment. | 330673 | BB745365 | 41 |
This change applies to an Enhanced Revenue Batch. Previously, when a payment was applied to a commitment as well as an additional application (such as an unapplied matching gift), and the designation was shared between both, a primary key error displayed. With this fix, the error no longer displays. | 396811 | BB748383 | 53 |
This change applies to an Enhanced Revenue Batch. Previously, when an individual or organization constituent record was edited in a batch and committed, recognition credit default settings associated with the constituent record were removed or deselected. With this fix, specification files were added and updated to ensure the default recognition credits remain unchanged upon committal. | 372108 | BB748829 | 41 |
This change applies to an Enhanced Revenue Batch. Previously, when importing matching gift payments and committing a batch, the receipt amount on the associated payment defaulted to zero. With this fix, the receipt amount is calculated correctly. | 386923 | BB748532 | 41 |
This change applies to an Enhanced Revenue Batch. Previously, when importing pledge payments and committing a batch, the receipt amount on the associated payment defaulted to zero. With this fix, the receipt amount is calculated correctly. | 367319 | BB748532 | 41 |
This change applies to an Enhanced Revenue Batch. Previously, when importing recurring gift payments and committing a batch, the receipt amount on the associated payment defaulted to zero. With this fix, the receipt amount is calculated correctly. | 386905 | BB748532 | 41 |
This change applies to an enhanced revenue batch. Previously, when the import process is used to add transactions to a batch, associated matching gift claims are not created upon committal. With this fix, the matching gift claims are correctly created upon committal. | 345608 | BB744331 | 34 |
This change applies to an Enhanced Revenue Batch. Previously, when you right-clicked on a highlighted row in the data entry grid, selected “Edit Constituent,” and clicked “Save” on the edit screen, an error displayed. With this fix, the error no longer displays upon save. | 385187 | 37 | |
This change applies to an Enhanced Revenue Batch. When multiple, identical addresses exist on a single constituent record where only the address type varies, the following error may display: "The address you entered already exists for this constituent." This error displays during the auto-match process because the program matches against the incorrect record. With this fix, we modified the auto-match process to consider address type and ensure the correct record is used during matching. Additionally, we modified the "Possible duplicate matches" screen to consider address, phone, and email types to ensure matching records display on the screen. | 276005 | 41 | |
This change applies to batch templates that use constituent matching. Upon commit, when the user selects “check for duplicates,” the correct matching thresholds from the batch template are now used. Previously, when committing a batch with "check for duplicates" selected, the matching algorithm assigned incorrect matching thresholds. In addition, depending on the global settings, the algorithm either failed the commit process for duplicates that should not have surfaced or passed the commit process by not allowing the correct duplicates to surface. This no longer occurs. As a recommendation, clients who experience this problem may need to recreate their custom batch template. | 310978 | BB743542 | 20 |
This change applies to Blackbaud Internet Solutions (BBIS) donation transactions downloaded into an Enhanced Revenue Batch. Previously, when a donation was made through BBIS and the "I prefer to make this donation anonymously" option was selected on the donation, when the transaction was downloaded into a batch, the option was not selected. With this fix, the option remains selected after the batch download. | 353815 | BB747765 | 37 |
This change applies to Blackbaud Internet Solutions (BBIS) donations downloaded into an Enhanced Revenue Batch. Previously, when duplicates were detected during the auto-match process where the matched constituent did not have an address, but the incoming constituent had an address with a specific type, the following error displayed upon committal: BBERR_ADDRESS_PRIMARYADDRESSREQUIRED. With this fix, we updated the auto-match process to correctly consider matches with no address to ensure the error no longer displays. | 400810 | 41 | |
This change applies to Blackbaud Internet Solutions when payments are applied to sponsorship recurring gifts in the transaction manager. After a payment is made to the first sponsorship recurring gift, when the sponsor applies a payment to the next gift, the amount that displays in the Amount field on the donation page reflects the amount from the first gift. With this fix, the correct amount displays in the Amount field. | 347563 | BB747017 | 29 |
This change applies to Blackbaud Internet Solutions. Previously, the Sponsorship Purchases page did not consistently display a sponsor’s name for unresolved online sponsorships purchases. Without a sponsor name, the Complete and Delete buttons on the action bar did not display as expected. With this fix, the sponsor name and associated action bar buttons display correctly for unresolved online sponsorship purchases. | 351068 | BB746219 | 41 |
This change applies to Blackbaud Internet Solutions. Previously, when a user referenced a CMS sponsorship query within a BBIS sponsorship search part, the search part page timed out. With this fix, we enhanced the query to ensure the page loads in a timely manner. | 347523 | BB746936 | 37 |
This change applies to Blackbaud Internet Solutions. With this fix, performance enhancements were made to the Sponsorship Status page as well as any page that includes a Query Results Display part referencing sponsorship query nodes. | 337967 | BB746599 | 37 |
This change applies to designations on opportunities. Previously, from an opportunity record, when you edited the opportunity and changed values for the Funding method, Category, Type, or Use code fields, the new values did not save. With this fix, the new values save appropriately. | 278464 | BB741678 | 34 |
This change applies to filter fields on the Encumbered Funds tab of a donor challenge record. Previously, when you selected "Encumbered" in the Status field and "All dates" in the Date range field, results were not returned in a timely manner. With this fix, we improved the processing performance of the filter fields. | 368014 | 41 | |
This change applies to non-administrative users with full security rights to Sponsorship and Revenue who access the "Add recurring additional gift" task on a Sponsorship page. Previously, when the "Add a recurring additional gift" screen was extended to include attribute categories, and a user added and saved data to this screen, an error displayed. With this fix, the error no longer displays upon save. | 349524 | BB747301 | 37 |
This change applies to payment transactions entered in an Enhanced Revenue Batch where Multicurrency is enabled. When the value in the Transaction currency field for a transaction is changed after an amount is entered, the recognition is set to a zero amount. This occurs when the transaction and base currencies are different and an exchange rate cannot be retrieved. With this fix, when an exchange rate exists between the transaction and base currency, the most current exchange rate is used to correctly calculate the base and recognition amounts. | 338799 | BB746709 | 34 |
This change applies to posted pledges that are being updated through a Revenue Update Batch. Previously, when a posted pledge was associated with a zero-dollar transaction, and the pledge amount was lowered, the installment associated with the zero-dollar transaction was incorrectly distributed. With this fix, the installment is distributed correctly. | 350466 | BB734750 | 37 |
This change applies to recognition credit amounts in an Enhanced Revenue Batch. Previously, when a donation amount was changed on the "Apply to commitments" screen, the "Recognitions" screen did not display the updated amount. With this fix, the "Recognitions" screen immediately displays the updated amount. | 368962 | BB748627 | 37 |
This change applies to recurring gifts associated with sponsorships. Previously, when a user updated a recurring gift through a Revenue Update Batch, the sponsorship link on the recurring gift record no longer displayed. With this fix, the sponsorship link correctly displays on the recurring gift record. | 326415 | BB745562 | 34 |
This change applies to site security on the Major Giving Management – Fundraisers and Steps page. Previously, on the Overdue Steps tab, the "Overdue steps" grid did not correctly filter or secure stewardship plan steps according to the appropriate site security. With this fix, site security is respected. | 367586 | BB747085 | 37 |
This change applies to the "Apply Matching Gift Payments" tab on the Reconcile Matching Gifts page accessed from Revenue. Previously, when an unapplied matching gift claim payment was applied on the "Apply Matching Gift Payments" tab, recognition credits did not update correctly for the applied payment. With this fix, recognition credit updates correctly. | 373851 | BB748987 | 53 |
This change applies to the ClickOnce version of Blackbaud CRM. Previously, when a user attempted to save a Constituent Update Batch, the error message "column does not accept nulls" appeared. With this fix, the error no longer appears upon save. | 351931 | BB747587 | 34 |
This change applies to the duplicate check process in Blackbaud CRM. Previously, when matching an incoming constituent with a title and gender to an existing constituent with a different title and gender, the matching process deducted a small number from the matching score and presented the records as likely matches. With this fix, the process deducts a higher number from the matching score and presents the records as unlikely matches. This matching rule only applies when title codes are associated with genders as defined on the "Title Code Defaults" page in Constituents. | 367944 | BB748596 | 37 |
This change applies to the duplicate check process in Blackbaud CRM. Previously, when two identical constituents were added to the database, a 100% match was presented. If a user selected to add one of the duplicates as a new record, all subsequent identical matches were not presented at a 100% match. With this fix, all duplicate constituents are correctly displayed at a 100% match. | 356556 | BB748031 | 34 |
This change applies to the Fundraisers tab of the "Major Giving Management – Fundraisers and Steps" page in Prospects. Previously, when you selected the "Include stewardship steps" filter, stewardship steps were not included in the results. With this fix, when you select this filter, stewardship steps now display. | 385116 | BB749739 | 53 |
This change applies to the Planned Gifts tab of a major giving group record. Previously, the Planned Gifts tab did not accurately calculate planned gift additions when displaying totals for balance, payments, and accepted amounts. With this fix, planned gift additions are accurately reflected on the tab. | 321784 | BB744803 | 34 |
This change applies to the recognition process when the "Consider recognition credits in donor constituency definitions" checkbox is selected when editing donor constituency criteria from "Constituents." Previously, when the checkbox was selected, "Major donor" and "Loyal donor" constituencies were not properly assigned to constituents who should have received revenue recognition. Also, these constituencies were not using the reporting filter default to determine which gifts count toward constituencies. This fix corrects both issues. | 358549 | BB743065 | 37 |
This change applies to the reconcile matching gifts process in Revenue. Previously, during reconciliation, when a user selected a related constituent's payment associated with a different currency than the unapplied claim to reconcile, the following error displayed: "Conversion from string (amount) to type decimal is not valid." With this fix, the error no longer displays. | 387164 | 53 | |
This change applies to the Revenue Summary and Recognition Summary tabs on the Revenue tab of a constituent record when "Fiscal year" is selected in the Breakdown field. Previously, under Revenue summary and Revenue by year (Revenue Summary tab) and Recognition summary and Recognition by year (Recognition Summary tab), the program displayed the year a gift was given. With this fix, the year now displays as the user-defined fiscal year associated with the gift. | 300013 | BB742197 | 34 |
This change applies to the Revenue tab for a constituent group or committee. Previously, from the Recognition History tab, when you selected a filter in the Type field, an error displayed. With this fix, the error no longer displays. | 337545 | BB742946 | 34 |
This change applies to the Unassigned Prospects tab of the Major Giving Management – Prospects page. Previously, for non-administrative users, the Unassigned Prospects tab did not display a full list of unassigned prospects. With this fix, we changed site security code to ensure a complete list of unassigned prospects displays when accessed by non-administrative users. | 373023 | BB748928 | 53 |
This change applies to the webshell version of Blackbaud CRM. Previously, in any batch where credit card fields existed, when you added a row of data, saved the batch, and continued to add or edit data in the saved rows, field values did not save correctly. With this fix, all field values save correctly. | 358363 | 34 | |
This change improves the methods data lists use to connect with the database server and strengthens system stability to prevent program failures. | 320606 | BB742469 | 39 |
This change is associated with the "Correct capitalization in name and address fields" global data entry setting that allows for automatic capitalization of names and addresses during data entry, as well as the "Standardize constituent name/addresses" global change that fixes existing names and addresses. Previously, for addresses with multiple lines, when the global data entry setting was selected, the automatic capitalization removed the new line character and displayed multiple address lines on one line. With this fix, the global data entry setting no longer causes addresses with multiple lines to display on one line. | 352311 | BB747634 | 34 |
This change resolves an issue that occurred for failures on custom parts that use the BBNCExtensions API. Previously when credit card processing, form submission validation, and record saving validation failures occurred for recurring transactions, the BBNCExtensions.API.Transactions.RecordDonationReply object did not provide error messages. If you use the BBNCExtensions API with a custom part, we recommend you review your code to ensure it properly handles the new messages. For additional information about the change, please contact Customer Support. | 370219 | BB748732 | 41 |
This error no longer occurs when viewing a List Profile report for an acquisition list with a category assigned: Error: The Hidden expression for the tablix ‘table1’ uses a numeric aggregate function on data that is not numeric. Numeric aggregate functions (Sum, Avg, StDev, Var, StDevP, and VarP) can only aggregate numeric data. | 369720 | BB748658 | 37 |
This fix address an issue with auction purchase payments. Now, when the auction item purchased is marked as "Do not post," you can still post and make adjustments, such as gains and losses against the fair market value of the item, to the auction purchase payment. Changing the post status on the auction item will still cause multiple distributions to be created on the posted auction purchase payment. | 287202 | BB742102 | 37 |
This fix addresses a credit card processing issue in batch with the Blackbaud Payment Service. Previously, the transaction amount sent to the Blackbaud Payment Service did not respect the proper decimal and grouping separator format of certain locales. Now, when a credit card is processed from a batch, CRM sends the user’s locale information to the Blackbaud Payment Service with each credit card transaction. For users in the WebUI version of the program, CRM uses the locale information from the user’s browser. For users in the ClickOnce version of the program, CRM uses the locale information from the web server. | 378101 | 37 | |
This fix addresses a performance issue in the Blackbaud Data Warehouse with the BBDW_DIM_MARKETINGSEGMENT and BBDW_DIM_MARKETINGSOURCECODEPART packages. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 392841 | BB749772 | 53 |
This fix addresses a performance issue on the History tab of business process pages throughout the program. The issue occurred when the program attempted to display status information for current processes and the database contained data for millions of completed processes. | 344984 | 53 | |
This fix addresses a performance issue that occurred on the History tab of the Import process page. Previously, a timeout message sometimes appeared before the data was available. | 354958 | BB747826 | 37 |
This fix addresses a performance issue that occurred on the Uncommitted Batches tab of the Batch Entry page. Previously, when the database included a large number of batches, an error message appeared before the data was available. | 401636 | BB750886 | 53 |
This fix addresses a performance issue that occurred when you opened the sites filter in Chrome and Safari. Previously, the site hierarchy always used the expanded view and loaded slowly when it included a large number of sites. Now, the site hierarchy uses the collapsed view when the number of sites exceeds 2000. | 372760 | BB748915 | 37 |
This fix addresses a performance issue when committing a Constituent Update Batch. | 356074 | BB738961 | 37 |
This fix addresses a performance issue when trying to open the Add payment screen from the Revenue and Recognition page of a constituent. Previously this screen loaded very slowly or timed out. | 356796 | BB748081 | 34 |
This fix addresses a performance issue with the Adjusted Revenue report which resulted in system-wide slowness, particularly when site security was not set up. Previously, site security checks were made when you ran this report even when site security was not set up. Also, the site security checks prevented users from getting the correct results when there were adjusted "child" financial transactions, such as adjustments to sold stock. Now, site security checks are not made when you run the report if site security is not set up in CRM and the correct results are returned. | 364281 | BB746573 | 37 |
This fix addresses a performance issue with the Global pledge write-off process in Revenue. | 323034 | BB744997 | 34 |
This fix addresses a performance issue with the Post to GL process when using a dynamic deposit selection. | 349243 | BB747271 | 34 |
This fix addresses a performance issue with the Post to GL process when using a Revenue selection. Previously, some users may have experienced trouble logging into the system when the process was running due to the performance issue. | 379329 | BB748882 | 37 |
This fix addresses a performance issue with the R68 online submission process. Previously, the Submit file to HMRC step could time out after two minutes with an error. | 372582 | BB748883 | 37 |
This fix addresses a performance issue with the Revenue by Payment Method report in systems that do not use both multicurrency and site security. | 333153 | BB738766 | 28 |
This fix addresses a possible revision error encountered when upgrading to Blackbaud CRM 3.0, Service Pack 5. The revisions affected are 14115 and 14125 of revision set 1341. The fix includes a new revision which will prevent the specified revisions from failing. | 351304 | BB747455 | 34 |
This fix addresses a potential performance issue on the Registrations tab of events. This issue occurred for events with at least one invitee when the database had a large number of invitees across all events. | 333389 | BB744995 | 28 |
This fix addresses a potential vulnerability on web dashboards that could have allowed malicious users to access secure areas of the program. | 410553 | 53 | |
This fix addresses a time out error which occurred when a non-administrator user in site-secured environment attempted to view the Revenue History tab of a constituent record. | 392468 | BB750317 | 41 |
This fix addresses a timeout issue which occurred when processing a large number of R68 Gift Aid claims. | 388575 | BB750027 | 55 |
This fix addresses an error that occurred when a credit card rejection message was longer than 250 characters. The error occurred in batches with a REJECTIONMESSAGE field with a length of 250 characters when a rejection message of more than 250 characters was received. Now we truncate any error messages longer than 250 characters and have adjusted the existing rejection messages to be 250 or fewer characters. | 408284 | BB751164 | 53 |
This fix addresses an error that occurred when a credit card rejection message was longer than 250 characters. The error occurred in batches with a REJECTIONMESSAGE field with a length of 250 characters when a rejection message of more than 250 characters was received. Now we truncate any error messages longer than 250 characters and have adjusted the existing rejection messages to be 250 or fewer characters. | 406660 | BB751164 | 44 |
This fix addresses an error that occurred when queries in the webshell version of Blackbaud CRM were edited. Previously, an error message appeared when the result fields included “Exist in” options from the Selections folder. | 356677 | BB748056 | 37 |
This fix addresses an error that occurred when you edited a posted payment, removed the original payment application, and then tried to apply the payment to a "Grant award" application instead. | 345716 | BB746852 | 34 |
This fix addresses an error that sometimes incorrectly appeared when you imported a file into a Constituent Update Batch. Previously, when the spouse lookup ID was required and your import file included a spouse lookup ID, you could still get an error indicating that the field was required. Now, when the field is included, you do not receive this error. | 304923 | BB743262 | 37 |
This fix addresses an error when you add a new primary address to a constituent through a Constituent Update Batch. Previously, you sometimes got an error if the new primary address had the same address type as the old primary address when you committed the batch. | 334291 | BB746313 | 34 |
This fix addresses an error which intermittently occurred when adding memberships using the Membership Dues Batch. The error "Cannot insert NULL into column 'NAMECODE', table 'Infinity.dbo.BATCHMEMBERSHIPDUES'; column does not allow nulls. INSERT fails." no longer occurs when you click the Next Payment button. | 418002 | BB751932 | 53 |
This fix addresses an error which occurred when merging two constituents who were registered for the same event. If no payments are associated with the event registrations, the constituents will now be merged with the event registration of the target constituent. The constituents will not be merged if both constituents have registrations for the same event and either registration has an event registration payment or an event registration payment pending in an uncommitted batch. Depending on the situation, if the constituents were merged, the target constituent could mistakenly have an over- or under-payment of the event registration or the target could have duplicate revenue for the event registration. | 360253 | BB748262 | 37 |
This fix addresses an error which occurred when using the event search field on the Events page. Previously, if you changed the Event Work Center Event Search to use a different event search using Search List Replacements in Administration, you received an error when you tried to use the event search field. | 382792 | 37 | |
This fix addresses an error which occurred when you edited the benefits on a posted payment and tried to waive those benefits. The error prevented you from being able to save the posted payment with the benefits waived. | 346048 | BB746921 | 34 |
This fix addresses an error which sometimes occurred when you deleted an event registration payment and then tried to remove the registrant from the event. The payment, even though it was deleted, was still linked to the registration. Now when you delete the payment, the link to the registration is also deleted so you can remove the registrant from the event. | 398878 | BB750685 | 42 |
This fix addresses an exception that sometimes occurred when running the credit card processing process. Previously, you received an exception when the Credit Card Number field was marked as required on the batch template and the credit card was no longer stored in the Blackbaud Payment Service. | 350226 | BB747347 | 53 |
This fix addresses an issue in Revenue Update Batch where the receipt amount for a pledge installment payment was incorrect after changing the amount from a partial payment to a full payment. The constituent also had to have an unpaid event registration commitment. This issue occurred in the ClickOnce version of the program only. | 347637 | 34 | |
This fix addresses an issue introduced in service pack 8 when running the Blackbaud Data Warehouse validation process. Previously, when you ran the validation, you received an exception indicating that there were null values on the Online System ID column. This happened because that column did not have default values. With this fix, we have added default values to the column so the exception no longer appears. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 417354 | BB751922 | 53 |
This fix addresses an issue introduced in service pack 8 when running the Blackbaud Data Warehouse validation process. Previously, when you ran the validation, you received an exception indicating that there were null values on the Online System ID column. This happened because that column did not have default values. With this fix, we have added default values to the column so the exception no longer appears. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 405338 | 53 | |
This fix addresses an issue so that time zones are now respected when syncing constituent interactions, prospect plan steps, and pending stewardship steps with Microsoft Exchange calendars for users. | 330873 | BB746029 | 28 |
This fix addresses an issue that allowed individual records to have multiple primary businesses. Previously, when you edited relationships between a constituent and an organization and the constituent had more than one relationship type with that organization, it was possible for the individual to show more than one primary relationship. This happened when you edited the non-primary relationship and made it the primary business for that constituent. In this case, the business relationship that was previously marked as primary remained that way, so both relationships were primary at the same time. | 391840 | BB750002 | 41 |
This fix addresses an issue that caused an error message to appear when adjusting a posted pledge. Previously, if the posted pledge payment amount was set to "0" and the user then attempted to set the pledge value to "0," a divide by zero error would occur. Now, the pledge value updates correctly. | 407925 | BB751276 | 53 |
This fix addresses an issue that caused the receipt amount to be incorrect for partial payments toward event registrations. | 351152 | BB747431 | 41 |
This fix addresses an issue that occurred after altering the benefits associated with a posted gift fee adjustment. Previously, the gift fee would maintain its post status of "Posted" despite choosing to reset the gift fee. Now, the correct gift fee general ledger distributions are generated. | 385335 | 53 | |
This fix addresses an issue that prevented the Generate payments process from generating payments for membership installment plans when the membership included one or more children. | 401120 | 53 | |
This fix addresses an issue that sometimes caused constituency information to be lost when you imported user registrations from BBIS. Previously, when you had an existing constituent with a user-added constituency, and then you imported that constituent through a BBIS batch, the constituency information was lost. This happened when you imported data using a BBIS Event Registration Batch, a BBIS Revenue Batch, or a BBIS Signup Transaction Batch. | 367342 | 53 | |
This fix addresses an issue that sometimes occurred with attributes in Enhanced Revenue Batches. Previously, when you ran the credit card process for an Enhanced Revenue Batch and one or more of the credit cards were provisionally rejected, the automatically generated retry batch included duplicates of any attributes present in the original batch. | 370500 | BB748760 | 53 |
This fix addresses an issue when calling USP_REVENUEDETAIL_EDIT_2 directly. Previously, when calling USP_REVENUEDETAIL_EDIT_2 directly, an error could occur and no changes would be made to the database. | 316655 | BB743869 | 28 |
This fix addresses an issue when editing a default tribute letter from a constituent's page. Previously, editing the tribute letter from the constituent page would erroneously set all the acknowledgee's letters to the default tribute letter. Now, editing the default letter will only affect the tributee's acknowledgement letter. | 378463 | BB749203 | 41 |
This fix addresses an issue when editing a pledge with posted payments. Unnecessary payment adjustments will no longer be created when changing the designation on unpaid installments. | 358586 | BB742000 | 37 |
This fix addresses an issue when migrating to SQL Server compatibility level 110, available in SQL Server 2012 and later versions. Previously, several functional areas did not appear after migration when running SQL Server 2012, compatibility level 110. | 392162 | BB750366 | 41 |
This fix addresses an issue when saving email addresses with special characters. Previously, if you tried to add an email address to a constituent record that included a special character (such as an umlaut, for example), you received an error indicating that the email address was invalid and could not be saved. | 349271 | BB747278 | 37 |
This fix addresses an issue when viewing an event registrant listed on the Registrations tab of a multi-level event. Previously, an error occurred if the "Update event attendance" task had been run to update the registrant’s status to "No-show." | 356696 | BB748060 | 37 |
This fix addresses an issue when you filtered business process reminders by date. Previously, when you filtered by date, the list took too long to load, and the process could time out. | 334465 | BB703627 | 28 |
This fix addresses an issue when you merged two constituent records and the source record was in use by a constituent batch. Previously, if the record to be deleted was in use by a constituent batch, you received an error because the batch process no longer recognized the record as valid. In addition, even though the data was merged into the target record, the source record was not deleted if it was in use by a batch, leaving potential duplicates. With this fix, once the records are merged, the entry in the constituent batch is updated to reference the correct record. | 383181 | 41 | |
This fix addresses an issue where constituent records could not be deleted if they were associated with a declined recognition level on the Recognition tab. The error occurred whenever a constituent with a declined recognition level was deleted, including through a constituent merge task. Now when a constituent record is deleted, the declined recognition level is also deleted. | 333266 | BB746246 | 37 |
This fix addresses an issue where receipt amounts were being incorrectly calculated when automatically applying a payment to multiple pledges in Enhanced Revenue Batch in the ClickOnce version of the program. | 359048 | 35 | |
This fix addresses an issue where receipt amounts were being incorrectly calculated when automatically applying a payment to multiple pledges in Enhanced Revenue Batch. | 355278 | BB747882 | 35 |
This fix addresses an issue where revenue records which could not be posted to the general ledger (such as recurring gifts) could have been displayed with an incorrect base currency symbol in revenue queries. This issue occurred only in multicurrency environments. | 345271 | BB746822 | 34 |
This fix addresses an issue where the Gift Aid revenue split was not being properly removed from the revenue record if you deleted the constituent’s Gift Aid declaration or changed the constituent associated with the revenue. | 347730 | 34 | |
This fix addresses an issue where the pledge write-off amounts displayed in the Recent revenue section of a constituent Summary tab were rounded to the nearest dollar. | 357253 | BB747588 | 37 |
This fix addresses an issue where users trying to view the Annual Performance Report received connection errors due to the Appeal Performance Report not setting the datasource correctly when loading. In order to utilize this fix, users will need to reload the Appeal Performance Report. | 412946 | BB751632 | 53 |
This fix addresses an issue which occurred when adding a Gift Aid declaration for a constituent when the constituent already had a pledge in the date range considered valid for the declaration. Previously, after the declaration was added, the value in the "Gross amount" column for the pledge displayed on the Revenue History tab for the constituent was not correctly updated to reflect the change. This fix affects UK clients only. | 369305 | BB748634 | 53 |
This fix addresses an issue which occurred when you attempted to view the application details on the Details tab of a revenue transaction. Previously, the application details were slow or failed to load. | 389667 | BB750142 | 43 |
This fix addresses an issue with banks using the "Other" banking system, which is set up by clicking "Banking systems" in Treasury. Previously, you sometimes received an error when running the Generate direct debit files process for a bank account with the "Other" banking system. Now the process runs and the batch of records is created correctly. However, you still cannot download the transmission file unless you have a customized download to create the file according to the other banking system's standards. | 434854 | BB752885 | 56 |
This fix addresses an issue with benefit attributes not appearing in the Blackbaud Data Warehouse. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 385406 | 37 | |
This fix addresses an issue with date filters when running the General Ledger post process with a revenue or deposit selection. Previously, selecting "Selected Revenue records" from the revenue option of a Post to GL process could result in records being incorrectly posted outside of the post process date range. | 405232 | BB751051 | 53 |
This fix addresses an issue with editing the designations of a posted pledge. Previously, if the designations were deleted and the exact same designations were re-added, the posted pledge’s status would be set to "Do not post." Now, a correct adjustment generates and the post status is set to "Posted (activity pending)." | 401093 | 53 | |
This fix addresses an issue with Group Sales. Previously, from the Reservations List tab when you clicked Add and then Add payment, the Add a payment screen was not displayed. | 393109 | 38 | |
This fix addresses an issue with importing memberships which create installment plans or recurring gifts. Previously, the payment details were not saved to the installment plan or recurring gift. | 340451 | 34 | |
This fix addresses an issue with incorrect event invitee numbers on the Event Profile report and in the Event Summary node in Query. The issue occurred when a constituent was invited to the same event using multiple Invitation Processes. You can refresh the report or query results to view the correct counts. | 412426 | BB751537 | 53 |
This fix addresses an issue with membership transactions from Blackbaud Internet Solutions. Previously, if a constituent was already a member of a program that did not allow multiple memberships and the constituent paid for that membership again on the website, the membership was turned into a "Renew" or "Rejoin" transaction when it was downloaded into the Membership Dues Batch. The amount was also changed if the renewal or rejoin amount was different than the membership "Join" amount, which caused a mismatch between what the constituent actually paid and what the membership transaction amount is in CRM. Now, the membership will be renewed, not rejoined, and the amount field will remain unchanged. | 430294 | BB752576 | 54 |
This fix addresses an issue with posted, but unapplied matching gift claim payments. The correct ledger adjustments are now created when you change the designation on the payment. | 358340 | BB747802 | 37 |
This fix addresses an issue with queries. Previously, they would not filter correctly on membership cancellation reason codes after the queries were saved. | 392744 | BB750336 | 53 |
This fix addresses an issue with running the credit card process when there is a problem with a credit card token not being present in either CRM or in the Blackbaud Payment Service. Previously, users were not necessarily made aware there was an issue and the credit card transaction was not processed. Now, when there is an issue with the credit card token, the batch row error message states, "The donor’s current credit card information cannot be used to successfully process this payment. Please contact the donor to get updated credit card information. You will need to update the credit card information in the batch row to process the current payment. You will need to update the credit card information on the original revenue commitment record in order to process future payments. | 373967 | 37 | |
This fix addresses an issue with service revisions when upgrading to 3.0. The revisions would previously fail while trying to alter certain transactions marked as deleted. | 329397 | BB745901 | 28 |
This fix addresses an issue with sponsorship recurring gifts from Blackbaud Internet Solutions. The issue occurred in CRM version 3.0 Service Pack 8 and higher. Previously, the credit card numbers for these transactions received tokens from the Blackbaud Payment Service, but the tokens were not saved correctly in CRM. | 439176 | 55 | |
This fix addresses an issue with the direct debit process in the ClickOnce version of the program. Previously, when you tried to download and open the direct debit transmission file, you received an error. However, you could download and open the file in the WebUI version of the program. | 384219 | BB749659 | 41 |
This fix addresses an issue with the ETL process when your database had a large number of fundraiser teams. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 408123 | 53 | |
This fix addresses an issue with the expiration date of memberships when upgrading them in a Membership Dues Batch. Previously, the expiration date of the membership was not editable upon upgrade. | 402146 | BB750920 | 55 |
This fix addresses an issue with the membership contribution process. Previously, it was renewing memberships for dues-based levels if the membership was in the program's renewal window. | 387753 | 41 | |
This fix addresses an issue with the Membership Dues Batch. Previously, when you changed the "Expires on" date in the batch grid view and then clicked "Return to form," the "Expires on" date on the form did not have the changes made in the batch. | 375343 | BB749117 | 41 |
This fix addresses an issue with the Membership part in Blackbaud Internet Solutions. When you have a membership program in CRM with multiple terms and levels and configure the Membership part with only one level, the part would not save any terms for the level. | 356782 | BB748079 | 41 |
This fix addresses an issue with the payment query. Previously, the query returned all transaction types rather than just payment transactions. The query now functions as designed. | 389737 | BB750145 | 53 |
This fix addresses an issue with the Recent revenue list on the Summary tab of a constituent. Previously, revenue entries were missing from the list when a single payment was applied to multiple designations. | 391097 | BB750209 | 41 |
This fix addresses performance within Prospects functional area of the program. Customers no longer receive an error when loading and viewing information about asks and total revenue received on the Summary tab of an Opportunity record. | 287224 | BB741384 | 53 |
This fix addresses possible revision errors encountered when upgrading to Blackbaud CRM 3.0 on SQL Server 2012. The revisions affected are 12080 and 12085 of revision set 1310, 970 of revision set 1311, and 275 of revision set 1321, as well as 10510, 63880, and 63885 of revision set 1120. | 347879 | BB747039 | 37 |
This fix addresses slow performance that occurred when users without administrator rights added solicit codes to a constituent record. | 352210 | BB747603 | 37 |
This fix allows a membership installment plan payment to be made toward a membership level or term that is currently inactive. Previously, if you added a membership which was paid with an installment plan and then made the membership level or term inactive, an error occurred which prevented the installments from being added. Memberships for levels or terms which have since been marked inactive cannot be renewed, but can still accept payments for the current commitment. | 277233 | BB741523 | 24 |
This fix allows you to apply revenue to a membership recurring gift commitment from the Edit payment screen. Previously, membership recurring gifts were not displayed as outstanding commitments. | 302411 | BB742660 | 24 |
This fix applies to an Enhanced Revenue Batch where the Finder number field is required. When a value for the required Finder number field does not exist, the validation error that displays does not specify that the error is associated with the missing field value. With this fix, an accurate error message displays during validation. | 325465 | BB740606 | 24 |
This fix applies to an Enhanced Revenue Batch. Previously, when "Check for duplicate constituents" was selected on the Commit parameters screen and the auto-match process ran, the following error displayed: "The current user does not have rights to use this feature in the context of this specific record." With this fix, the error no longer displays. This fix corrects an issue introduced in 372112 (SP 7). | 391629 | BB750260 | 38 |
This fix applies to the validation process for an enhanced revenue batch. Previously, when the account system setup used revenue categories, the GL distributions were incorrect for pledges with a specified revenue category. This caused incorrect validation. With this fix, the validation processes correctly. | 333303 | BB744990 | 34 |
This fix corrects a gender data issue for a website user's spouse when you process an online donation from your Blackbaud Internet Solutions website. Previously, the spouse's gender changed from the original selection ("Male" or "Female") to "Unknown" on the constituent record after you processed the donation. This occurred because the information was not saved as a part of the transaction process from Blackbaud Internet Solutions to Blackbaud CRM. Now, the transaction saves the spouse's gender so the correct data continues to appear on the constituent record after you process the donation. | 372118 | BB748831 | 41 |
This fix corrects a performance issue in the appeal email list processor for Blackbaud Internet Solutions. When you send a message with an appeal data source to a large recipient list, the message can now process successfully without timing out. | 290256 | BB742296 | 24 |
This fix corrects an error which occurred when you tried to edit a posted grant award revenue transaction. | 358515 | 37 | |
This fix corrects an issue for countries that have the same associated state values in Blackbaud Internet Solutions. Previously, when a website user selected a country with state values that were the same for another country (for example, Malta and New Zealand both include the state value "Not Applicable" with the state abbreviation value "N/A"), a different country appeared in the Transaction details for the batch in Blackbaud CRM. To correct this, the program now only performs a look up for State and Country fields when a website user leaves the Country field blank on a web page in Blackbaud Internet Solutions. | 339725 | 34 | |
This fix corrects an issue for eReceipts on the Transaction Manager part on your Blackbaud Internet Solutions website. Previously, if a website user submitted a donation without logging into your site and then later logged into your site to view the receipt on the part, the eReceipt link was incorrect. Now, the eReceipt link opens the correct receipt whether the website user was logged in or not. | 407233 | BB751208 | 53 |
This fix corrects an issue introduced in service pack 5 that caused user-defined smart queries with "Exists in Selection" parameter fields to display an error message. The error occurred when the queries were generated or edited. | 369665 | BB748423 | 37 |
This fix corrects an issue so that a profile update transaction processes successfully when the website user’s birthday is a fuzzy date (for example, 1/1990) on the constituent record in Blackbaud CRM. Previously, the program could not process a fuzzy date which prevented the transaction from downloading to Blackbaud CRM from Blackbaud Internet Solutions. Note: This only applies when the Birth date field is not on the Profile Update form on your website. If the Birth date field appears on the form, the date must be a complete value (for example, 1/1/1990.) | 382946 | 37 | |
This fix corrects an issue so the Donate widget successfully displays donor recognition and the thermometer for a participant's web page on mobile devices when you use Blackbaud Friends Asking Friends. Previously, these features only worked for Desktop browsers and did not appear for mobile devices. Note: After you implement this fix, we recommend you test the Donate widget display on mobile devices to make sure style sheet adjustments are not necessary. | 351686 | 34 | |
This fix corrects an issue that intermittently prevented users from receiving Blackbaud Internet Solutions emails after they made a donation or registered for an event. | 326190 | BB745500 | 26 |
This fix corrects an issue that prevented profile transactions without origin information (for example, page name or page ID) from downloading to Blackbaud CRM from Blackbaud Internet Solutions. | 349839 | BB745585 | 41 |
This fix corrects an issue when the RECORDSECURITY_ENABLED_FOR_SEARCHLIST setting in the web.config file is set to 'true' so that a user with rights to appeals in Blackbaud CRM and Blackbaud Internet Solutions can successfully search for and find an appeal in Blackbaud Internet Solutions. | 348973 | BB743930 | 34 |
This fix corrects an issue where a changed revenue application was not posted when the Post to GL process was set to include "Not posted adjustments and reversals only." Previously, for a posted revenue transaction, if a user edited the payment, deleted an application, and then added a new application, the reversal was posted, but the changed application was not. | 356170 | BB748027 | 37 |
This fix corrects an issue where certain drop-down lists would not refresh correctly after changing pages in a batch. This affects only the WebUI version. | 352538 | BB747671 | 37 |
This fix corrects an issue with the Constituent revenue amounts smart field when set up to return the "Largest gift amount." Previously, when the smart field included event registration fees and was set up to include only revenue with specific designations, the results it displayed were not correct. | 328394 | BB745761 | 37 |
This fix displays a message to donors on your website when a timeout occurs in Blackbaud Merchant Services or Blackbaud Payment Services. The message informs donors that their transactions are still processing to prevent them from attempting to resubmit their donations multiple times. This change applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 333124 | BB746229 | 26 |
This fix eliminates a 'Cannot convert string to date' error message for date attributes in a profile update transaction from Blackbaud Internet Solutions. The message appeared when processing the transaction in a Constituent Update Batch in Blackbaud CRM and the profile form did NOT include the date attributes, but the constituent record included one using the format (dd/mm/yyyy). To correct this issue, a standard date format is now used for date attributes from Blackbaud Internet Solutions to make sure date formats process using the same format used in Blackbaud CRM. | 331420 | 29 | |
This fix eliminates a conflict error that may occur in database 'dbo.PHONE' when you commit an Enhanced Revenue Batch that includes donations from Blackbaud Internet Solutions. To eliminate this error, the constituent update rules for the batch attempt to match an unformatted phone number to an existing formatted phone number when the website user from Blackbaud Internet Solutions matches an existing constituent in Blackbaud CRM during the batch and commit process. Also, a failsafe has been added in the batch commit code to properly handle the conflict error if it occurs in the dbo.PHONE table. | 328114 | BB745725 | 25 |
This fix eliminates a time out issue when you attempt to access the Communications tab on a constituent record. To resolve this issue, the stored procedure USP_DATAFORMTEMPLATE_VIEW_CONSTITUENTCORRESPONDENCEPREVIEWCOMMUNITYEMAIL has been updated to improve performance and avoid time outs. | 386166 | BB749802 | 53 |
This fix eliminates an "Object reference not set to an instance of an object" exception when you edit, validate, or commit a transaction in the BBIS Profile Update Transaction Batch in Blackbaud CRM. This exception occurred when NULL handling was missing for primary business data for a constituent. To resolve this issue, the BBNCProfileBatchCommit.vb code has been updated. | 386658 | BB749832 | 53 |
This fix eliminates an error and the inability to edit content (for example, parts) when Blackbaud Internet Solutions is installed on SQL Server 2012. This occurred because the stored procedure USP_TEMPDATA_ADD converted dates and times that SQL Server 2008 accepted, but SQL Server 2012 did not. The stored procedure has now been updated so that SQL Server 2012 successfully accepts the converted dates and times and content is editable again. | 419474 | 53 | |
This fix eliminates an error when a non-supervisor user accesses the Image library or attempts to upload an image in a part. To correct this, permission has been granted to the user functions UFN_CLIENTUSERS_TASKS, UFN_CLIENTUSERS_OBJECTTASKOBJECTS, and UFN_CLIENTUSERS_TASKS so all users with applicable rights in the program can successfully access the library and upload images in parts. This fix applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 326412 | 24 | |
This fix eliminates an occasional "Index was outside of the bounds of the array" error when a website user attempts to donate or register on your Blackbaud Friends Asking Friends website. This occurred because the program's code did not ensure an array had a value when required. The code has been updated to eliminate that gap so users can donate and register successfully. | 406675 | BB751167 | 46 |
This fix eliminates an occasional Index was outside of the bounds of the array error when a website user attempts to donate or register on your Blackbaud Friends Asking Friends website. This occurred because the program's code did not ensure an array had a value when required. The code has been updated to eliminate that gap so users can donate and register successfully. | 409832 | BB751167 | 53 |
This fix eliminates the "One-time gifts must have a credit card payment option" message that appeared in Blackbaud Internet Solutions when you tried to save a Donation Form part for pledges. This issue was introduced in Service Pack 4 for work item 310918 which required you to select the credit card payment option for one-time gifts. The part has been updated to save for pledges without requiring the credit card payment option. | 352211 | BB747611 | 34 |
This fix eliminates the CK_CONSTITUENCY_ISUNIQUE exception when validating an Enhanced Revenue Batch for transactions from Blackbaud Internet Solutions. It also ensures that existing constituencies on the Blackbaud CRM record remain the same when the transaction includes a new constituency. | 324698 | 24 | |
This fix enables Blackbaud Internet Solutions to transmit data to Blackbaud CRM when users navigate from your Blackbaud Internet Solutions Payment 2.0 web page to the secure payment page and an interruption unexpectedly occurs before the transaction is submitted. Now data from the transaction is temporarily stored in a new CMS_SessionVariableBackup database table so Blackbaud Internet Solutions can send the information to Blackbaud CRM. To support this enhancement, two new web.config settings exist for you to select how often the program checks the table for data and for you to select whether remaining data in the table is pushed to another new CMS_ UnprocessedBBSPTransaction archive table or deletes permanently. For details about this fix, refer to https://www.blackbaud.com/files/support/guides/enterprise/300/bbistrans.pdf. | 431909 | 55 | |
This fix ensures that constituent attribute dates only allow for date values on the User Login part on your Blackbaud Internet Solutions website. Previously, website users could submit numerical values that are not possible to be a date, such as "12345678." These values prevented you from downloading the transaction in Blackbaud CRM. The program has been updated to make sure values are valid for constituent attribute dates. Also, when you run the upgrade that applies this fix, a revision runs to remove non-date values from failing transaction so they can download successfully. | 402416 | BB750948 | 53 |
This fix helps prevent constituents from receiving duplicate emails sent from Blackbaud Internet Solutions. | 412756 | BB751626 | 55 |
This fix improves a performance issue when editing a posted payment to change the constituent. | 353854 | BB747777 | 37 |
This fix improves a performance issue when editing posted payments. | 357398 | BB748139 | 37 |
This fix improves a performance issue when running a Constituent recognition process. | 273600 | BB739252 | 24 |
This fix improves performance and helps prevent a timeout error when you upload a large email list (for example, over 10,000 recipients) in Blackbaud Internet Solutions. To avoid this, the EmailUploadTimeout value now appears in the the web.config file and defaults to 120 seconds. However, your system administrator can adjust this limit. The new USP_EMAILLIST_CREATEUPLOADEMAILTABLE and USP_EMAILLIST_CREATEUPLOADEMAILTABLEINDEX stored procedures and the new IX_CONDITIONALCONTENTRECIPIENT_EMAILLISTUPLOADMASTERLISTID index have also been added to also help improve performance and avoid a timeout error. | 383880 | 37 | |
This fix improves performance for constituent merges. | 360300 | BB740380 | 37 |
This fix improves performance on the Revenue History tab of a constituent. | 352401 | BB743081 | 37 |
This fix improves performance on the Revenue Summary tab of a constituent record when there are many revenue transactions to include. | 350525 | BB747192 | 30 |
This fix improves performance on the Revenue Summary tab of a constituent record when there are many revenue transactions to include. | 345997 | 34 | |
This fix improves performance when calculating a constituent's donor constituency. The UFN_CONSTITUENT_ISDONOR function was rewritten to query the database more efficiently and return a value more quickly. | 303961 | 20 | |
This fix improves performance when querying and searching for a revenue record's lookup ID. | 310402 | BB742316 | 20 |
This fix improves speed and performance issues when accessing the Commit Multiple Batches page in Blackbaud CRM. | 372353 | BB748867 | 37 |
This fix improves the credit card authorization process with the Blackbaud Payment Service to help ensure that each transaction receives an authorization code or rejection message, as needed. | 324163 | BB745255 | 53 |
This fix improves the performance time in Blackbaud Internet Solutions and Blackbaud NetCommunity when users submit information on a payment form. The Payment 2.0 part now makes fewer external requests to Blackbaud Secure Payments so payment pages can load more quickly. | 320973 | BB743357 | 41 |
This fix includes credit card processing enhancements between CRM and the Blackbaud Payment Service. We improved polling between CRM and the Blackbaud Payment Service so that CRM can know when transaction processing starts for a batch. We capture additional details to the server’s Event Log during card processing. In addition, for improved tracking, credit card processing status and error messages in CRM are now more specific. | 346868 | BB746374 | 53 |
This fix is related to the fix for work item 406892. As noted in 406892, the API endpoints for custom parts with Blackbaud's secure payment page no longer clears the part's content when the "{content}" placeholder does not exist on the page. However, this fix provides a way for you to add "Visible=False" to the custom part's placeholder front end code to avoid exceptions when sending template updates for the secure page. This change applies to Blackbaud Internet Solutions. | 412171 | BB741522 | 47 |
This fix opens a committed batch that contains donations from Blackbaud Internet Solutions after you move the Blackbaud Internet Solutions database to a different server and do not encrypt data with new keys (for credit card and account numbers.) Previously, an error message appeared. Now, the committed batch opens with blank encrypted fields. | 337543 | BB744729 | 34 |
This fix prevents "1/1/0001" from displaying in the System Value column for a blank educational involvement date in a BBIS Profile Update Transaction Batch. Now, the cell correctly remains blank when there is no value for an educational involvement date. | 380160 | 37 | |
This fix prevents a constituent's email address from incorrectly appearing for another constituent in a Blackbaud CRM web transaction batch when you download a profile update from Blackbaud Internet Solutions. This occurred when the email address end date entered in batch came after the profile update transaction date. The USP_DATALIST_EMAILADDRESS stored procedure has been updated to resolve this issue. | 351825 | BB747558 | 37 |
This fix prevents an error when you send a test email to an individual recipient by entering the email address manually in the Test email field in Email, Messages. This error, introduced in 270970, occurred because the program did not check manually entered individual email addresses. This applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 322614 | BB745445 | 24 |
This fix prevents the 'UPDATE statement conflicted with the CHECK constraint' error message from possibly appearing when you attempt to commit a BBIS Event Registration Transaction batch that includes an event registration transaction with updated address information from your Blackbaud Internet Solutions website. To resolve this, the stored procedures USP_BBNC_COMMITPROFILEUPDATEADDRESS.xml and USP_COMMITPROFILEUPDATEADDRESSANY.xml have been updated. | 413289 | BB751668 | 55 |
This fix prevents timeout errors when you save or send a mass email from Blackbaud Internet Solutions and a website user submits a donation transaction at the same time. To avoid this, email and donation processes are redirected to different back end data tables to increase efficiency so all processes complete successfully. Also, an index has been added to the UpdateDate and BBNCMapId fields in the NetCommunityEmailJobRecipient table to increase performance for various processes. | 338079 | BB746641 | 31 |
This fix properly totals the amounts of split applications for revenue during the Membership contribution process so that members are upgraded into the correct membership levels. | 275189 | 28 | |
This fix provides a way for you to configure the "From" field for Blackbaud Friends Asking Friends fundraising messages so that registrants can send messages when their email address is from a Domain-based Message Authentication, Reporting, and Conformance (DMARC) compliant email provider, such as Yahoo! and Hotmail. To do this, your system administrator can update the following setting in the web.config file: <appSettings><add value="<Email address value here>" key ="BBCustomerMarketingEmailAddress"/></appsettings>. This change resolves problems that occurred because many DMARC compliant systems recently updated their policies to instruct other DMARC compliant systems to reject email when messages using their addresses did not originate from their servers. Now when you include an email address with your organization’s domain in the "From" field, the fundraising messages are accepted because they are sent from your organization. | 390806 | BB750182 | 41 |
This fix provides a way for you to eliminate an intermittent stack trace error if it appears when you create an email message for a Blackbaud Friends Asking Friends event. If the error occurs, it is possible for you to change the CMSEmail_SmallTimeout value in AppSettings of the web.config file. | 392447 | BB750314 | 55 |
This fix removes the check constraint error CK_EVENTREGISTRANTPAYMENT_VALIDAMOUNT when you commit a BBIS Event Registration Transaction Batch and the batch includes a registration overpayment for an event from your Blackbaud Internet Solutions website. Previously, the error occurred when the constituent’s account balance was paid in full, and the overpayment caused a negative amount due. Now, the batch commitment can handle the overpayment and proceed without error. | 395218 | BB748072 | 53 |
This fix resolves a compatibility issue with Microsoft SQL Server 2012 and 2014 that caused errors to appear when you attempted to commit the Currency Exchange Rate Batch. | 429315 | 53 | |
This fix resolves a styling issue that appeared on mobile pages when users clicked the Blackbaud CRM Mobile back button. Previously, a blank blue bar was inserted on a page each time a user click the back button within the application. Now, a blue bar only appears for a page's header. | 378626 | 37 | |
This fix resolves an error in the screen where you specify export criteria for one-to-many fields in export definitions. The screen appears after you add a one-to-many field to an export definition. Previously, the error occurred when you chose the option to apply a filter to selected values and then attempted to specify a value. | 393023 | BB750371 | 40 |
This fix resolves an issue for Blackbaud Internet Solutions that was introduced in Service Pack 9. When you associate an Advanced Donation Form with a Payment 2.0 part, payment method validations have been restored so the payment processes successfully. To avoid further issues, it is possible you may need to update the HTML code for the Advanced Donation Form part if you are using improper HTML. As a result of this fix, the secure payment page template update process is now enabled for the Advanced Donation Form. | 435403 | BB752997 | 55 |
This fix resolves an issue for email addresses when a website user submits the User Interests Form part on your Blackbaud Internet Solutions website. Previously, the user's preferred email address changed to their previous email address after the transaction processed and appeared in batch in Blackbaud CRM. To prevent this, the program now matches the email address from the form with the user's preferred email address from the constituent record. | 382940 | 37 | |
This fix resolves an issue for read only Educational histories fields on the Profile Update form in Blackbaud Internet Solutions. Previously, website users could continue to edit these fields when the checkbox was cleared in the Edit column on the form to prevent users from changing data. Now, the form honors the checkbox status so the field remains read only and users cannot change data. | 387297 | 53 | |
This fix resolves an issue for website users searching by "Organization name" on a Directory web page when you configure the Directory part to include "Both Organizations and Individuals" under Records to Include and you include the Organization name field in the Search Form Fields box. Previously in this scenario, the search returned results for individual constituents not associated with an organization. Now, when you include this field in the box, only organizations appear in the results display window, when you include the Name field (under Bio) in the box, only individuals appear in the results, and when you include both fields in the box, the search returns results for both organization and individual constituents. This fix applies to Blackbaud Internet Solutions website and Blackbaud NetCommunity. | 383781 | 53 | |
This fix resolves an issue introduced in patch 39 that occurred when users accessed tabs in the ClickOnce version of the program which included dashboard sections. Previously, an error message appeared instead of the data. | 395489 | BB750649 | 41 |
This fix resolves an issue introduced in service pack 5 that changed the behavior of code table parameter fields in user-defined smart queries. The code table parameter fields filtered data as if they contained a database ID, and caused incorrect query results. | 360470 | BB748181 | 37 |
This fix resolves an issue introduced in Service Pack 7 that caused an object reference error in Blackbaud NetCommunity when you attempted to view parts and pages that include mailing address fields. Now when you attempt to view parts and pages with address fields, the error no longer appears. | 423165 | N/A - datafix request | 51 |
This fix resolves an issue introduced in Service Pack 7 that caused an object reference error in Blackbaud NetCommunity when you attempted to view parts and pages that include mailing address fields. Now when you attempt to view parts and pages with address fields, the error no longer appears. | 419329 | N/A - datafix request | 53 |
This fix resolves an issue so that users can now return to the previous page successfully in CoSign authenticated environments when they click the back button within Blackbaud CRM Mobile. Previously, the button did not consistently return to previous pages. | 398173 | BB748622 | 53 |
This fix resolves an issue so that users now return to the previous page successfully in Webkit-based browsers when they click a back button within Blackbaud CRM Mobile. Previously, the button did not consistently return to previous pages. This fix only applies to the back button within the application. We recommended that users select the application's back button rather than the browser’s back button when navigating in Blackbaud CRM Mobile. | 368811 | BB748622 | 37 |
This fix resolves an issue that caused a timeout to occur when a user was active in one tab of a browser and had another, inactive tab open in the background. | 403774 | 53 | |
This fix resolves an issue that caused an error to appear when adjusting posted revenue from the Edit posted payment screen. The issue occurred when the adjustment's post status was set to "Do not post" and a benefit was associated with the payment. | 388595 | BB750031 | 53 |
This fix resolves an issue that caused an error to appear when batches that included direct debit payment transactions were committed. The error occurred when the payments were made by users who were logged into Blackbaud Internet Solutions websites. | 400987 | 41 | |
This fix resolves an issue that caused an error to appear when certain profile update and donation transactions were downloaded from Blackbaud Internet Solutions websites. The issue occurred when the transactions included blank values for some of the fields. | 382721 | BB749537 | 41 |
This fix resolves an issue that caused an import selection process to fail when the CSV file included multiple alternate IDs that referenced a single record. Now, the process recognizes the issue as an exception and includes a message to explain the import failures in the downloadable exceptions file. | 372573 | BB748504 | 37 |
This fix resolves an issue that caused certain report models to return incorrect data. The issue occurred when the models were generated from query views that contained multiple fields with the same name in the database and those fields referenced the same database tables, such as code tables, simple data lists, selections, and search lists. For example, if a record included multiple attributes that all referenced the same code table, the attribute fields on the query view were all named VALUE in the database. The fields now include unique database names. To apply the change to existing report models, you must regenerate them. | 372235 | BB748818 | 53 |
This fix resolves an issue that caused entire sections of Blackbaud Internet Solutions communication preferences forms to not appear when one of the field options was disabled for a user. Now, only the disabled option does not appear. For example, if an option for an appeal field is "post" and a user's record includes the "do not mail option," "post" does not appear as an option for the field when the user accesses the form. | 410869 | 53 | |
This fix resolves an issue that caused the Gift Aid refresh process to not include revenue in its calculations when a Yes declaration was added to a constituent with an existing Gift Aid eligible revenue record. | 436303 | BB752986 | 55 |
This fix resolves an issue that caused the program to double count the tax claim amount for fields in the ad-hoc query Revenue > Gift Aid node. The correct amounts now appear for the Gross Amount, Gross Amount (transaction currency), Gross Amount (organization currency), Potential Gross Amount, Potential Gross Amount (transaction currency), and Potential Gross Amount (organization currency) fields. | 411674 | 53 | |
This fix resolves an issue that caused the program to insert an extra carriage return in label templates when you used the Word document merge functionality from the webshell version of Blackbaud CRM. | 383004 | BB743110 | 41 |
This fix resolves an issue that caused the direct debit payment merge fields to not appear on Payment 2.0 part confirmation screens for website users. | 409657 | 49 | |
This fix resolves an issue that occurred for specific data lists created from ad-hoc queries. If the query included an output field with a list of known values such as “Installment frequency,” the field values used similar words such as “Annually” and “Semi-annually,” and the output field was included as a data list filter option with “Equal To” or “Not Equal To” as filter operators, then the list returned incorrect results when you used the filter option. Results with similar values to the one you used as the filter appeared. For example, if the data list filter operator for "Installment frequency" was "Equal To" and you selected to filter the data list with the value of "Annually," the results included annual and semi-annual payments. This fix resolves the issue for new data lists. | 356383 | BB748008 | 37 |
This fix resolves an issue that occurred in the duplicate resolution screen when individual, organizational, or constituent batch records potentially matched existing records in the database. Previously, the program did not always display the correct contact information for potential duplicate records when the existing records included multiple addresses, email addresses, or phone numbers. Now when new contact details do not match existing details, the program displays the primary contact information. When new contact details match existing details, the program displays the existing information. | 398766 | 53 | |
This fix resolves an issue that occurred in the webshell version of Blackbaud CRM 3.0 when custom query views included field names with backslashes. Previously, when you used the fields as filters in ad-hoc queries, an error message appeared. | 367588 | BB748528 | 37 |
This fix resolves an issue that occurred when existing import file templates were edited from the Import page in Administration. Previously, you could not change existing field mappings or map additional fields. | 351843 | BB747561 | 41 |
This fix resolves an issue that occurred when a query included a selection that was later renamed. Previously, the query would sometimes experience performance issues when you attempted to generate results. In rare cases, you may need to open and re-save a query that includes a selection in order to apply the fix. | 329584 | BB745937 | 37 |
This fix resolves an issue that occurred with Add, Edit, and View forms in Blackbaud CRM Mobile. Previously, when the forms included extensions, the extensions were not formatted for mobile devices. You can add extensions to data forms from Administration or with the Infinity SDK. | 352051 | BB747596 | 37 |
This fix resolves an issue that prevented group assignments to system roles with LDAP queries in the webshell version of the program. System role group assignments are available from the Groups tab on the System roles page in Administration. | 407773 | BB751262 | 53 |
This fix resolves an issue that sometimes caused an error message to appear on the Import page in Administration. The issue occurred during recurring import processes when the program was configured to import files from a SFTP server and the file names included wildcard characters. | 384869 | BB749722 | 53 |
This fix resolves an issue that sometimes caused an error to appear when the program used the UFN_BUSINESSPROCESSSTATUS_STANDARDDATALISTVALUES_ROWSTORETURNSTARTEDDATE function. The function is used from the History tab of business processes pages throughout the program and is available from the Infinity SDK for data lists and other customizations. | 370728 | 53 | |
This fix resolves an issue that sporadically caused an error when you uploaded files to the smart client version of the program. Previously, persistent cookies were not distributed in load balanced environments. | 355909 | 38 | |
This fix resolves an issue when editing a pledge. Previously, if you edited a pledge and changed the pledge amount, any benefits associated with the pledge were automatically removed from the Edit pledge screen. | 358262 | 37 | |
This fix resolves an issue which caused an error to appear when you edited a payment and applied it to an auction purchase. The error occurred when the auction item was for an account system other than "System Generated Account System." | 389748 | BB751049 | 45 |
This fix resolves an issue which occurs when you add a matching gift claim to a payment which is associated with a solicitor. Previously, the user would be unable to save the "Add a matching gift claim" screen and would receive an error. | 368004 | BB748599 | 37 |
This fix resolves an issue with address field autopopulation on donation pages when website users accessed the pages from Blackbaud Internet Solutions email links. The issue occurred when the "Allow users to select a different address" option was not selected in the Administration, Sites and Settings, Address Options section of Blackbaud Internet Solutions. Previously, the website treated these users as though they were anonymous and displayed blank values for the address fields. | 317753 | BB744243 | 41 |
This fix resolves an issue with Campaign Goal KPIs. Previously, the date range was not properly considered when a campaign hierarchy existed. The KPIs incorrectly included revenue outside the specified date range. | 356283 | BB746785 | 37 |
This fix resolves an issue with constituent attribute code tables that accept multiple values and appear on Profile Update forms. Previously, when Blackbaud Internet Solutions website users updated values, the changes did not download to Blackbaud CRM. | 392260 | 41 | |
This fix resolves an issue with payments to a pledge which include a sold transaction of property, stock, or gift-in-kind. Previously, the GL account on the sold transaction was not updated properly when the designation was changed and the designation included a mapping segment. The issue occurred when editing a pledge with payments that were either posted or not posted. Now, the GL distributions will be updated correctly when editing the pledge. | 340007 | BB745587 | 34 |
This fix resolves an issue with the "Constituent by last revenue" smart query. Previously, the revenue query specified in the smart query was not applied to the smart query results, which caused incorrect results in the smart query output. | 354125 | BB747374 | 34 |
This fix resolves an issue with the "RE7 Gift Splits" smart field failing to process with RE7 payments of constituents soft credited for payments. You must re-deploy the Datamart to utilize this fix. | 418642 | BB751983 | 53 |
This fix resolves an issue with the Campaign Priority Report. Previously, the "Total Raised" amount for campaign subpriorities did not include write-off amounts correctly. | 359084 | 37 | |
This fix resolves an issue with the Campaign Priority Report. Previously, the "Total Raised" amount was calculated incorrectly. | 359080 | 37 | |
This fix resolves an issue with the Directory part results on your Blackbaud Internet Solutions website when you select to include the "Education History, Education institution (Affiliated)" field in the Listing Fields box on the part and the Academic Catalog is turned off in Blackbaud CRM. Previously, this prevented Directory results from appearing on the web page because the search attempted to include unaffiliated institutions for the field. Now, the search has been updated to search for and display affiliated institutions only. | 384268 | 41 | |
This fix resolves an issue with the Opportunity field on the Edit posted pledge screen. Previously you were able to select an opportunity but unable to remove it from the posted pledge. Now you are able to select the blank option in this field or manually delete the text to remove the opportunity. | 326931 | BB745620 | 28 |
This fix resolves an issue with the Opportunity field on the Edit posted pledge screen. Previously, you were able to change the opportunity on the Edit posted pledge screen, but the updated opportunity was not actually saved to the pledge. | 340072 | 34 | |
This fix resolves an issue with the Top Fundraisers list when you use Blackbaud Friends Asking Friends. Previously, when a top donation leader used existing credentials to register for a second event and additionally made a second qualifying donation for recognition in the Top Fundraisers list, the donor's name appeared two times in the list. This occurred because the program did not fully specify which event the list was for at every fundraising level. To resolve this, USP_DATALIST_FAFTOPFUNDRAISER has been updated so the top donor's name only appears once in the list. | 385999 | BB749794 | 41 |
This fix resolves an issue that occurred when website users in the United Kingdom attempted to submit direct debit payments. Previously, an error message appeared for payments from accounts registered to the Royal Bank of Scotland, Barclays, and Lloyds. Please note this fix does not validate sort code and account number combinations for pending payments that appear in the Transaction Manger part. | 406615 | BB749540 | 49 |
This fix resolves errors that occurred when clients with SQL Server 2012 attempted to install the program or upgrade to a newer version. | 410011 | BB751414 | 53 |
This fix resolves insufficient memory errors that sometimes appeared when you used the Word document merge functionality from the webshell version of Blackbaud CRM. | 336932 | BB746450 | 41 |
This fix resolves issues that occurred in Shell Design under Administration when output fields in user-defined data lists were added or edited. Previously, when you modified data list ad-hoc queries, the web shell stopped responding or the changes would not save. The issues occurred when you clicked Save and did not select the Set save options tab. | 372372 | BB732068 | 37 |
This fix resolves an issue that caused an error to appear when certain filters were applied to user-defined data lists. For example, the issue occurred when the ad-hoc query used to create the data list included the "Category" and "Subcategory" fields from the Steps/Interactions source view and those fields were also used as filters. To apply this change to existing data lists, edit and save them in Shell Design under Administration, Application. | 423241 | BB752212 | 55 |
This fix updates the error message you receive when you try to merge two constituents with identical addresses. This error occurs when your merge configuration is set to exclude duplicate addresses and delete source constituents, and the source constituent's identical address is in a Constituent Address Update Batch. The new error message clarifies the cause of the error. | 334644 | BB730454 | 34 |
To avoid an "Unable to save batch row" error message in Blackbaud CRM for a donation transaction from Blackbaud Internet Solutions, the download process now attempts to use the designation ID from the Donation Form part when it cannot find the backoffice ID for the donation. | 326231 | BB745517 | 28 |
To help align lost features from the deprecated Profile Form part, the Required property has changed for a Yes/No constituent attribute on a Profile Update Form in Blackbaud Internet Solutions. To require website users to select "Yes" or "No" for a constituent attribute, select Yes for the property. To eliminate the requirement for the attribute and to provide the options for users to select "Yes", "No", or a blank (or empty) value, select No for the property. This change helps prevent the possibility of the attribute inaccurately updating to "Yes" or "No" when a user submits a Profile Update Form. | 355323 | 37 | |
To help improve mass email performance when you send donation acknowledgements on the Donation Form part, the email processor now runs fewer processes at one time. This applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 270970 | BB740870 | 20 |
Tribute acknowledgee, corporate, and matching gifts that you download from Blackbaud Internet Solutions no longer require you to review a revenue note before you commit the Enhanced Revenue Batch. This change alters the way the program informs you about revenue notes. It alerts you that a note exists, but you can commit the batch successfully without manual action to clear the batch message. Previously, tribute, corporate, and matching gifts created an exception on the batch row that prompted you to manually clear the revenue note before you committed the batch, which slowed down batch processes. | 298807 | BB742772 | 17 |
Update BBDW_FACT_FINANCIALTRANSACTION and BBDW_FACT_FINANCIALTRANSACTIONLINEITEM packages to address a problem with having duplicate records when there are two application users with the same user name. BBDW will need to be redeployed and complete an incremental refresh for this to take effect. | 297536 | BB742546 | 15 |
Update Campaign Recognition Credit Report and Campaign Priority Report for issue where those reports wouldn't load. | 276373 | 15 | |
Update gift fee GL distributions on a payment when changing designations with the Edit payment or Edit posted payment task. | 280019 | 15 | |
Update gift fee GL distributions when changing designations on a posted payment from the Edit screen on the Details tab. | 279971 | 15 | |
Update Gift fee GL distributions when waiving a posted gift fee. | 279667 | 15 | |
Update GL distributions for applications on matching gift claim payments when applications are changed. | 281196 | BB741760 | 15 |
Update Revenue Update Batch in the webshell version of the program to prompt for resetting recognition credits when you update a payment amount whether or not there are existing recognition credits. | 276382 | 15 | |
Update stewardship plan recurring steps to copy plan participants when creating the next step in the recurrence. | 276375 | BB738998 | 15 |
Update the Bulk Assign Prospects screen to not load all unassigned prospects when the fundraiser field is cleared in order to prevent "out of memory" error message. | 277960 | BB741479 | 15 |
Update the SAR merge revision to handle null finder numbers. | 266062 | BB740225 | 1 |
Update the user agent when requesting an RSS feed. | 273381 | BB741060 | 7 |
Updated Event Registration Form client-side interaction script. | 268467 | 3 | |
Updated the annotation processor to handle records without a valid ID mapping. | 277818 | 10 | |
Updated the configurability of timeout periods for Email List refresh. | 273757 | BB741107 | 11 |
Updated the notification and annotation processors to handle non-guid ids. | 275852 | 9 | |
Updated transaction assignments for Funds. | 275179 | BB741267 | 11 |
Updated transaction processing for events to apply registration fees to the participants. | 270818 | 5 | |
Updating BBDW_REPORTSERVERCREDENTIALS package to address a problem with creating reports from ad-hoc queries based on BBDW. BBDW will need to be redeployed and complete an incremental refresh for this to take effect. | 276242 | 13 | |
Updating enhanced revenue batch to support notifications with the new constituent record type. | 277489 | 13 | |
Updating the marketing constituent package to better handle international dates. BBDW will need to be redeployed and complete an incremental refresh for this to take effect. | 266441 | BB740027 | 2 |
Validation of an enhanced revenue batch will no longer throw an incorrect error claiming that an account number doesn't exist for a payment to planned gift. | 317383 | BB743549 | 20 |
Volunteer job assignments now display correctly when you attempt to schedule multiple days of volunteer job assignments when using a locale with a day-month-year date format. To schedule multiple days of volunteer job assignments, click Schedule under Tasks from the volunteer record and then click Schedule multiple days. | 316870 | BB743911 | 24 |
Volunteer job match details now display correctly when you attempt to schedule jobs for a volunteer when using a locale with a day-month-year date format. To schedule jobs and view match details for a volunteer, click Schedule under Tasks from the volunteer record. | 316867 | BB743907 | 24 |
We fixed a performance issue that caused the Appeal performance report to time out when you selected an appeal. | 388607 | BB741153 | 41 |
We fixed a performance issue that occurred when you selected Unmark for re-receipt for a process that included a large number of consolidated revenue marked for re-receipt. The receipt process no longer times out. | 371649 | BB748813 | 37 |
We fixed an issue that caused the "Constituent lifetime gifts on file" and the "Constituent single gift consecutive year donors" smart fields to hang during refresh. | 397490 | BB750607 | 41 |
We fixed an issue that caused the Constituent Lifetime Gifts on File smart field to hang during refresh. | 379378 | BB749288 | 41 |
We fixed an issue that occurred after you deleted a Remove members process for a segment. When members were added back to the segment, the constituent segment table did not re-populate with constituent information which caused finder numbers to be invalid. The segment table now re-populates correctly. | 375886 | BB748647 | 37 |
We fixed an issue that occurred when a constituent donated through Blackbaud Internet Solutions and entered a finder number that did not match the constituent. During batch validation, the program detected the mismatch and did not save the finder number, but still validated the gift. The program now provides a validation message that says "The constituent does not match the finder number" and you must remove the finder number or update the constituent before you can commit the batch. | 402827 | BB750974 | 53 |
We fixed an issue with the Appeal Performance report. You no longer receive this error when an appeal includes a pledge payment without appeal information: Error: An error has occurred during report processing. (rsProcessingAborted) Query execution failed for dataset 'AppealPerformanceByMailing'. (rsErrorExecutingCommand). | 414551 | BB751751 | 53 |
We have improved the credit card tokenization process used in batch through better communication with the Blackbaud Payment Service. We have also improved error handling, as well as the status and error messages displayed when the credit card tokenization process encounters errors, whether on batch row auto-save or any other time a batch is saved. | 385486 | BB740136 | 41 |
We've added a "show inactive" filter to the marketing selections list and we've used that filter to hide inactive selections on the "create multiple selections" form. Clients with selections that are not useful to the "create multiple segments" functionality can mark them inactive to improve the performance of that form. | 266427 | BB740424 | 13 |
We've made changes to improve performance when processing joint name formats where the first name that appears is determined using a selection. It is still highly recommended that a static, rather than a dynamic, selection be used for this purpose. | 304644 | BB741731 | 20 |
We've restored the ability to use a selection to define the transactions included when generating consolidated receipts. | 303500 | BB742970 | 17 |
When a change is made to a template or page, the updatedate in the SitePages table no longer updates for all templates and pages on every website in the database. It now only updates for the changed template and page on the on the impacted site. This fix improves performance for style sheet, layout, template, and page updates to the Blackbaud secure payment page because it uses updatedate to determine the latest changes to apply to the secure payment page. This applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 328389 | 21 | |
When a finder file is imported, exceptions can occur. Previously, it was not possible to download the exception file if no records were processed successfully. This has been fixed. | 316800 | 20 | |
When a marketing effort was exported, seeds were sometimes missing information about segments and packages in the output. To fix this issue, seeds are now matched differently with segments when the output is generated. | 323099 | BB744889 | 24 |
When a marketing effort was sent as email from Blackbaud Internet Solutions, the program sometimes excluded constituents if the marketing effort included multiple segments with different packages that used the same email message and the number of recipients exceeded the chunk size defined by the web config (5000 by default). This issue no longer occurs. | 379646 | BB748140 | 37 |
When a non-US website user submits a Profile Update form on your Blackbaud Internet Solutions website, this fix prevents unchanged Education - Degree data from showing as changed when you view the transaction in a BBIS Profile Update Transaction Batch in Blackbaud CRM. To correct this issue, a standard date format is now used for the education date fields on the form. | 331421 | 37 | |
When a participant user imports contacts from Google on a Blackbaud Friends Asking Friends website, Google no longer prompts the user with intermittent warning messages about fraudulent access to user accounts. Previously the program authenticated Google accounts by sending credentials over the Internet. This fix changes the authentication so that it is now handled by Google servers only. | 304689 | BB743236 | 19 |
When a redirect URL link in an email contains HTML fragments for client side routing frameworks (for example, AngularJS), Blackbaud Internet Solutions now correctly appends query string parameters after the HTML fragment. Without this, it was possible for donation transactions submitted via the link in the email to process without its associated finder number, appeal, and marketing effort information. | 395552 | 53 | |
When a searchlist is launched from a Task and no security context is provided, then use the task as the security context. This is how Click-Once behaved. This supports just granting the user rights to the task and not the search list directly. | 290321 | BB733421 | 14 |
When a website user changes a solicit code preference on the Communications Preferences form on your Blackbaud Internet Solutions website, a transaction for it no longer inadvertently appears in batch in Blackbaud CRM; it now directly defaults on the constituent record. This occurred when the user changed a solicit code and then submitted a profile update transaction in the same session without logging out of your website. | 384340 | BB749672 | 53 |
When a website user changes existing data in the Position field for educational involvements to blank (or empty) on a Profile Update form on your Blackbaud Internet Solutions website, an error no longer appears in BBIS Profile Update Transaction Batch that prevents you from processing the empty Position field. This fix allows you to process educational involvement data without a position defined so you can commit the batch. | 356775 | 37 | |
When a website user is redirected after submitting a secure payment transaction on your Blackbaud Internet Solutions website, an extra "?" no longer appears in the URL query string. This occurred when you use API endpoints that allow custom parts to use Blackbaud's secure payment page. Depending on your API code, be aware you may experience issues after applying this fix. For example, if you added code to expect the extra "?," you need to remove it. | 350313 | 53 | |
When a website user navigates from your email appeal to an online payment form in Blackbaud Internet Solutions and leaves the Appeal field blank, the appeal now automatically downloads to the revenue record in Blackbaud CRM to track the donation amount and conversion details for the appeal. | 224009 | 34 | |
When a website user submits a transaction on the User Login part on your Blackbaud Internet Solutions website and leaves the "Gender" field blank, "Unknown" now processes to the Constituent Update Batch in Blackbaud CRM. This corrects an issue with "Female" incorrectly processing to the batch in CRM when the field is left blank. | 306329 | 20 | |
When adding a test segment to a marketing effort that uses a source code with a user-defined value, overriding the marketing effort's setting for that value will no longer result in an error when saving the test segment. | 310180 | BB743411 | 20 |
When an enhanced revenue batch included a record with the same finder number as an imported list member, during validation you received an exception for the matching records. After you resolved the matches on the Possible duplicate matches screen and then validated again, the records still received an exception saying they were duplicates. This issue is fixed and the duplicate records should validate correctly after they are resolved. | 324721 | BB745348 | 37 |
When an event invitation process was run, the program included constituents with addresses marked "Do not send mail to this address" and the communication was added to their constituent records. This issue no longer occurs. | 352650 | BB747682 | 37 |
When Blackbaud CRM constituents register on your Blackbaud Internet Solutions website, existing interests on constituent records are no longer overwritten by interests selected on your site. To correct this issue, the Constituent Update Batch now only adds interests from your website to constituent records so existing interests continue to appear on them after the transaction process. | 347432 | BB715901 | 30 |
When Blackbaud Friends Asking Friends participants enter offline gifts from their participant headquarters, the gifts are now mapped to the correct geographical designations they select when “Designation by geography” is enabled for the account. Previously, the program assigned the event’s default designation. To resolve this issue, the stored procedure USP_DATAFORMTEMPLATE_ADD_REVENUEOFFLINEDONATION was updated to calculate the designation correctly. | 382968 | 53 | |
When clearing the results for a re-receipt process that included a large number of revenue records, the program would sometimes time out. The underlying performance issue was fixed and the program no longer times out when you clear results. | 346896 | BB746957 | 37 |
When configuring an email message in BBDM, entering an email address into the "Failure notification" field should result in failure notification emails being generated and sent to that address when an email job using that message is sent. This was not working, and has been addressed for current and future BBDM email messages with a "Failure notificiation" email address. | 291000 | BB742440 | 20 |
When downloading web transactions into an enhanced revenue batch in Blackbaud CRM, an error occurred for sponsorship payment transactions from Blackbaud Internet Solutions. With this fix, the error no longer displays and the BBIS sponsorship payment transactions download successfully. | 349857 | BB747334 | 31 |
When editing HTML in the web shell -- for example, when adding or editing an email message in the Marketing and Communications area -- Preview and Print buttons will now be available. Preview will display the HTML content in its own dialog, and Print will enable you to send that content to a printer. | 267305 | BB740568 | 20 |
When exporting information for a large marketing effort, the marketing effort export process ended abruptly after running for numerous hours. With this fix, the marketing effort export process no longer times out. | 427196 | BB752422 | 53 |
When merging output from a marketing effort with multiple letters, the checkboxes allowing individual letters to be selected were not being respected in the click-once client. This has been fixed. | 324466 | BB745288 | 24 |
When merging output from a marketing effort with multiple letters, the checkboxes allowing individual letters to be selected were not being respected in the click-once client. This has been fixed. | 302114 | BB742983 | 24 |
When processing consolidated receipts using a custom output format, you no longer receive a status message of "Tokens not found." | 354140 | 34 | |
When resolving duplicate records in batch, fields should not have their value overwritten by data from the selected record. | 275945 | BB741049 | 9 |
When running a "per payment" receipt process with a Gift detail, Email gift detail, or Formatted mail gift detail output format, the program incorrectly receipted "consolidated" revenue instead of "per payment." This issue is fixed. | 370675 | 37 | |
When running pledge reminders using the "Formatted mail reminder output" output format, and more than 20 reminders were generated, and one of the designations appearing in the output was part of a hierarchy where the total number of characters making up the names of all of the designations in the hierarchy was greater than 100, the user would receive the error "string or binary data would be truncated...". This has been fixed. | 311001 | BB743506 | 20 |
When the receipt process used an export definition, it did not generate output for receipt fields. Also, export definitions were missing necessary receipt fields. To resolve these issues, we fixed the receipt process and updated the export definition fields. The Last receipt number and Last receipt date fields, previously found under the Revenue node in an export definition, are now hidden because they hindered the Revenue query view performance. Existing queries or exports that used these fields will still work correctly after you update. There is now a Receipts node found under Revenue that includes these nodes: All Receipts, Most Recent Receipt, Original Receipt, and Previous Receipt. For each of these nodes, you can select these fields: Date, Number, Process date, Receipt stack short name, and Unique receipt number (Receipt stack short name plus Number). - All Receipts: Includes all receipts for a given transaction. This is a one-to-many field that provides all receipts generated for the transaction. - Most Recent Receipt: Includes the most recent receipt generated for the transaction. To recreate the Last receipt number and Last receipt date fields, select the Number and Date fields for this node. - Original Receipt: Includes the first receipt generated for the transaction. This value is the same as Most Recent Receipt if the transaction has only one receipt. - Previous Receipt: Includes the receipt prior to the most recent receipt. This value is blank if the transaction has only one receipt. | 324470 | BB738713 | 28 |
When the same letter was associated with a gift twice with different acknowledgees. If those acknowledgees were identified as duplicates, they would not merge properly. To fix this issue, the program now deletes one of the letters from the gift before it processes the constituent merge. If one of the letters is acknowledged and the other is not, the program deletes the one that is not acknowledged. | 347665 | BB747028 | 37 |
When two constituents are linked to two CMS accounts for Blackbaud Internet Solutions and you merge the two constituents to one in Blackbaud CRM, the oldest CMS account is now deleted from the database. This avoids duplicate emails to the constituent after the merge. | 303573 | BB741135 | 20 |
When website users import Gmail contacts on a Blackbaud Friends Asking Friends participant website, the program now uses a secure "https" URL to import the information. Previously, the program used a "http" URL that caused an "unexpected result" error after a Google API update to require "https." | 373789 | BB748981 | 36 |
When you add a membership, you can now hover over items in the Add a membership field to see an expanded description which includes information such as the level and the expiration or cancellation date. | 267622 | BB738999 | 13 |
When you create a marketing effort from a marketing plan that includes segment summaries with packages, if you add segment groups to the effort's segment summaries, an object reference error no longer occurs. | 281932 | BB741960 | 15 |
When you create a marketing effort from a marketing plan that includes segment summaries, if you run calculations and then select "Exclude from effort but show counts" for a segment included in the segment summary, a "Value cannot be null" error no longer occurs. | 282352 | BB741981 | 15 |
When you create an email message in Blackbaud Direct Marketing, you must insert a special page link to a User Email Preferences Form and Privacy page on your website. Previously when you used the "Special page" field to select a page, all types of special pages (Privacy page, Login page, Email preferences page, etc.) appeared in the drop-down list. Now there is an additional field that allows you to select which type of special page you want to choose from. Pages are also listed alphabetically to make them easier to find. | 330716 | BB745997 | 37 |
When you design an email message in Blackbaud Internet Solutions and include the "Preferred email" merge field, the correct email address now displays when the message is received. The merge field previously displayed the first email address added on the constituent record in Blackbaud CRM, even when it was not selected as the primary email address. | 371265 | BB748805 | 53 |
When you download a profile update transaction for a United Kingdom website user, UK addresses that were not changed no longer appear as changed in the BBIS Profile Update Transaction Batch in Blackbaud CRM. This occurred when the County field was populated, even though the user did not select a different county. Note, this fix does not resolve 374156 for UK business addresses with county information. | 372735 | 37 | |
When you download a transaction in Blackbaud CRM that generates from a pledge payment on the Transaction Manager part on your Blackbaud Internet Solutions website, an "Unable to save batch row 1. Verify that the field SPLITS is present in the batch template and that the value for the field is valid" message no longer appears on the Failed transactions tab. This occurred because the receipt amount for the payment did not process to the batch in Blackbaud CRM. Now, the receipt amount processes to the batch so the transaction processes successfully. | 352467 | 34 | |
When you download constituent attributes with a Yes\No value from a Profile Update form on your Blackbaud Internet Solutions website into a BBIS Profile Update Transaction Batch, the program now recognizes and displays Yes\No values. Previously, these appeared as True\False in batch and added unnecessary updates to the Constituent attributes tab. | 371064 | 37 | |
When you edit the amount of a payment using Edit payment under Tasks and the payment contains gift fees, you are now prompted to update the gift fee amount. | 279666 | 15 | |
When you edited a list segment, if you attempted to select a different list in the List field, the dropdown incorrectly loaded lists with a different base currency than the current segment. This issue is fixed and the List field now loads lists with the same base currency. | 345140 | 34 | |
When you enter text for opt-out emails for EmailFinder, you receive an error when the email text exceeds the space limit allowed. With this fix, you can now see the number of remaining available characters as you enter your message. If you need to include a longer message than the space limitations allow, please contact Blackbaud Data Enrichment Services. | 417000 | BB751637 | 53 |
When you export an ad-hoc query to .csv or Excel format, fields are now formatted correctly if you use Dutch regional settings. Previously, these exports had formatting problems in Dutch. | 346816 | 34 | |
When you export an ad-hoc query to .csv or Excel format, fields are now formatted correctly if you use Dutch regional settings. Previously, these exports had formatting problems in Dutch. | 328417 | BB743921 | 24 |
When you open a multi-level event from the Event Search screen, you will now see the multi-level event summary page instead of main event page for the first event. This worked correctly in the ClickOnce version of the program. | 317219 | BB741761 | 24 |
When you process a signup transaction from Blackbaud Internet Solutions to Blackbaud CRM, phone and email address data with the same type (for example, Home) now appears in the signup transaction batch and successfully downloads to the constituent record. Previously, the email address did not appear in the batch and did not process to the record. | 405615 | BB751093 | 53 |
When you process an anonymous gift from Blackbaud Internet Solutions to an Enhanced Revenue Batch in Blackbaud CRM, the "Gives anonymously" checkbox on the donor's constituent record no longer clears. This fix ensures the checkbox is not cleared on the constituent record, but does select the "Payment is anonymous" checkbox on the revenue record. To resolve this, the stored procedure USP_BBNC_CONSTITBIODATA has been updated. | 376947 | BB749150 | 53 |
When you upgraded from Blackbaud CRM and Blackbaud Internet Solutions version 2.9 to 3.0, constituent queries that filtered on the "Community Member" node no longer worked properly because that node was renamed to "Online Information" in version 3.0. This fix automatically replaces "Community Member" with "Online Information" in your existing queries so they will run correctly again. | 319276 | BB744398 | 24 |
When you use a Blackbaud Internet Solutions Weblog part on a web page, this fix adds back formatting options that previously appeared on the part. On the HTML editor Formatting tab, these options include Find and replace, Format (e.g., Paragraph, Address, Preformatted Heading 1), and Remove formatting. Note: We recommend you test the part's display on a web page to make sure the page layout is wide enough for these options to appear. | 346863 | BB746226 | 34 |
When you use Appeal Record to query a list of constituents with appeals on their Communications tab, query results now include constituents who received an appeal when its record was created in Blackbaud CRM and when its record was created in Blackbaud Internet Solutions. Previously, the program only returned a list of constituents who received the appeal when the record was added in Blackbaud CRM. To resolve this, the program now pulls data from the NETCOMMUNITYEMAILJOBRECIPIENT table in the back end, in addition to the CONSTITUENTAPPEAL table, so appeal records added in Blackbaud Internet Solutions are also recognized. | 322860 | BB744962 | 28 |
When you use Blackbaud Direct Marketing, finder numbers for marketing efforts supplied by the URL parameter "efndnum" now appear for online donations in Enhanced Revenue Batch. Previously, finder numbers only appeared in batch when website users manually entered them in the Finder Number field on the donation web page. Now, finder numbers appear in batch regardless of its origin. | 320456 | BB744614 | 24 |
When you use Blackbaud Friends Asking Friends and enter an offline gift from Add New, Friends Asking Friends gift on the Home screen, the error message "Data could not be saved. Data validation error:CreditCardSecurityCodeIsRequired" no longer appears. This occurred after you entered the CSC digits and saved the credit card information. To resolve this issue, the payment code has been updated to include CSC code in its parameters. | 337533 | BB746510 | 37 |
When you use Blackbaud Friends Asking Friends to edit an event theme, your changes now save on the Design tab in the program and appear correctly on the web page. Previously, the changes reverted to the default design for some browsers (for example, Google Chrome and Mozilla Firefox.) To resolve this issue, JavaScript code has been updated to make the theme page browser agnostic. | 367777 | BB748563 | 41 |
When you use Blackbaud Friends Asking Friends, constituent merge performance has been improved by calculation updates for the event raised totals when you add, edit, or delete revenue recognitions. | 357446 | BB740380 | 37 |
When you use Blackbaud Friends Asking Friends, embedded YouTube videos on participant web pages now render as secure videos that use https when you use SSL ( Secure Sockets Layer. ) Previously, these rendered incorrectly as http. | 327496 | BB745660 | 37 |
When you use Blackbaud Friends Asking Friends, the call for the Add and Edit buttons to display the add and edit scheduled message windows has been updated on the Marketing tab. The previous call used window.showModalDialog to display the windows. This dialog is no longer an Internet browser standard and has been removed by all major browsers. | 426181 | BB752301 | 55 |
When you use Blackbaud Friends Asking Friends, the registration web page no longer freezes when a registrant attempts to submit an email address over 34 characters. To correct this issue, the regular expression validation for email addresses is now less complex and time consuming. | 326178 | BB745499 | 34 |
When you use Blackbaud Friends Asking Friends, this fix removes the Violation of UNIQUE KEY constraint error message that appeared when a website user attempted to log in using social media credentials. To resolve this, the program now stores the temporary name of the user as a dynamic name rather than a static one. | 363469 | BB748341 | 55 |
When you use Blackbaud Friends Asking Friends, this fix successfully displays the Story widget on mobile devices for viewing purposes only. This fix does not include the ability for participants to edit the widget from mobile devices. | 333241 | BB746235 | 34 |
When you use Blackbaud Internet Solutions and the Academic Catalog is off in Blackbaud CRM, this fix corrects an issue so the College/School and Department merge fields successfully display data on the Profile Display part web. Previously, the merge field data did not display on the web page. This issue was introduced in work item 379848 in Blackbaud 3.0 service pack 7. | 412337 | BB751436 | 53 |
When you use Blackbaud Internet Solutions and the Academic Catalog is off in Blackbaud CRM, this fix corrects an issue so the College/School and Department merge fields successfully display data on the Profile Display part web. Previously, the merge field data did not display on the web page. This issue was introduced in work item 379848 in Blackbaud 3.0 service pack 7. | 410196 | BB751436 | 47 |
When you use Blackbaud Internet Solutions, batch no longer requires a full date format (for example, mm/dd/yyyy) for the Date to, Date from, and Graduation dates for "Educational histories" and "Educational involvements" profile fields when these fields are not present on the form on your website, but data exists for the fields on the constituent record in Blackbaud CRM and uses a fuzzy date format (for example, mm/yyyy.) Previously in this scenario, these fields appeared in batch as changed because batch did not accept fuzzy dates for the fields and attempted to update and enter a full date. To resolve this, the DataForm types have been updated from Date to Fuzzy Date for the Profile Transaction Data Form. | 388581 | 53 | |
When you use Blackbaud Internet Solutions, the Date to, Date from, and Graduation dates for "Educational histories" and "Educational involvements" profile fields now accept fuzzy date entries (for example, mm/yyyy) in batch when you download profile transactions to Blackbaud CRM. Previously, batch only accepted full date formats (for example, mm/dd/yyyy) so these dates showed as changed because the program attempted to enter a full date. To resolve this, the DataForm types have been updated from Date to Fuzzy Date for the Profile Transaction Data Form. | 388802 | 53 | |
When you use Blackbaud Internet Solutions, the QAS "Find Address" link now displays correctly on a web page beside the Postcode field. Previously, this link appeared above the address fields on the page. | 347209 | BB746995 | 32 |
When you use Blackbaud Internet Solutions, this fix correctly removes phone information from the Profile Display part when the end date has passed on the constituent's record in Blackbaud CRM. To implement this fix, the stored procedure USP_BBNC_CONSTITPHONEOREMAIL has been updated. | 387149 | BB749855 | 53 |
When you use the Academic Catalog in Blackbaud CRM and integrate the data with a Profile Update Form in Blackbaud Internet Solutions, the College/School, Division, Department, Sub Department, and Degree type fields now display for affiliated schools on the profile update web page. Previously, Blackbaud Internet Solutions did not include affiliated school information. | 379848 | 37 | |
When you use the ClickOnce version of Blackbaud CRM 3.0, you no longer receive an "Unable to get value of the property" error message when you add or edit parameter sets for the following business processes: Credit Card Processing, Generate Payments Process, and Generate Direct Debit File Process. Note, the ClickOnce version of these add and edit forms do not support parameters for membership installment plans (introduced in Blackbaud 3.0, Service Pack 4). When a parameter set is created in WebUI using a membership installment plan, you cannot edit it in ClickOnce. If you do, some parts of the form are inaccessible. Additionally, we recommend you use the WebUI version of Blackbaud CRM 3.0 for the best user experience and to gain full functionality of these forms, including the new membership installment plan features. | 337952 | BB746589 | 28 |
When you use the deprecated Profile Form part in Blackbaud Internet Solutions, preferred email addresses marked as public now display on the Profile Display part for website users without Supervisor rights. Previously, public preferred email addresses only appeared for Supervisor users. | 358731 | 37 | |
When you use the deprecated Profile Form part in Blackbaud Internet Solutions, preferred email addresses marked as public now display on the Profile Display part for website users without Supervisor rights. Previously, public preferred email addresses only appeared for Supervisor users. | 358590 | 53 | |
When you use the QAS address service for United Kingdom addresses on your website, the addresses now correctly populate for Blackbaud NetCommunity and Blackbaud Internet Solutions. Work Item 347209 in patch 32 (for Blackbaud CRM and Blackbaud Internet Solutions) introduced this issue. In addition, the QAS "Find Address" link now displays correctly beside the Postcode field and after the Country field on a Blackbaud Internet Solutions web page. | 374782 | 37 | |
When you view and export an email recipient list to CSV from the Recipients tab in Email, Messages, the operation now completes faster. Also, to avoid a timeout error, the operation complete time has been increased from 30 to 60 seconds. This increase applies to all instances of PagedSQLReader.ExecuteDataTable for Blackbaud Internet Solutions and Blackbaud NetCommunity. | 311004 | BB742180 | 34 |
When you view the Revenue Summary and Revenue History tabs on a constituent record, the campaign filter now includes only campaigns the constituent has given to and, for context, the associated parent campaigns in the hierarchy. The campaign filter on the Recognition Summary and Recognition History tabs includes only campaigns the constituent has recognition credit for, along with the associated parent campaigns in the hierarchy. Previously, the campaign filter on these tabs included the complete campaign hierarchy even if the constituent did not give to those campaigns. | 327091 | 24 | |
With this fix you can now add an additional designation to a pledge that has posted payment(s). Prior to this, users would sometimes encounter the error message "The installment amount cannot be less than the applied amount." | 322869 | 24 | |
With this fix, duplicate constituent records which have revenue adjustments can now be merged successfully. Previously if the source constituent had any revenue adjustments, an error would occur and the constituents would not be merged. | 328693 | BB745808 | 28 |
With this fix, the last four digits in the BSB and Account number fields now display on the Confirmation page on your website. Previously, all digits were masked for these fields on the Confirmation page. This change applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 348914 | BB747217 | 53 |
With this fix, we implemented backend changes to allow certain database collations. Blank databases with these collations can be successfully updated to Blackbaud CRM 3.0. | 349542 | BB747282 | 34 |
With this fix, we implemented backend changes to allow certain database collations. Blank databases with these collations can be successfully updated to Blackbaud CRM 3.0. | 265647 | BB740358 | 34 |
With this fix, we implemented process improvements to ensure data displays more efficiently when viewing the history of a planned gift. | 339994 | BB745743 | 34 |
With this fix, we improved the performance of the Constituent Search by Lookup ID feature when accessed through an Enhanced Revenue Batch. The search performance is now consistent with the search performance of the Constituent Search by Name feature in a Revenue Update Batch. | 328378 | BB745294 | 53 |
With this fix, we made several backend changes to ensure that editing the Amount and Designation fields on a sponsorship recurring gift record does not change the application type. These changes also ensure that the designation on a sponsorship recurring gift record cannot be split. | 328760 | BB745830 | 24 |
With this fix, when searching for major giving prospects, you can now use the Constituency field on the Prospect Search screen to filter by constituency. | 352219 | BB747613 | 37 |
With this fix, when you edit the revenue category for a pledge, the appropriate adjustments for the pledge payment(s) are now created. Prior to this, editing the revenue category on the pledge would not create an adjustment for the posted payment(s) associated with the pledge. | 319785 | 24 | |
With this fix, you can now add revenue to a planned gift addition for a planned gift associated with a vehicle type of "Living trust." | 389301 | BB749501 | 53 |
Work item 310918 in Service Pack 4 introduced a technical change that requires you to select the credit card payment option for one-time gifts. Selecting direct debit payments is no longer an option. Related to that change, this fix prevents you from selecting a Donation Form that does not accept the credit card payment option for pledge payments when you create or edit a Transaction Manager. | 359140 | 37 | |
You can now import any memberships with installment plans, including those with irregular schedules, in the Membership Dues Batch. Previously, the only memberships with installment plans you could import were lifetime memberships with the default installment plan schedule. | 276601 | BB741271 | 24 |
You can now start an email job from a marketing effort export before the marketing effort is activated. | 319570 | 24 | |
You can now use CSS classes and styles within the HTML of a BBDM email message. | 330316 | 28 | |
You no longer receive an error when calculating segment counts for a marketing effort that uses an email package and includes "All qualifying constituents" for the Universe definition. | 336762 | BB746436 | 28 |