This service pack is cumulative. It includes all issues addressed in CRM 4.0 prior to Service Pack 9, as well as any new features and changes outlined below. When you integrate CRM and Blackbaud Internet Solutions, we recommend you make sure both applications are running the same version and service pack.
For information about all of the new features released in Blackbaud CRM 4.0, see the CRM 4.0 New Features Guide. The Service Pack New Features chapter of the guide contains information about features released in this Service Pack as well as previous Service Packs.
Note: For Service Pack 8 for Blackbaud CRM, all of the assemblies were rebuilt and have a new date stamp; therefore the Release Notes do not contain information about specific affected assemblies.
Note: The version number for this release changed from 4.0.163.0 to 4.0.166.0. There were no security-impacting changes with this release.
| Comment | Work Item | Location | Knowledgebase |
|---|---|---|---|
| Technical Change: This fix addresses an issue with the "Address Geocode" global change in Administration. Previously, you could receive the error “The geocode process could not be completed. The remote server returned an error: (503) Server Unavailable” due to how the program was contacting the geocoding service. With this change, the “Address Geocode” global change process is now more stable with fewer errors and unprocessed geocoded addresses. The change affects the Microsoft endpoint that is used to process the geocode information. With the endpoint change, the “Address Geocode” global change process now completes with far fewer issues, though the processing time has increased. Submitting fewer records in one global change process will help decrease the processing time. However, you can also still set up a job schedule for the “Address Geocode” global change process. You can also still add it to a queue to be processed overnight or weekly, as needed, to minimize impact during normal business hours. | 639991 | All assemblies |
|
| This fix addresses an error which could occur when geocoding an address. The issue could occur when adding or editing a single address and using the “Validate” button for the address or when geocoding multiple addresses by using the “Address Geocode” global change in Administration. The error occurred when an address contained symbols such as # which were not being handled correctly during the geocode process. | 635169 | All assemblies |
|
| New Feature: With this enhancement, when you add a payment toward an existing commitment in Enhanced Revenue Batch, the appeal associated with the commitment is now defaulted onto the payment’s row in batch. However, if you add an appeal for a payment to the batch row before you select the application, the appeal will not be changed. Also, if the batch template has a default appeal, the appeal from the template is used as the default. | 630049 | All assemblies |
|
| This fix addresses an issue with ad hoc constituent queries in the Blackbaud Data Warehouse. Previously, an error sometimes occurred when attempting to view the results of these queries which contained attribute categories and designations which referenced a code table filter field with a code table value that had already been deleted in Blackbaud CRM. | 628070 | All assemblies |
101415 |
| This fix addresses an issue which occurred when you upgraded and you had custom batch extensions. Previously, a revision error could occur when upgrading if the batch extensions included system fields. The error was due to an incorrect validation check. | 622798 | All assemblies |
101047 |
| This fix addresses an issue with site security and Enhanced Revenue Batch. Previously, you could receive the error “The current user does not have rights to use this feature in the context of this specific record” when adding a new constituent with a payment in Enhanced Revenue Batch. | 621880 | All assemblies |
67343 |
| This fix addresses several validation errors which occur with the Blackbaud Data Warehouse. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 621748 | All assemblies |
|
| This fix addresses an issue that could cause payment applications to be missing in some batches. Previously, when you opened an imported Enhanced Revenue Batch that included payments for pledges, the payment applications could be missing, even though the revenue ID had been entered correctly in the import. This only happened when the constituent on the pledge was different from the constituent on the payment. Now, when you open an imported ERB, payment applications are displayed correctly. | 619422 | All assemblies |
100771 |
| This fix addresses an issue with the currency symbol displayed for certain revenue goal information on the KPIs tab on the Information Library page. Previously, if the KPI was set up to use one currency such as USD on the Criteria tab and the computer’s or browser’s regional settings were set to something other than “en-US” such as “en-UK,” the incorrect currency symbol was displayed for the revenue goal amounts in the list. The goal amounts were not actually converted into the different currency. Now, the currency selected on the Criteria tab of the KPI is always used for that KPI. | 619191 | All assemblies |
100750 |
| This fix addresses an issue which was introduced in Blackbaud CRM 4.0 Service Pack 6. Previously, if you added a new constituent through Constituent Update Batch and then entered the same constituent information again in a second Constituent Update Batch, the duplicate checking did not work correctly to match the duplicate constituent. | 617227 | All assemblies |
100614 |
| This fix addresses an issue which was introduced in Blackbaud CRM 4.0 Service Pack 7. You could receive an error when running the ETL refresh process for the Blackbaud Data Warehouse if any constituent interactions from the CRM database had a status of “Canceled.” To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 616831 | All assemblies |
100576 |
| This fix addresses an issue with PeopleFinder batches in the Data Tune-Up section of Administration. Previously, United States of America addresses included in the PeopleFinder batch were sometimes mistakenly translated to other countries and states outside of the United States when the batches were committed, such as "Seattle, WA, United States" being changed to "Seattle, Western Australia, Australia." | 616827 | All assemblies |
|
| Technical Change: To enhance web browser security with Blackbaud CRM, we have added functionality for CRM to send down the "X-Frame-Options" header with the "sameorigin" value when responding to browser requests. We also strongly recommend you update your site’s web.config file to add an IIS custom headers configuration setting to the <system.webServer> section. For information about the setting, see KB101073. | 614185 | All assemblies |
101073 |
| To improve security, this fix blocks a user from entering JavaScript code in the User Name field on your website's sign up page. This change applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 613011 | All assemblies |
100307 |
| This fix resolves a currency conversion issue for the Blackbaud Internet Solutions Transaction Manager part. Previously, an error message occurred when the IIS culture setting was set to a non-US format. The part has now been updated to handle all currency types so the Transaction Manager part renders successfully on your website. | 612944 | All assemblies |
100302 |
| This fix removes the revision error “The ALTER TABLE statement conflicted with the CHECK constraint "CK_CMS_SESSIONVARIABLEBACKUP_TYPECODE" when upgrading from Blackbaud Internet Solutions 3.0 Service Pack 14 to Blackbaud Internet Solutions 4.0. This upgrade now completes successfully without error. | 612810 | All assemblies |
100280 |
| This fix addresses an issue with marketing efforts and source codes. Previously, source codes were being incremented incorrectly even when the “Automatically increment source code values during data entry” checkbox was not marked on the source code part. Marketing efforts with incorrect source code values can be manually corrected or can be recreated. | 612598 | All assemblies |
100263 |
| This fix addresses an issue inadvertently introduced in CRM 4.0 Service Pack 6 which caused campaign goal information to not be included in the output of a Campaign query even when those output fields were included in the query. | 610980 | All assemblies |
100115 |
| This fix addresses an issue where an error message could appear for Enhanced Revenue Batches that contained pledge installment payments created with the “Generate payments” process. The error “The total amount must be equal to the sum of the amounts applied to commitments” appeared if you increased the amount of the latest overdue installment to pay for any amount greater than the latest overdue installment amount and you tried to validate the batch. | 610407 | All assemblies |
100087 |
| New Feature: We have made some improvements to the performance and security of the AddressFinder and DeceasedRecordFinder processes in Data Tune-Up. On the main Data Tune-Up page in Administration, we have added a configuration task for “Finder settings.” You should contact Support to receive your new credentials to enter on the “Edit finder settings” screen. You will also need to enter some information about your organization. We have also separated each process into four separate steps, rather than three. Previously the first step created and submitted the file to Blackbaud for processing. Now the first step is to create the file and give you a record count of how many records are included. This is so that you can better manage and track your actual number of records submitted for processing against the number of records you have contracted with Blackbaud to process. Step two is when you submit your file to Blackbaud. Step two also alerts you as to how many records you are submitting to be processed; you may be charged if you submit more records than you have contracted with Blackbaud to process. The final two steps remain the same with the exception of the step number. In step three (formerly step two), you retrieve the processed file from Blackbaud. And in step four, the final step (formerly step three), you can update the records in your database. After you upgrade, you must enter the information for this new configuration task before you can run any existing or new AddressFinder or DeceasedRecordFinder processes. | 607223 | All assemblies |
|
| New Feature: To increase email efficiency in Blackbaud Internet Solutions, we have enhanced the send final email process to help make sure the correct group of recipients receive your intended email. Now, when you click Send final on an email message, a new Send Status tab appears for you to view the target lists, the number of recipients in each list, and when the lists were last refreshed. | 606163 | All assemblies |
|
| This fix addresses an issue with import and file mapping templates which was introduced in CRM 4.0 Service Pack 6. If the file mapping template did not collection fields mapped, an import process using the template would fail. | 602995 | All assemblies |
99447 |
| Technical Change: When you process an updated phone number from a Blackbaud Internet Solutions event web page to Blackbaud CRM, the updated start date for the number now adds to the constituent record. Previously, only the original start date appeared. To resolve this, the stored procedure "USP_BBNC_COMMITPROFILEUPDATEPHONE" has been updated in the back end. | 601272 | All assemblies |
99292 |
| This fix addresses an issue which occurred with unapplied matching gift payments in Enhanced Revenue Batch. Previously, you could manually add a recognition credit to an unapplied matching gift payment in the batch. However, even when you saved the batch, if you reopened or committed the batch, the recognition credit you created manually for the payment was removed. Now, once added to the batch, the recognition credit you manually added is saved and will be committed correctly. | 599986 | All assemblies |
99206 |
| New Feature: In Blackbaud Internet Solutions, the Blackbaud CRM Integration service setting on the Schedules tab in Administration now displays the number of records to update in Blackbaud CRM. This is an informative way for you to monitor the amount of data the setting needs to process, which helps you avoid integration delays from Blackbaud Internet Solutions to Blackbaud CRM. | 599962 | All assemblies |
|
| New Feature: We have added the ability to use the “Add constituent attribute” global change process to add more than one instance of the same attribute category but a different attribute value to a constituent record. For example, you might want to assign an attribute category of "Distinguished Alum" with a value of "Athletics," as well one with a value of "Academics" to a graduate who earned honors in both areas. This can occur only when the attribute does not have the “Allow only one per record” setting marked and when the global change process does not have the “Overwrite existing value” setting marked. | 599137 | All assemblies |
99138 |
| This fix addresses an issue with the tax claim numbers for revenue as assigned by the R68 process for Gift Aid. This issue could occur if you ran the R68 process for a set of revenue transactions, but did not submit the claims to HMRC. If you then edited the R68 process and changed the tax claim number for the process, you could rerun it and inadvertently change the tax claim numbers associated with the revenue. There could also then be a mismatch between the tax claim numbers which appeared on the revenue records in CRM and the tax claim numbers submitted for the revenue to HMRC. Now, each instance of the R68 process will preserve the original tax claim number for the associated revenue. | 598730 | All assemblies |
99090 |
| This fix addresses a database revision error related to the main constituent page which could occur when upgrading Blackbaud CRM when the Corporate Info subtab has been removed. | 597730 | All assemblies |
|
| This fix addresses an error which sometimes occurred when running a tribute acknowledgement process. | 594265 | All assemblies |
98808 |
| This fix addresses an issue with information displayed on the VSE Survey report in Fundraising. Previously, donations from constituents not associated with an affiliated educational institution were included only in section 3 (“Outright Giving”) of the report and not included in the breakdowns in sections 4a (“Additional Details on Section 3 – Individuals”)and 4b (“Additional Details on Section 3 – Organizations & Other”). Now the donations are included correctly in both sections of the report. | 593685 | All assemblies |
98751 |
| This fix addresses an issue with prospect plan steps and interactions when you merge two constituents. Previously, if the source constituent had a major giving prospect plan with steps and those steps had interactions, the associated interactions did not appear on the target constituent after the constituent merge. The prospect plan and its steps did appear on the target constituent, just not the associated interactions. | 593521 | All assemblies |
98731 |
| This fix addresses an issue with the Membership Contribution Process. Previously, the process was not processing renewals and upgrades correctly for membership programs with the renewal window set to begin at the start of the membership. The issue occurred only when the membership term length was set to anything longer than 13 months. Now, membership terms of all lengths are correctly handled by the process. | 592548 | All assemblies |
98669 |
| This fix resolves an issue to successfully process transactions from Blackbaud Internet Solutions that are charged in Blackbaud Merchant Services, but do not appear in Blackbaud CRM. Previously, if an exception occurred for a transaction, it deleted from the transaction table. This prevented it from downloading to Blackbaud CRM. With this fix, the transaction remains in the table so it appears in Blackbaud CRM with an exception transaction status. | 587899 | All assemblies |
98381 |
| New Feature: The User Login part in Blackbaud Internet Solutions now includes the ability to change the order of the constituent attributes appearance on the form and modify their labels. This provides flexibility so you can specify how the attributes should appear on the web page, such as if you want them in the same order as they appear in Blackbaud CRM. | 583649 | All assemblies |
|
| New Feature: In Blackbaud Internet Solutions, organization settings now includes the Titles section so you can filter the options that appear from the Title field drop down on web pages. Previously, all titles from Blackbaud CRM appeared in the list. Use this feature to remove titles that are not frequently selected by website users, such as General and Chief. | 583648 | All assemblies |
|
| This fix helps improve the performance and loading time of the main import page in Administration for organizations with many different sites and many imports. The performance improvement happens only for system administrators or for those users in system roles with the “Run queries as admin” system privilege granted. | 575203 | All assemblies |
97320 |
| This fix addresses an issue with viewing query results through OData in a Microsoft Excel 2010, 2013, and 2016 which sometimes caused issues with data not appearing in Excel. | 568527 | All assemblies |
96829 |
| This fix addresses an issue with recognition credits for recurring gift payments in Enhanced Revenue Batch and Revenue Update Batch. Previously, when you added a payment for a recurring gift, the recognition credit information was defaulted from the settings on the constituent record and not from the recognition credit settings on the recurring gift. Now the recurring gift payment has the correct recognition credits as specified on the recurring gift. | 565617 | All assemblies |
96625 |
| This fix addresses a site security-based performance issue which could occur when opening or editing an import process in Administration. | 564288 | All assemblies |
96521 |
| Technical Change: This fix addresses an issue with searching for recognition programs in a Constituents query. Previously, if a user created a constituent query and wanted to include a specific recognition program as a filter, the user received a “The current user does not have rights to use this search” error, even when the system role had rights to all features. The issue did not occur for users who were system administrators. In order to address the issue, we created a new feature permission and you must manually grant the feature permission for “Recognition Program Search” under “Fundraising Efforts > Recognition Program” from the Features tab of the system role. | 563476 | All assemblies |
BB749968 |
| This fix addresses an issue which could occur when validating the Blackbaud Data Warehouse in Administration. Previously, when you attempted to validate the warehouse, you could receive a status of “Did not finish” with a message of “Invalid column name ‘ID’.” To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 561594 | All assemblies |
96308 |
| This fix addresses an issue with the constituent recognition process awarding levels to constituents correctly based on giving; however, the amounts calculated for the previously attained levels were sometimes incorrect. | 539085 | All assemblies |
95496 |
| New Feature: To enable you to specify which email address to use for messages in Blackbaud Internet Solutions, a new Email address type field is now available when you create templates from Email, Templates or messages from Email, Messages. When a constituent does not have the email address type you select in the field, the message is sent to their primary email address. | 538488 | All assemblies |
|
| This fix addresses an issue with UK-specific Gift Aid fields appearing on the “Split designations” screen accessed from the “Add a pledge,” “Edit pledge,” and “Edit posted pledge” screens in non-UK CRM environments. | 537608 | All assemblies |
95384 |
| This fix addresses an issue with recognition programs in Constituents. Previously, if you ran the constituent recognition process through a queue (set up in Administration) or if you scheduled the process to run using the “Job schedules” tab on the process, the status of the recognition program for constituents was always set to “Active.” This occurred even if you selected “Pending” in the “Initial status” field of the constituent recognition process. | 535335 | All assemblies |
95207 |
| This fix addresses an issue which could occur when you edited an export process and changed which smart query selection it used from one to another or from a smart query selection to an export definition. When the issue occurred, the error “You must use a selection that includes a system record ID in the primary key field” appeared even though that did not actually describe the issue. Now, you can edit the export process successfully without receiving the error when the system record ID is included. | 534145 | All assemblies |
95111 |
| This change applies to a Sponsorship Batch. Previously, the base amount displayed the currency of the organization instead of the base currency in multi-currency environments. Now, the correct currency is displayed. | 526736 | All assemblies |
|
| This fix addresses an issue with “Prospect assigned” email alerts which are configured in Administration. Previously, the email alert included a link to a blank CRM page. Now the email alert includes the correct link to the Prospect tab of the constituent record. | 520680 | All assemblies |
93491 |
| This fix addresses an issue that prevented a matching gift condition on an organization constituent record from being deleted if a matching gift claim referencing that rule had been entered in an Enhanced Revenue Batch | 408801 | All assemblies |
BB750982 |
| Assembly | Patch |
|---|---|
| All assemblies | 4.0.166.0 |
| Installer filename | SHA-1 Hash |
|---|---|
| BlackbaudInstaller.exe | 237DF37BE671E94AC06D443C033FE77B37A3844B |
| Comment | Work Item | Location | Knowledgebase | Patch |
|---|---|---|---|---|
| This fix addresses an issue with scheduled business processes not running in Blackbaud CRM. The issue occurred when the program’s virtual directory contained non-lowercase letters. The issue impacted existing job schedules, as well as new ones created after CRM 4.0 Service Pack 8 was installed. | 649439 | Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Server.dll |
102942 | 34 |
| This fix addresses an issue with recurring gifts and direct debit rejections. Previously, a direct debit rejection could appear to be associated with the next installment even if the rejection should be associated with a previous paid installment. However, the ledger distributions were correct. Now, the direct debit rejection is displayed with the correct installment on the recurring gift. | 641502 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1540.dll |
33 | |
| This fix addresses an issue with batch-related revisions and custom batch templates which caused upgrades to take a long time or to time out and fail. | 631567 | All assemblies |
101647 | 32 |
| This fix addresses an issue with revenue records in the Blackbaud Data Warehouse missing source codes that are present in Blackbaud CRM. The revenue source code information is now consistent. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 625474 | All assemblies |
101230 | 32 |
| This fix addresses an issue with customized batch templates. Beginning in CRM 4.0 Service Pack 6, revisions affecting customized batch templates were skipped. After upgrading, opening an uncommitted batch could cause an error. With this fix, the revisions run properly for all batch templates. | 623018 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1530.dll Blackbaud.AppFx.Platform.Catalog.dll Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.ServiceRevisions.Specs1530.dll Blackbaud.Web.Content.Core.dll |
31 | |
| This fix addresses an issue with site security and code tables. Previously, users with limited site security access could have inadvertently accessed code table entries that were associated with specific sites, even without access to those sites. | 621867 | All assemblies |
98460 | 32 |
| This fix improves performance for international customers when processing a donation that uses the Blackbaud secure payment server. | 620950 | All assemblies |
64364 | 32 |
| This fix addresses an issue in Enhanced Revenue Batch with adding revenue with a payment method of “Stock” toward an outstanding pledge. Previously, if you then used the “Sell stock” task on the revenue record to record the actual sale of the stock, the revenue was displayed as a gain, even if the stock was actually sold at a loss. Now, the revenue from the sale is displayed correctly as a gain or a loss. | 616781 | All assemblies |
100558 | 32 |
| Technical Change: Accent marks (also called diacritical marks), such as a tilde over an 'ñ' in Peña, now process from the following fields on a Donation Form part to Blackbaud CRM: First name, Middle name, Last name, Email address, Address Lines, City, State, and Zip. Previously, accent marks were removed when a website user entered these on your Blackbaud Internet Solutions website. This fix also applies to Blackbaud NetCommunity when you process donations to the Raiser's Edge. To resolve this, the HTMLHelper.VB file has been updated in the back end. | 608084 | All assemblies |
99890 | 32 |
| With this fix, we have improved the wording on the Vehicle Options tab in the Major Giving Setup configuration task in Prospects. Previously, when you edited a planned gift vehicle's options, you could mark a "Auto-calculate realized amount" checkbox which simply enabled the option for users to enable this functionality on an individual planned gift record. To help clarify the functionality, the checkbox now reads "Enable the option to auto-calculate realized amount." When the checkbox is marked and a planned gift of that vehicle type is added, you can then click the "Enable realized amount auto-calculation" task from the planned gift. As revenue is associated with the planned gift, the realized amount is then automatically calculated. Also with this fix, the planned gift vehicle's subtype is displayed, when applicable, in the summary section of the planned gift record. | 603943 | All assemblies |
32 | |
| This fix addresses an issue that occurred when importing transactions into Enhanced Revenue Batch, such as transactions from Blackbaud Internet Solutions. The issue occurred when updates to existing constituent information were included and the constituent had a spouse relationships with recognition credit information. Previously, the recognition credit information was completely removed from the related constituent in CRM. Also, the related constituent’s lookup ID was re-issued to the next available ID value. Now, the related constituent’s existing recognition credit information and lookup ID remain unchanged after the import. This issue was introduced in CRM 4.0 Service Pack 6. | 603933 | All assemblies |
99546 | 32 |
| This fix addresses an issue which could occur when upgrading Blackbaud CRM when you had created new, or had updated, custom batch templates. Previously, during an upgrade, all new and updated CRM-added batch templates were loaded or reloaded; however, new or updated custom templates were not loaded or reloaded appropriately when upgrade revisions were run. Now both CRM batch templates and custom templates are updated correctly. | 602877 | All assemblies |
99434 | 32 |
| This fix addresses an issue with synchronizing Luminate Online constituent interaction information from CRM to the Blackbaud Data Warehouse. Previously, the ETL refresh business process could time out. We have increased the timeout settings so this no longer occurs. | 602807 | BBDW.ReportDB.Catalog.dll Blackbaud.Web.Content.Core.dll |
96637 | 29 |
| This fix removes a run time error message on the Directory part when it includes the Education History Attributes field as a search field on your Blackbaud Internet Solutions website. The message appeared when a website user entered search criteria in the field, and the program returned a constituent record with that data in the results. The DirectoryOutput.ascx.vb and BBGridViewDataSource.vb files have been updated in the back end to remove this error message so the search results now appear successfully. | 602057 | All assemblies |
99367 | 32 |
| This fix addresses an issue which could occur when importing into an Enhanced Revenue Batch. Previously, if you mapped the "New/edit constituent" batch template column fields in the import and the import included revenue for existing constituents, you could receive an error. | 602003 | Blackbaud.AppFx.Address.UIModel.dll |
99361 | 29 |
| This fix addresses an issue with constituent revenue application smart fields for constituents who are members of households or groups. Previously, if the household or group gave the revenue (not the individual constituent) and the smart fields were set up to calculate based on revenue recognition, the constituent revenue application smart field values for the individual constituents were incorrect and did not include the recognition amounts based on the household or group giving. The individual constituent's smart field values could also be incorrectly inflated by counting revenue and recognition amounts multiple times. Now, these smart field values are calculating correctly. After you upgrade, you must re-process these smart fields in order for the values on the individual constituents to be correct. This fix addresses issues reported in work items 586545 and 601462. | 601462 | All assemblies |
99309 | 30 |
| This fix addresses an issue with duplicate constituent matching in Constituent Update Batch. Previously, if you had a constituent in Blackbaud CRM with an address and an address type but with no post code and then you entered information for the same constituent in Constituent Update Batch with the same address and address type also with no post code, the program did not match those two constituents as the same and so an additional, duplicate address with no post code was created. | 601051 | All assemblies |
99271 | 32 |
| This fix resolves an issue to successfully track external links sent from Blackbaud Internet Solutions in a marketing effort. Previously, tracking information was lost intermittently. | 599689 | All assemblies |
99194 | 32 |
| This fix addresses an issue which occurred when solicit codes were used as exclusions for marketing efforts. Previously, if you added a solicit code as an exclusion to one marketing effort, it was inadvertently removed from other marketing efforts. Now, the same solicit codes can be used on multiple marketing efforts. This issue was introduced in CRM 4.0 Service Pack 6. If you added marketing efforts with solicit codes as exclusions in Service Pack 6, you should check your marketing efforts after you upgrade and re-add the solicit codes when needed. | 599331 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1510.dll Blackbaud.AppFx.Marketing.Communications.Catalog.dll Blackbaud.Web.Content.Core.dll |
99155 | 29 |
| This fix addresses an issue with a data list that had been customized. Previously, specific values defined for some fields in the data list did not appear correctly. | 599182 | Blackbaud.AppFx.Server.dll Blackbaud.AppFx.UIModeling.RestServices.dll Blackbaud.AppFx.WebShell.WebUI.dll |
99142 | 29 |
| With this fix, the Degree field for the Education histories element on a Profile Update form now displays the degree name on your Blackbaud Internet Solutions website. Previously, the degree's database ID (the GUID) appeared. | 599106 | Blackbaud.AppFx.ApexForm.Web.dll Blackbaud.AppFx.BBNCSvc.dll Blackbaud.Web.Content.Core.dll |
98998 | 28 |
| This fix addresses an issue with correspondence process mailings to households. Previously, if a the processing options for the output format were set to “Include household member processing” and “Mail to primary household member when available,” the primary household member was inadvertently removed from the mailing if that constituent was also a non-primary of another household included in the mailing. | 598446 | All assemblies |
99086 | 32 |
| This fix addresses an issue with benefit unit values on event registrations added from through batch in CRM. Previously, if a constituent had two or more of the same registration option for an event registration, the benefit unit value amount on the saved registration was doubled. For example, if a constituent registered for an event and requested two “Couple” registration options with a T-shirt benefit (four registrants, four shirts), the benefit unit value amount displayed on the Benefits tab of the registration was double the actual unit value set up for the T-shirt. The quantity of the benefits was calculated correctly, but the unit value and therefore the total value of the benefits were incorrect. | 598166 | All assemblies |
32 | |
| This fix addresses an error which sometimes occurred when website users attempted to sponsor a child through Blackbaud Internet Solutions. | 598158 | Blackbaud.AppFx.Sponsorship.ContentManagement.dll |
99053 | 28 |
| This fix addresses an error which occurred when importing revenue transactions with application IDs into an Enhanced Revenue Batch. This issue was introduced in CRM 4.0 Service Pack 6. With this fix, CRM reads the application ID from the import file and associates the correct transaction type code to the revenue automatically. | 596435 | All assemblies |
98962 | 30 |
| This fix improves performance issues related to application user security which occurred when running certain processes in CRM. | 596391 | All assemblies |
32 | |
| This fix makes RequestContext and RequestSecurityContext of the Import Process Handler public so they can be set outside of the platform catalog. | 595013 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Platform.Catalog.dll |
98217 | 29 |
| Technical Change: When you use Blackbaud Merchant Services to process Blackbaud Internet Solutions transactions, the gateway ID for credit card transactions is now processed and appears on the Reconcile transactions and disbursements page in Blackbaud CRM. | 594242 | All assemblies |
30 | |
| New Feature: We have added the ability to assign categories to smart fields. When you add or edit a smart field, you can now choose to assign a category to it. You can define your categories to best suit the needs of your organization. You can then sort or filter smart fields by category on the Smart Fields page under Administration to help you navigate the list more easily. To sort or filter by category, you use the new Category column, which now appears on the list by default. In addition, we have added the columns "Created by" and "Created on" to this list, which you can also use for sorting or filtering smart fields. These two columns do not appear on the list by default, but you can add them by clicking Columns and selecting them. | 593042 | All assemblies |
30 | |
| This fix addresses an issue with constituent revenue application smart fields for constituents who are members of households or groups. Previously, if the household or group gave the revenue (not the individual constituent) and the smart fields were set up to calculate based on revenue recognition, the constituent revenue application smart field values for the individual constituents were incorrect and did not include the recognition amounts based on the household or group giving. The individual constituent's smart field values could also be incorrectly inflated by counting revenue and recognition amounts multiple times. Now, these smart field values are calculating correctly. After you upgrade, you must re-process these smart fields in order for the values on the individual constituents to be correct. This fix addresses issues reported in work items 586545 and 601462. | 586545 | All assemblies |
30 | |
| New Feature: As a follow up to the new Delete email permanently organization setting in Administration (released in version 4.0 Service Pack 5), you can now select to delete messages and newsletters based on whether the email is beyond a certain number of days, months, or years. To delete email permanently based on age, schedule the new Automatically delete email older than option. When the process runs based on this setting, the program first checks this section to delete email permanently. If you do not want to delete email messages and newsletter issues based on age, leave the default to Never. | 585412 | All assemblies |
32 | |
| This fix addresses an issue which occurred when updating credit card numbers for recurring gifts. Prior to CRM 4.0 Service Pack 2, if a constituent had more than one recurring gift using the same credit card and a CRM user updated the credit card number on the "Edit payment details" screen for one recurring gift, the user received the message: "Other commitments use the original credit card. Would you like to update them to use the new credit card?" Beginning in CRM 4.0 Service Pack 2, even if the user clicked "No," all of the commitments were inadvertently updated to the new credit card number. Now, in CRM 4.0 Service Pack 6, if the user clicks "No" on the message, the credit card information for the other commitments remains unchanged. The same issue occurred beginning in CRM 4.0 Service Pack 2 when updating credit card numbers for commitments in Revenue Update Batch. However, in batch, the user was not prompted to change the details for other commitments; the credit card information for the other commitments was automatically updated. Now, in CRM 4.0 Service Pack 6, in Revenue Update Batch, the credit card information for only the commitment being edited in the batch is updated. | 585200 | All assemblies |
98224 | 27 |
| This fix addresses an issue with changing the constituent or revenue amount fields for a revenue transaction in a Revenue Update Batch. Previously, if the appeal entered on the original revenue transaction included an appeal with a default designation, you could have manually changed the designation on the original transaction before you saved it. If you later edited that transaction in a Revenue Update Batch and changed the constituent or the amount, the designation was automatically re-defaulted and the designation that was selected manually was overwritten. Now, changing the constituent or revenue amount fields for a transaction in a Revenue Update Batch will not re-default the designation in order to match the behavior that occurs when you edit these transactions one at a time and not in a batch. | 584659 | All assemblies |
98178 | 32 |
| This fix improves a performance issue which sometimes occurred when running a consolidated receipt process. Previously, the consolidated receipt process could take longer than expected to complete or could time out and not complete. | 584638 | All assemblies |
98175 | 30 |
| This fix addresses an issue with importing constituents and revenue from a list segment in a direct marketing effort into Enhanced Revenue Batch. Previously, if the constituent was imported into a batch and then the same constituent and list segment was used in another batch, the error "BBERR_ADDRESS_PRIMARYADDRESSREQUIRED" appeared. This error occurred when constituent matching was enabled in the "Enable/disable matching" configuration task in Administration. | 583704 | All assemblies |
97626 | 30 |
| New Feature: You can now easily indicate whether to send multiple or single copies of emails when two or more constituent records include the same email address. To send one email to multiple constituents with the same email address, clear the new Send a unique email to each constituent who shares the same email address option in Administration. You typically select this when you want constituents, such as spouses, who share email addresses to each receive a copy of messages. This new option applies to recipients in an email constituent list and an import list. | 583647 | All assemblies |
32 | |
| This fix helps improve the performance of the “Revenue dynamics” smart query. | 583491 | All assemblies |
98048 | 32 |
| When you download a recurring gift with a split designation from Blackbaud Internet Solutions to a Blackbaud CRM batch, the gift type now correctly downloads with a 'Gift' revenue type. Previously, this appeared as 'Grant Award.' In addition, the ability to edit designations for these transactions has been restored. To resolve this issue, the DonationProcessor.vb file has been updated in the back end. | 581462 | All assemblies |
97774 | 32 |
| When you use the Record Display part on your Blackbaud Internet Solutions website, the Event Date merge field now appears in the correct format. Previously, it displayed alphanumeric characters. | 581217 | All assemblies |
97748 | 32 |
| This fix addresses an issue with the sort order for some code tables after you installed Blackbaud CRM Service Pack 5. Code tables are sorted alphabetically by default. However, before Service Pack 5, if a user chose to sort code tables differently, the system remembered this selection and used the sort order chosen by the user the next time the user accessed the code table. After you installed Service Pack 5, code tables reverted to alphabetical sort order, even if you had selected a different sorting option. This fix ensures that sorting options are persistent as they were before Service Pack 5. | 580556 | All assemblies |
97353 | 27 |
| Blackbaud CRM now eliminates leading spaces when downloading a zip code from your Blackbaud Internet Solutions website to the program. The leading spaces in the field were entered by the website user. This fix improves constituent searches that use zip code by eliminating the leading spaces. To resolve this, the AddressUIBase.vb file has been updated in the back end. | 580472 | All assemblies |
32 | |
| This fix addresses a recognition credit issue which occurred when adding a payment to a matching gift claim in Enhanced Revenue Batch. Previously, if the matching gift claim had more than one designation, the recognition credits were duplicated on the matching gift organization’s constituent record. | 579991 | All assemblies |
97636 | 32 |
| This fix addresses an issue which sometimes caused the next installment date included in the output of a reminder process to be incorrect. | 579817 | All assemblies |
97000 | 30 |
| This fix addresses an issue where constituents within the search radius did not show in a MapPoint Radius search despite being closer to the center than others displayed. With this fix, the constituents now correctly appear in MapPoint Radius search results. | 579301 | All assemblies |
30 | |
| This change applies to an Enhanced Revenue Batch containing a pledge where the amount is zero and the frequency is set to anything other than "Single installment" or "Irregular." Previously, when editing any pledge field other than "Amount," an error displayed stating that the server connection was lost. With this fix, when a pledge is edited, the server connection remains. | 578925 | Blackbaud.AppFx.Fundraising.UIModel.dll |
26 | |
| This fix addresses an issues with security permissions for information in ad-hoc queries related to direct marketing efforts and refreshed segment counts. Previously, if a user had rights to view direct marketing effort segment counts in a query and then the counts were refreshed, those query security permissions were inadvertently removed. Now, the queries retain the correct, granted permissions for granted users to be able to query on information related to refreshed direct marketing segment counts. After you upgrade, existing queries now return the correct information automatically. | 578104 | All assemblies |
97516 | 32 |
| Technical Change: This fix addresses an issue with users without System Administrator security rights and the "Screen list" button on the Research List page in Prospects. Previously, these users were not able to see this button, even when system administrators thought the users' system roles had the correct permissions to do so. For this fix, we added an additional security permission for the "WealthPoint Generate Request Research List Add Form." System roles will need to be granted this additional security permission in order for users to access the "Screen list" button. | 577276 | All assemblies |
97474 | 30 |
| This fix addresses an issue with pledge commitments in Enhanced Revenue Batch. Previously, certain pledges did not appear as commitments for a constituent in the batch. This occurred for pledges which had multiple payments and write-offs for the same pledge installments. Now, the pledge commitments will appear correctly for the constituent in the batch. | 577025 | All assemblies |
97444 | 32 |
| This fix removes the error 'Object reference not set to an instance of an object' when you attempt to commit a BBIS Profile Update Transaction Batch in Blackbaud CRM with educational history data from your Blackbaud Internet Solutions website. | 576575 | All assemblies |
97401 | 30 |
| New Feature: When you make changes to a constituent record to "Show more" or "Show less" of the constituent summary of the record which includes the constituent summary tiles, the program remembers your settings the next time you open a constituent record. This is not a system-wide setting, but instead is specific to each user. | 576504 | All assemblies |
30 | |
| This fix addresses an issue with some organization names being incorrectly changed in Constituent Update Batch. When you create a new organization constituent record, you can enter a backslash to denote a first word of the organization's name that should not be required when searching for the organization by name. For example, you might enter "A\Seed for Hunger" or "The\Dog House" so that users can simply search for "Seed for Hunger" or "Dog House" and still easily find the organization record. Previously, if you included the organization in a Constituent Update Batch and made any changes or additions to the record, the "A" or "The" and the backslash were removed from the organization's name. Now, you can update the organization in Constituent Update Batch and the full name of the organization is preserved. | 575827 | All assemblies |
97354 | 30 |
| This fix improves the way smart field data is stored in the Blackbaud Data Warehouse in order to prevent failures during the ETL refresh process. | 575250 | All assemblies |
96696 | 30 |
| This fix addresses an issue which prevented some credit card information from being properly saved in Enhanced Revenue Batch. The issue occurred when Blackbaud CRM received an error status from the Blackbaud Payment Service which CRM did not know how to interpret properly. Now Blackbaud CRM can process the error information from the Blackbaud Payment Service correctly during payment processing. The fix addressed issues reported in work items 544731, as well as 575210. | 575210 | All assemblies |
97321 | 30 |
| In order to optimize performance, we have updated the constituencies ETL in the Blackbaud Data Warehouse to take advantage of the new functionality that lets you mark constituencies as inactive. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 574441 | All assemblies |
94516 | 27 |
| This fix addresses an issue with gifts of sponsorship given through Blackbaud Internet Solutions. Previously, if the gift of sponsorship was given to a constituent that already existed in CRM, the sponsorship was not correctly processed as a gift. | 573722 | All assemblies |
97223 | 27 |
| This fix addresses an issue with benefit unit values on event registrations added from an event record in CRM not using batch. Previously, if a constituent had two or more of the same registration option for an event registration, the benefit unit value amount on the saved registration was doubled. For example, if a constituent registered for an event and requested two "Couple" registration options with a T-shirt benefit (four registrants, four shirts), the benefit unit value amount displayed on the Benefits tab of the registration was double the actual unit value set up for the T-shirt. The quantity of the benefits was calculated correctly, but the unit value and therefore the total value of the benefits were incorrect. | 573703 | All assemblies |
97220 | 30 |
| Technical Change: Previously, when a registrant's event attendance status changed to 'Will not attend' or 'Canceled' in Blackbaud CRM, the change did not impact event capacity on the Event Registration Form part on your Blackbaud Internet Solutions website. With this fix, event capacity on your website now adjusts when a registrant's status updates to either of these in Blackbaud CRM. For example, if two attendees cancel their attendance for an event, the event capacity increases by two on your website. | 573608 | All assemblies |
30 | |
| This fix addresses an issue with address validation in constituent batches (Constituent Batch, Constituent Update Batch, and Constituent Address Update Batch), as well as in Enhanced Revenue Batch. Previously, when you validated addresses for all rows in the batch and then committed the data, the address information was entered or updated correctly on the constituent records. However, the validation information on the Details tab of the constituent's address ("Last attempt" and "Validation message") did not appear. This validation information now appears correctly on the address so you can view and query on it as needed. | 573561 | All assemblies |
97207 | 30 |
| New Feature: With this release, when you issue a refund for a credit card transaction, you can now view refund details on the Details tab of the payment record as well as the Reconcile transactions and disbursements page in Treasury. Note that the ability to issue a refund for a credit card transaction by editing or deleting a payment is existing functionality. | 573168 | All assemblies |
30 | |
| This fix addresses an issue with the "Date sent" for a mailing direct marketing effort on the Communications tab of a constituent record. Previously, if the "Launch date" field on the direct marketing effort was blank, the "Date sent" for the mailing on the Communications tab of the constituent record was also blank. Now, the "Date sent" for the mailing on the Communications tab of the constituent record is set to the "Activation date" of the marketing effort when the "Launch date" is blank. | 573014 | All assemblies |
97151 | 30 |
| This fix addresses an issue with using finder numbers in Enhanced Revenue Batch. In Blackbaud CRM 4.0 Service Pack 5 or higher, if you entered a finder number to enter a transaction in batch, the designation appeared to be filled in and you could enter the transaction amount and date. However, if you tried to validate the batch, you received an error that the transaction must have at least one designation. Now, the finder number populates the designation information correctly and the batch can be validated. | 572888 | All assemblies |
97147 | 30 |
| This fix corrects an eReceipt issue for the Transaction Manager part on your Blackbaud Internet Solutions website. Previously, it was possible for an eReceipt to appear for a different constituent other than the logged in website user. Now, the correct eReceipt appears for each logged in user on your website. To resolve this, the following files have been modified in the back end: CMSReceiptKeyByRevenueId.DataList.xml, CMSReceiptKeyByRevenueIdDataList.codegen.VB, and GivingHistory2Control.ascx.vb. | 572484 | All assemblies |
27 | |
| This fix addresses two Marketing and Communications-related issues which could occur when importing direct marketing efforts into a Direct Marketing Effort Batch. The first issue dealt with "Test segment codes." Previously the combination of the "Test segment name" and the "Test segment code" had to be unique. The same "Test segment code" could not be used for more than one test segment. Now, only the "Test segment name" must be unique and the same code can be used on multiple test segments. The second issue dealt with direct marketing packages. Previously, if a package was associated with a direct marketing effort segment, you could not update the marketing effort segment with a different package during import. This fix addressed two work items: 512314 and 572140. | 572140 | All assemblies |
73628 | 27 |
| This fix addresses an issue where the Wealth and Ratings page was unable to load if a group or constituent had over 100,000 gifts found by WealthPoint. | 572083 | All assemblies |
97092 | 27 |
| This fix addresses a potential revision failure when upgrading Blackbaud CRM. Previously, you could receive a "Revision ID: 529 for revision set 1430 failed" error due to a memory usage issue. | 571478 | All assemblies |
97034 | 30 |
| This fix addresses an issue which occurred when merging two constituents when the source constituent was a member of a household and the target constituent was not a member of any household. Previously, if you selected to mark the source constituent inactive after the merge, the constituent still remained part of the household in the CONSTITUENTHOUSEHOLD database table. The source constituent was not visible on the household record in the program, but the information was incorrect in the CONSTITUENTHOUSEHOLD table which could cause issues with customizations or other reporting processes. Now, when the two constituents are merged, the source constituent is marked inactive and is removed from the CONSTITUENTHOUSEHOLD table. | 571445 | All assemblies |
97028 | 30 |
| New Feature: We have added the Site field to several constituent search screens so that you can further refine your search parameters. The updated search screens include: Constituent Search, Constituent Search by Name or Lookup ID, Committee Search, and the corresponding search screens in batches, when available. | 570996 | All assemblies |
30 | |
| This fix addresses an issue when switching view options in the Information Library. Previously, when you selected to view queries by folder, the system remembered your selection the next time you were on this page. However, when you selected to view queries by category, owner, or record type, those selections did not persist the next time you were on the page. With this fix, all "view by" selections are persistent, so you see the last option you selected when you go back to this screen. | 569673 | All assemblies |
96918 | 27 |
| Technical Change: This fix downloads the assigned Constituency to organization records in Blackbaud CRM when processing a corporate gift from your Blackbaud Internet Solutions website. Previously, these only downloaded to individual records. To resolve this issue, the dbo.USP_BATCHREVENUECONSTITUENT_ADD file has been updated in the back end. | 569617 | All assemblies |
96915 | 30 |
| Proposed Patch Tag: When a pledge with irregular installments is edited in Revenue Update batch the installment dates could be incorrectly altered when viewing the installment schedule through the edit installments dialog. The dates should no longer be incorrectly altered. | 568909 | All assemblies |
96852 | 30 |
| New Feature: For databases with the UK locale, the Payment 2.0 part in Blackbaud Internet Solutions now includes information about whether a Gift Aid declaration has been included with a donation. This information appears in the Payment 2.0 part shopping cart items list, the Payment 2.0 part confirmation page receipt grid, and the Payment 2.0 part acknowledgement email receipt grid. | 568598 | All assemblies |
BB742662 | 27 |
| New Feature: The Payment 2.0 part in Blackbaud Internet Solutions now includes information about whether a donation is given anonymously. This information appears in the Payment 2.0 part shopping cart items list, the Payment 2.0 part confirmation page receipt grid, and the Payment 2.0 part acknowledgement email receipt grid. | 568596 | All assemblies |
BB742662 | 27 |
| Previously, when matching gift records were imported through an Enhanced Revenue Batch, multiple donations displayed in the Revenue Application query. With this fix, the correct donations display in the query. | 568109 | All assemblies |
96803 | 30 |
| This fix addresses an issue with the “Constituent declines Gift Aid” checkbox on recurring gifts in a UK environment. Previously, after you saved the recurring gift, you could not edit it and mark or unmark the checkbox unless you changed the recurring gift amount or designation. Now, you can edit the gift and change the checkbox without changing anything else. | 568017 | All assemblies |
32 | |
| This fix addresses an issue which occurred when copying segments from one direct marketing effort to another. Previously, users sometimes received the error "The current user does not have rights to use this form" even when they had security rights to copy the segments to the marketing effort. Now, users can copy segments to a marketing effort without receiving the error. | 567832 | All assemblies |
96777 | 30 |
| This fix improves the performance of selections used within segments and segments groups in "Marketing and Communications." | 567618 | All assemblies |
96749 | 27 |
| This fix addresses a performance issue that occurred when you attempted to validate and commit an Enhanced Revenue Batch when a constituent had a large number of commitments. | 567556 | All assemblies |
27 | |
| This fix removes an error that appeared with a 'download transaction' ID message when attempting to download donations for non-US countries from Blackbaud Internet Solutions into a Blackbaud CRM batch. This was caused by an invalid row for routing numbers in a back end table. To resolve this, the DonationCapture2.ascx.vb file has been updated in the back end so that a validation now applies to all countries to validate routing numbers for the Donation Form. | 567421 | All assemblies |
96732 | 32 |
| This fix improves the performance of the "Sponsor" node in queries and selections. | 567196 | All assemblies |
96718 | 30 |
| This fix resolves a site security assignment issue when you download an organization record from Blackbaud Internet Solutions into Blackbaud CRM. Previously, the site security did not assign to the organization record. With this fix, the site security successfully assigns. To resolve this issue, the dbo.USP_BATCHREVENUECONSTITUENT_ADD file has been updated in the back end. | 567128 | All assemblies |
96710 | 27 |
| This fix addresses an error that occurred when the geocode process encountered an exception and all associated addressCoordinates records were deleted. With this fix, addresses that have existing coordinates will be retained in the addressCoordinates table and flagged so that they will be picked up for the next run of the geocode process. Records that have no longitude/latitude set will be deleted. | 566102 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Constituent.SpWrapConstituent.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1500.dll |
25 | |
| New Feature: We have added two new settings to the "Global rules for married constituents" section on the Marriage tab of the Manage Life Changes page. To access this page, click "Manage life changes" under Configuration in Constituents. You can now select whether or not to have the primary phone number and email address automatically copied to a spouse's constituent record when you create the spouse relationship. Previously, when you added a spouse, all primary contact information (address, phone number, and email address) was copied from the existing constituent to the spouse record. Now, based on the new "Global rules for married constituents" settings, the primary phone number and email address may or may not be automatically copied to the spouse's record depending on your configuration settings. The primary address, however, is always copied to the spouse record. By default, the new "Copy primary phone number to spouse's record" and "Copy primary email address to spouse's record" checkboxes are marked. If you do not want this information copied to spouse records, you can change these configuration settings. | 564759 | All assemblies |
71543 | 30 |
| This fix addresses an error that occurred when you ran the Prospect Assignment Process for prospects that had both a current prospect manager and a historical prospect manager with null start dates. | 564757 | Blackbaud.AppFx.MajorGiving.Catalog.dll |
84436 | 24 |
| This fix helps improve performance of the "Assign letters process" on the Letters tab of the Acknowledgements page. | 564472 | All assemblies |
30 | |
| This fix helps improve performance of the "Marketing acknowledgement process" in Marketing and Communications. | 564461 | All assemblies |
30 | |
| This fix addresses a revision error that could occur when you upgraded Blackbaud CRM. | 563644 | All assemblies |
27 | |
| This fix addresses an error which sometimes occurred when exporting a marketing effort. | 563479 | Blackbaud.AppFx.Server.dll |
96465 | 24 |
| This fix addresses an issue when filtering global changes by site. Previously, the filtering by site was not working correctly on the Global Changes page. This issue was introduced in Blackbaud CRM 4.0 Service Pack 5. With this fix, filtering by site is working correctly again. | 563126 | All assemblies |
96434 | 27 |
| Previously, when adding and saving a payment for a specific account system, the GL Distributions tab for the payment displayed a different account system. With this fix, the payment appears with the correct account system. | 563097 | All assemblies |
96431 | 27 |
| This fix addresses an issue with the Model Scores and Ratings Batch and the Model Scores and Ratings Update Batch. Previously, you could not enter model scores or ratings information for organizations, only individual constituents. You can now select constituents who are individuals or organizations in these batches. | 562792 | All assemblies |
96414 | 30 |
| This fix addresses an issue with importing records with lookup IDs or alternate lookup IDs into a Constituent Update Batch. Previously, the constituent matching logic was not applied based on the lookup or alternate lookup IDs and the constituent update rules were not followed. Constituent matching rules and constituent update rules are defined in the "Global data entry settings" task in Administration. Now the constituent matching logic is applied and the constituent update rules are followed. | 562315 | All assemblies |
96354 | 30 |
| Previously, when upgrading from CRM version 3.0 to 4.0, a revision error could occur for systems that use the SEPA banking system. With this fix, the error no longer occurs. | 561302 | All assemblies |
96293 | 27 |
| This fix addresses an issue when running certain smart queries. After you applied Service Pack 5 of Blackbaud CRM, user-defined smart queries that used filter operators other than "Equal To" could return an error when you tried to run them. This fix addresses the issue so that the queries run correctly. | 561247 | All assemblies |
96291 | 27 |
| Previously, when updating multiple designation levels, a trigger in the designation table could throw an error. With this fix, we improved the trigger to handle bulk (multiple) updates. Note that this change fixes customizations that broke when the trigger was introduced in CRM 4.0 Service Pack 4 and is directly related to work item 505735. Additional customizations should not be impacted. | 561209 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1500.dll |
96453 | 24 |
| This change applies to an Enhanced Revenue Batch when adding a payment to a pledge associated with pre-existing paid installments. Previously, upon opening the saved batch, when the batch was validated or the batch row that included the pledge payment was changed in any way, the application associated with the payment was removed. With this fix, the application remains on the batch row. This change also introduces a known issue with the "Application" field in a Revenue Update batch. When the payment is applied to a fully-paid commitment, the "Application" field is incorrectly blank and the commitment information is only accessible through the "Apply to commitments" screen. | 561015 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1500.dll |
96278 | 24 |
| When an administration user manually enters the URL for a deleted web page into a browser address bar, the browser now redirects the user to the Site explorer page. Previously, the deleted page continued to appear. This change applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 560774 | All assemblies |
96259 | 27 |
| Previously, when a non-administrator user searched for revenue records in a Revenue Update Batch, the process was slow and did not return records. With this fix, we updated the search form SQL to use FTM tables. Now, the search process returns records in a timely manner. | 560637 | All assemblies |
95879 | 27 |
| Technical Change: This fix addresses an error that could occur when you set a filter in a data list created using the "Revenue (from the Blackbaud Data Warehouse)" query view. Previously, you received an error when you tried to save the data list after setting filters for attributes and smart fields. If you have custom code or reports that use a dbo.V_QUERY_BBDW_ATTRIBUTE<GUID> view or a dbo.V_QUERY_BBDW_SMARTFIELD<GUID> view, you must change them to use the BBDW.V_QUERY_BBDW_ATTRIBUTE<GUID> or BBDW.V_QUERY_BBDW_SMARTFIELD<GUID> instead. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 560472 | Blackbaud.AppFx.WebOlap.dll |
95836 | 22 |
| We have optimized the processing performance of the DIM_CONSTITUENT package in the Blackbaud Data Warehouse. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 560433 | All assemblies |
94516 | 27 |
| New Feature: This fix addresses an issue with the PhoneFinder process in the Data Tune-up section of Administration. Previously, if a constituent had an address marked as "Do not send mail to this address," the address was still included in the PhoneFinder submission file. With the AddressFinder process, you have the flexibility to choose whether or not to include those records. To be more consistent, there is now an "Include addresses marked as Do Not Mail" checkbox on the "Edit PhoneFinder submit process" screen. If you have many constituents who do not receive mail from your organization, you may still want to use addresses that are marked as "Do not mail" to help locate new or updated phone numbers for those constituents. However, if you use "Do not mail" to also indicate invalid or out-of-date addresses, you may not want to use those in the PhoneFinder process. By default, this checkbox is marked to match existing behavior. In order to omit these addresses from the PhoneFinder process, you must edit existing PhoneFinder submit processes and unmark the "Include addresses marked as Do Not Mail" checkbox. | 560242 | All assemblies |
27 | |
| With this fix, we have improved the performance of the AddressFinder process located in the Data Tune-up section of Administration. Previously, in the "Step 1: Create and submit file to Blackbaud" step, you could select "For households, submit shared addresses once along with primary contact name" and, in some situations, the AddressFinder process could time out and fail to complete as a single file. You then had to break up the addresses into multiple files for processing. In addition, we made some performance improvements to the "Step 3: Update addresses" step which included enhancements for how the batch is committed. | 560206 | All assemblies |
27 | |
| This fix addresses a revision error that could happen when reloading code table specs. Previously, when you had a custom index on a code table and reloaded all code tables, the custom index could not be updated. | 559674 | All assemblies |
27 | |
| Previously, when multiple processes (such as saving revenue and adding solicit codes) attempted to update the same records simultaneously, a deadlock error message displayed. This fix improves performance and reduces the occurrence of deadlock errors. | 545987 | All assemblies |
96015 | 27 |
| This fix addresses an issue which occurred when importing into a Constituent Update Batch when the constituents had many pre-existing relationships in the database. Previously, the batch commit process after the import could take much more time to run due to the number of relationships the process needlessly checked. Now, this process has been improved so the batch commit process takes less time to run. | 545968 | All assemblies |
96013 | 27 |
| New Feature: This fix helps improve performance when you attempted to edit relationships between constituents. Previously, when a constituent had a relationship with a commonly used relationship pair (such as employee and employer) and you tried to edit the relationship, the "Edit relationship" screen could take a long time to load. To improve performance, we have added the ability to change the functionality so that the sort order for relationships in those relationship fields is alphabetical instead of being sorted with the most commonly used relationship pair at the top of the list. However, when you change the sort order to alphabetical instead of "Most frequently used pairing," the reciprocal relationship will not default automatically to the reciprocal relationship field. The new setting is on the Relationship Types tab of the Relationship Settings page which you access from the "Relationship settings" configuration task in Constituents. There is now a "Sort method for reciprocal relationships" setting on the tab. After you upgrade, the new setting will be set to "Most frequently used pairing." In order to see the performance improvements, you must change this setting to "Alphabetical" instead. | 545019 | All assemblies |
BB755658 | 27 |
| This fix addresses an issue which prevented some credit card information from being properly saved in Enhanced Revenue Batch. The issue occurred when Blackbaud CRM received an error status from the Blackbaud Payment Service which CRM did not know how to interpret properly. Now Blackbaud CRM can process the error information from the Blackbaud Payment Service correctly during payment processing. The fix addressed issues reported in work items 544731, as well as 575210. | 544731 | All assemblies |
95954 | 30 |
| This fix addresses an issue which could occur when using AddressFinder in the Data tune-up area of Administration. Previously, when on "Step 2: Get file from Blackbaud," you could receive an error message if an address you submitted to Blackbaud had been deleted from the database. The "Index was outside the bounds of the array" message no longer appears and the addresses that are in the response file but have been deleted from the database are skipped and are placed into an exception file. You can download the exception file (as *.csv or *.xlsx) from the Recent Status tab of the process. | 544686 | Blackbaud.AppFx.AddressManagement.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.Web.Content.Core.dll |
20 | |
| This fix addresses an issue which occurred when refreshing an email marketing effort. Previously, if the refresh process timed out, you could receive an exception message that could not be properly displayed. Now the exception message information will be logged to the event viewer and IIS logs instead. | 544586 | All assemblies |
95937 | 32 |
| This fix helps improve performance with updating unmapped transactions from a general ledger account system in Administration. Previously, from an account system, if you clicked the "Review unmapped transactions" task and then clicked the "Update unmapped transactions" task, the process could sometimes run slowly or fail to complete. | 544478 | All assemblies |
95924 | 32 |
| This fix improves the performance of queries that include sponsorship nodes and recurring gift payment queries. | 544100 | All assemblies |
95890 | 27 |
| This change applies to revenue records associated with posted credit card payments processed through Blackbaud Payment Service. Previously, when a user selected to delete a revenue record, a confirmation message appeared with no option to cancel out of the delete process. When a user clicked the "X" in the top corner of the confirmation message, the message closed and the payment was deleted. With this fix, we added a "Cancel" option to the confirmation message and confirmed that clicking Cancel or "X" closes the confirmation message and nothing is deleted. | 543695 | All assemblies |
27 | |
| Previously, when creating a batch using the "Generate revenue update batch" process, pledge payment adjustment fields were disabled, and an error displayed during validation. With this fix, adjustment field values from the batch grid automatically display in the payment adjustment details section on the Edit installment designations screen, and the batch validates properly. | 543613 | All assemblies |
27 | |
| This fix addresses an issue when searching for smart field processes by site. This happened when you edited a process for a smart field queue and tried to search for an existing smart field process. When you selected a specific site to search under, the smart field processes for that site did not appear in your search results. The results did appear if you did not filter your search by site. With this fix, you can see the correct smart field processes in your search results even when you restrict the results by site. | 543530 | All assemblies |
95839 | 27 |
| This fix address an issue with direct marketing efforts and solicit code exclusions. Previously, if a solicit code was added as an exclusion to a communication template and you created a marketing effort from that template, you could still then go back and edit the solicit code. If you marked the solicit code itself as required when it wasn't required at the time the marketing effort was created, you could receive an error when you edited any solicit code exclusions on the marketing effort and tried to save it. The program was incorrectly trying to add a duplicate "required" version of the solicit code to the effort automatically, even though that was not expected behavior. Now, the marketing effort is saved correctly with only one solicit code and no duplicates, so there is no error. | 543524 | All assemblies |
95838 | 27 |
| This fix addresses an issue when you save new batches assigned to an owner other than the user creating the batch. Previously, when you created a new batch and assigned it to an owner different from you, the batch would open when you saved it. Now, when you save the batch, the batch does not open if it is assigned to an owner different from you. | 543435 | All assemblies |
95833 | 27 |
| Previously, when users tried to edit a "Generate payments" process that was associated with an inactive batch template, an error displayed. With this fix, users can now edit the process when the batch template is inactive. | 543345 | All assemblies |
95818 | 27 |
| This fix resolves an issue with the Designation field on a Donation Form web page when using Internet Explorer 10 or 11. With this fix, website users can now successfully click the drop down for the field to select a designation. Previously, the list of designations quickly appeared when clicking the drop down in IE10 or IE11, and the user could not select a different designation. This issue was introduced in Blackbaud Internet Solutions 4.0, Service Pack 5, 463584. | 543157 | All assemblies |
27 | |
| Previously, if you added a research list using a constituent selection, the research list would not populate with the selected constituents if a constituent revenue application smart field existed in the system. With this fix, the form saves and the list populates successfully. | 543078 | Blackbaud.AppFx.ProspectResearch.Catalog.dll |
95784 | 23 |
| This fix addresses a performance issue with the Donor list smart query and multicurrency. Previously, the Donor list smart query could take significantly longer to process when a non-organizational currency was selected. In addition, this fix also resolves an issue related to historic exchange rates and time zone information. Previously, an incorrect exchange rate could be used in revenue calculations when the transaction time was within the time zone offset of either the start or end date range of the exchange rate. | 543052 | All assemblies |
94143 | 27 |
| This fix addresses an issue where an error occurred when limited rights users searched for revenue not associated with an opportunity on the Opportunity Unassociated Revenue Search screen with search list security enabled. With this fix, the error no longer occurs. | 542145 | All assemblies |
95778 | 27 |
| This fix addresses an error that could sometimes occur when running an export process that used a selection as an output field. This happened when you created a selection from an ad-hoc query and selected the option to "Show this Selection in the Query Designer" on the "Set save options" tab of the query screen. If that selection was used as an output field in an export definition and you renamed the ad-hoc query the selection was based on, you would receive an error the next time you tried to use that export definition. Now, when you rename the ad-hoc query, the selection, as well as the export definition which used the selection, continue to work as usual. | 542138 | All assemblies |
95776 | 27 |
| This fix can help improve performance when opening certain uncommitted Enhanced Revenue Batches. Previously, when you opened a batch, it attempted to unnecessarily reload commitment information multiple times. Now, some of that information is cached so the batch does not have to reload it. | 541761 | All assemblies |
30 | |
| This fix addresses an issue with the marital status of constituents when using the "Global rules for married constituents" and "Global rules for deceased constituents" in the "Life changes" configuration task in Constituents. Previously, if you had configured the global rules to change a constituent's marital status automatically, there was an issue with a constituent's status of "Widowed" getting set back to "Married." This issue occurred when the relationship information between the spouses was changed or re-saved after the marital status was set to "Widowed." | 541503 | All assemblies |
82254 | 27 |
| New Feature/Technical Change: This fix improves the "Incremental Constituent Duplicate Search Process" located in Duplicates which you access from Constituents. Previously, two constituents with addresses that were almost identical were sometimes not seen as duplicates by the process. The issue occurred when one address included a five-character postal code and the other included the ZIP+4 postal code with all other address information matching exactly. To correct this issue, we added a new field to the "Custom settings" tab of the "Edit incremental duplicate constituent search process" screen. The "Number of characters to use for matching" field allows you to specify how many characters of the postal code to compare for the match criteria. The default for the new field is 12 but you can change it to suit the needs of your organization. If the value of this field is set to five, for example, the five-character postal code and the ZIP+4 postal code will now be seen as exact matches since only the first five characters are compared. A higher number represents a more stringent match criteria. The new POSTCODEPREFIXLENGTH column was added to the CONSTITUENTDUPLICATESEARCHPROCESS table to represent the new search process option field. The stored procedure USP_DATAFORMTEMPLATE_EDITLOAD_CONSTITUENTDUPLICATESEARCHPROCESS for the "Edit incremental duplicate constituent search process" screen now returns a value for POSTCODEPREFIXLENGTH. A new stored procedure USP_DATAFORMTEMPLATE_EDIT_CONSTITUENTDUPLICATESEARCHPROCESS_2 is now used to save the incremental duplicate search process settings. The stored procedure USP_CONSTITUENTDUPLICATESEARCHPROCESS_GETCONSTITUENTS now takes a new parameter POSTCODEPREFIXLENGTH when searching for possible duplicate constituents. If you have customizations for the incremental duplicate constituent search, you should consider implementing this new feature. | 541174 | All assemblies |
83328 | 27 |
| This fix improves a revision error to help you more easily identify the source of the problem for a certain scenario. When running revisions, you could encounter an exception error if an index on a custom code table was incorrect. Previously, the exception error language was generic. This fix has updated the exception message to provide more specific and clear details to help you identify the source of the issue. | 540702 | All assemblies |
27 | |
| This fix addresses an issue which occurred when attempting to view a public media effort in Marketing and Communications. Previously, if your browser language settings were set to anything other than "English (US)," you sometimes received the error "Input string was not in a correct format." | 540347 | All assemblies |
27 | |
| Previously, when you entered membership transactions into Blackbaud CRM through Blackbaud Internet Solutions, the Inbound channel field was blank. Now, information properly defaults in the Inbound channel field for membership transactions. | 538998 | All assemblies |
88816 | 27 |
| Previously, recognition credits did not default for memberships of new constituents created from the Membership Dues Batch. With this fix, recognition credits are created correctly. However, uncommitted batches generated through Import or downloaded from Blackbaud Internet Solutions will need to be imported or downloaded again. | 538989 | All assemblies |
88906 | 30 |
| This fix addresses an issue which occurred sporadically when opening a Membership Dues Batch. Previously, a user would sometimes receive the error "Expires on is required" when attempting to open the batch. | 538974 | All assemblies |
91220 | 30 |
| This fix addresses an issue that prevented organizations with duplicate matching gift conditions from merging. With this fix, these organizations now merge successfully. | 538963 | All assemblies |
92971 | 30 |
| This fix addresses an issue that occurred when you attempted to rejoin a canceled membership through Blackbaud Internet Solutions. Previously, when you changed a membership dues row in batch to rejoin a previous membership, the membership level and term adjusted incorrectly. | 538947 | All assemblies |
95154 | 32 |
| This change applies to an Enhanced Revenue Batch. Previously, when a user added a payment to a pledge or recurring gift and committed the batch, payment details (such as payment method) were not accurately reflected on the pledge or recurring gift record. With this fix, payment details are updated correctly. | 538705 | All assemblies |
95472 | 27 |
| This fix addresses an issue where the marketing information section on the Payment tab of a sponsorship would load incorrectly if the sponsor associated with the sponsorship had a finder number longer than 10 characters. This issue was due to the Finder number field having an incorrect data type which has now been updated so the Finder number field now displays finder numbers with more than 10 characters. | 538696 | All assemblies |
95470 | 27 |
| This fix addresses an issue where revenue queries using columns from the Recurring Gift Revenue Function History Query node did display data for those columns. Now, columns from that query node will display data correctly. | 538420 | All assemblies |
27 | |
| Previously, an error occurred when you attempted to edit the Revenue category field of a pledge payment when the pledge was linked to an opportunity. With this fix, you can now select a new revenue category, and the error no longer occurs. | 537457 | All assemblies |
95374 | 27 |
| This fix addresses an issue which occurred when adding a new public media group segment to a public media effort in Marketing and Communications. Previously, when you selected the segment for the effort from the Segment field, this list contained only segments that were not public media segments. When you selected a segment from the list, you then received an error when you tried to save the public media effort. | 536783 | All assemblies |
95335 | 27 |
| This fix ensures that audit tables are listed by size in Database Growth Management. Previously, the list of audit tables on the Audit Tables tab of the Database Growth Management screen were not arranged by size. With this fix, the audit tables are now listed by size, from largest to smallest. | 536586 | All assemblies |
95330 | 27 |
| This fix addresses an issue which occurred when editing responses for a prospect plan step. Previously, on the Details tab of a prospect plan, when you clicked "Step" and then "Responses" for a planned, pending, or completed step, you could receive an error which said that you did not have rights to access the "Edit responses" screen. The error occurred even when you did have rights to access the screen. The error no longer appears when you have rights to access the "Edit responses" screen. | 536348 | All assemblies |
95311 | 27 |
| This change applies to a Revenue Update Batch. Previously, when applying a payment to a pledge that overpaid the next installment, recognition credits were not saved correctly upon batch committal. With this fix, recognition credits are saved correctly. | 535963 | All assemblies |
95284 | 27 |
| This change applies to editing pledges. Previously, when making changes to the designation, installments, and distribution of amounts, the pledge did not save the changes and an error message appeared. With this fix, we updated the "save" handler on the Edit Installment Designations form to ensure that the correct value is saved. | 535957 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Fundraising.UIModel.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1500.dll |
95279 | 23 |
| This fix addresses an issue with designations displayed on the Installment/Write-off Activity tab of a pledge. Previously, if a pledge was set up with multiple designations, all of the designations were displayed for installments even when the payment was not actually applied to each designation. Now only the designations associated with each payment are displayed. | 535943 | All assemblies |
95274 | 32 |
| This fix addresses an issue where an error occurred when you added a payment with the payment method of Other to a recurring gift in an Enhanced Revenue Batch. | 535919 | All assemblies |
95270 | 27 |
| New Feature: We have added the ability to query on recurring gift status activity in revenue queries. We have added the "Revenue>Recurring Gift Amendments" node to revenue queries with the "Recurring gift previous status," "Recurring gift status," "Recurring gift status change reason," and "Recurring gift status change reason description" fields. You can edit existing queries to include these new fields. | 535834 | All assemblies |
95265 | 30 |
| This change applies to the "Constituent revenue application amounts" smart field. Previously, the smart field was not updated with constituents recently added to the site associated with the smart field configuration. When a constituent was added to the site after the smart field process ran, the smart field value was not added to that constituent's page. With this fix, the smart field is checked for any constituents that have been added to the site since the process last ran. | 535445 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1500.dll |
95223 | 23 |
| Previously, when you replaced a manager for a prospect on the Prospect Team tab, an overlapping dates error sometimes occurred that prevented you from replacing the prospect manager, even if the start date of the new manager did not overlap with the previous manager. With this fix, the error no longer appears. | 533530 | All assemblies |
95064 | 27 |
| This fix addresses an issue that sometimes occurred with custom collection fields. Previously, some custom collection fields did not display on forms when you accessed them using Chrome as a browser. This happened when the fields used a <span> element for field mapping. With this fix, custom collection fields now display correctly in Chrome. | 533436 | All assemblies |
95053 | 27 |
| This fix addresses an issue which occurred when entering a payment with multiple applications and at least two additional applications, each with an amount of zero, in an Enhanced Revenue Batch. Previously, you received a "You must have at least one application" exception message when you validated the batch. | 533229 | All assemblies |
95041 | 30 |
| This fix addresses an issue when identifying loyal donors in the Blackbaud Data Warehouse. You define loyal donors by editing donor constituency criteria under "Constituencies" in the Constituents functional area. Previously, in the Blackbaud Data Warehouse, constituents were only identified as loyal donors when they had given for exactly the amount of time you defined, but not if they had given for more than that time. For example, if you defined loyal donors as those constituents who have given for three consecutive years, the Blackbaud Data Warehouse only identified as loyal donors those constituents who had given for exactly three years, but did not include constituents who had given for more than three years. With this fix, donors who have given for the length of time you define or longer are correctly identified as loyal donors. In the previous example, donors who have given for three years or more would be identified as loyal donors. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 533046 | All assemblies |
95017 | 27 |
| With this fix, we improved the performance of the following EFT processes: Generate payments, Generate direct debit files, and Credit card processing. | 532454 | All assemblies |
94979 | 27 |
| Previously, in an Enhanced Revenue Batch, an error may have displayed when applying payments (with a payment method of credit card) to commitments. With this fix, the error no longer displays. | 532350 | All assemblies |
94974 | 27 |
| This fix addresses a usability issue with smart fields listed on the "Assign smart fields" screen used to assign rights to the smart fields to the system role. Now, these smart fields are sorted alphabetically which helps make a long list of smart fields easier to navigate. | 532237 | All assemblies |
94962 | 30 |
| This change applies to an Enhanced Revenue Batch. Previously, when a user entered revenue in a batch row, entered an amount, and selected an appeal with no benefits, then went back and changed the Amount field, the Receipt amount field was not updated. With this fix, the Receipt amount field updates when a change is made to the Amount field. | 532144 | All assemblies |
94945 | 27 |
| This fix addresses an issue where child campaign goals were incorrectly displayed in queries. Now, query results no longer list goals that existed before a campaign was added to a hierarchy. | 531223 | All assemblies |
94836 | 27 |
| This fix addresses an error that occurred when a constituent sponsoring a child signed up as a new BBIS user if the constituent was automatched with an existing constituent in Blackbaud CRM. With this fix, this error no longer occurs. | 531126 | All assemblies |
94831 | 21 |
| New Feature: To provide an optimal check out experience for website users on multiple devices, you can now upgrade your static Blackbaud secure payment web pages to responsive web pages. You can select to upgrade each secure payment page individually, or you can upgrade all pages, across all of your websites, at the same time. After you select to upgrade Blackbaud secure payment pages from static to responsive, you cannot use static pages again. | 531051 | All assemblies |
27 | |
| This fix addresses an issue where users sometimes received an error message when running the R68 process. With this fix, the error no longer displays. | 530899 | All assemblies |
94810 | 27 |
| This fix addresses an issue when granting task permissions on system roles. Previously, when you were granting task permissions, you could sometimes see features on the list that you could not grant permissions to. Those features are no longer visible to eliminate confusion when selecting features to grant permission to. | 530759 | All assemblies |
94800 | 27 |
| New Feature: From Administration, Sites & settings, you can now select 'This is a non-production environment' when you want to test or disable specific functionality in an environment that is not available to website users and email recipients. When this checkbox is clear, your environment is live and set to Production. | 530367 | All assemblies |
27 | |
| This change applies to an Enhanced Revenue Batch imported using the Additional applications collection field. Previously, when the collection field was mapped to a single application, recognition credits were incorrectly cleared. With this fix, recognition credits remain. | 529961 | All assemblies |
94742 | 21 |
| Previously, for a Revenue Update Batch, the Revenue category was blank when loading multi-designation recurring gifts and pledges. With this fix, we changed the load stored procedure for Revenue Update Batch to return a Revenue category for these types of gifts. The Revenue category now loads correctly. | 529870 | All assemblies |
73881 | 21 |
| This fix resolves an issue with the Online Information tab in Blackbaud CRM. Previously, the tab did not display an imported website user's lasts login date from your Blackbaud Internet Solutions website. With this fix, the date now displays in the Last login field for all imported website users, as well as registered website users. To resolve this, the USP_BBNC_INTEGRATIONWEBTRAFFICADDUPDATE stored procedure has been updated in the back end. | 529438 | All assemblies |
94698 | 27 |
| New Feature: With CRM 4.0 Service Pack 6, we introduce Credit Card Updater Service - a subscription service that helps you maintain accurate credit card data for your recurring gifts, pledges, and membership installment plans. To use Credit Card Updater, your organization must subscribe to the Credit Card Updater Service and have an active Blackbaud Merchant Services account. Within CRM, features include an option to enable or disable the Service, a new business process and query, and a new revenue record field that indicates when the associated credit card was last updated. For more information about subscribing to Credit Card Updater, contact Blackbaud Merchant Services at bbms@blackbaud.com. | 529408 | All assemblies |
27 | |
| This fix addresses a formatting issue in import exception files. Previously, data in import exception files sometimes showed no spaces between fields. This happened when the file you imported was a fixed-width file. | 528688 | All assemblies |
94649 | 27 |
| This fix optimizes performance when high volume donations impact a Payment 2.0 part using the Blackbaud secure payments checkout process. This fix also improves the process when a website user clicks the back button on the secure payment web page by maintaining the user's dbo.CMS_SessionVariableBackup row in the back end until the transaction processes successfully. Previously, this row was deleted when the user clicked the back button. These changes apply to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 528644 | Blackbaud.AppFx.ContentManagement.Parts.ShoppingCart.UI.dll Blackbaud.Web.Content.Core.dll |
19 | |
| This fix addresses an issue where users received an error when attempting to edit a child or project record in a sponsorship opportunity group that allowed unlimited sponsors. With this fix, the error no longer displays. | 528321 | All assemblies |
94610 | 27 |
| This fix addresses an issue that could lead to blank exception batches as a result of General Ledger errors in Enhanced Revenue Batches. Previously, legitimate errors could fail to appear in exception batches if a batch's required fields became out of sync with the batch template's required fields. This could lead to empty exception batches even though there were exceptions that should have appeared. This could happen when you modified a batch template after a batch had been created based on that template. If you changed the required fields on the template but the batch was created before those changes, the required fields on the template and on the batch would become inconsistent and exceptions could fail to appear on the exception batch. | 527975 | All assemblies |
94541 | 27 |
| This fix addresses an issue with start dates for Gift Aid declarations in databases using the UK locale. Previously, when you downloaded donations from Blackbaud Internet Solutions, the start date was set to the date you completed the download instead of the date the gift was given. With this fix, the date correctly indicates when the gift was given and the declaration completed. | 527797 | All assemblies |
27 | |
| This fix addresses an issue where the Committee Summary tab was being displayed for constituents who were not committees. | 527727 | All assemblies |
94525 | 27 |
| We have optimized the ETL by changing when the clustered index is added to fact tables during full refreshes. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 527620 | All assemblies |
94516 | 27 |
| This change applies to an Enhanced Revenue Batch. Previously, after importing a payment applied to a constituent's commitment where the constituent was different than the one imported into the batch row, the Application and Applied amount fields were blank. With this fix, the field information displays correctly. | 526372 | All assemblies |
94444 | 27 |
| New Feature: This fix addresses an issue with event invitees and the Constituents query. Previously, you sometimes got incorrect results when you used the "Constituents>Invitee>Name" field for output in addition to the "Constituents>Invitee>Event>Invitations>Name" filter to query on invitees from a specific invitation list. The issue occurred because all invitees were included in the results regardless of the invitation, even when a specific invitation was specified as a filter. Now, we have added the ability to query on event invitees by invitation lists in constituent queries. You can use the new "Constituents>Invitees" node which can sort or filter the results by invitation list. If you have any existing queries using the "Constituents>Invitee" node and you would like to sort or filter by invitation list, you should modify them to use the new "Constituents>Invitees" node. | 525927 | All assemblies |
94412 | 30 |
| This fix resolves an issue for multiple event registrations on your event web page. When one event is sold out, the event capacity message no longer appears for additional events with available registrations. With this fix, online registrants can continue to process these registrations successfully. To resolve this, the CartDisplay.ascx.vb file has been modified in the back end. This fix applies to the Event Registration Form part for Blackbaud Internet Solutions and to the Event Registration Form (Classic) part for Blackbaud NetCommunity. | 525849 | All assemblies |
94390 | 27 |
| This fix optimizes performance of the ETL process in the Blackbaud Data Warehouse. To improve performance of the FACT_FINANCIALTRANSACTIONLINEITEM ETL package, we have optimized the indexes for the FACT_FINANCIALTRANSACTIONLINEITEM_STAGE table. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 525205 | BBDW.ServiceRevisions.dll BBDWETL - SSIS Reporting Package |
19 | |
| This fix resolves an issue that sometimes caused external links in emails you sent from Messages to redirect to the website's home page instead of their destinations. The issue occurred when your website also used acknowledgement emails that included links. The problem was introduced by a change in Blackbaud Internet Solutions 4.0 Service Pack 3, 464025 and Blackbaud NetCommunity 6.64 Maintenance Release, 464025. This change resolves the current and previous issues. | 525167 | Blackbaud.Web.Content.Core.dll |
94919 | 18 |
| This fix allows you to schedule SQL Snap to run automatically on system startup. For more information, see Knowledgebase solution 54657 at https://kb.blackbaud.com/articles/Article/54657. | 525092 | All assemblies |
94356 | 21 |
| This fix helps improve performance issues when refreshing static queries. The fix also helps improve performance in queries which contain smart fields that use value groups. | 525072 | All assemblies |
94352 | 32 |
| This fix addresses an issue with the Event Profile report. Previously, constituents who received an event invitation and declined were sometimes listed as "Did not respond" instead. The issue occurred when the constituent was sent more than one invitation to the same event and the constituent declined the most recent invitation. Now, a constituent's event invitation status is listed according to the response to the most recent invitation. If a constituent declined a previous invitation to an event but did not respond to a more recent invitation, the constituent is considered "Did not respond." Note that constituents are considered "Registered" if they register for any invitation to the event, regardless of how they respond to the most recent invitation. | 525033 | All assemblies |
94350 | 30 |
| This fix addresses an issue that could make some queries intermittently slow when you opened or edited them. | 524836 | All assemblies |
94334 | 27 |
| This fix addresses an issue with batch actions. Previously, you sometimes could not see the actions that normally appear underneath each query on the Batch Entry screen in Revenue. When you filtered one of the columns on this page, you sometimes were not able to see the actions for each batch, such as "Edit batch" and "Commit." With this fix, the actions appear correctly for all batches, even when you filter the list by column. | 523808 | All assemblies |
94280 | 21 |
| This fix removes unnecessary message from the ETL log file. Because this reduces the size of the log file, you might notice performance improvements during the ETL process. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 523799 | Blackbaud.AppFx.ReportDB.BuildTasks.dll Blackbaud.AppFx.ReportDB.Config.dll |
83343 | 19 |
| Technical Change: Previously, the Results per session field on the Sponsorship Search Part was limited to 50 results. With this fix, there is no longer a limit to the amount of results on this field. | 523708 | Blackbaud.AppFx.Sponsorship.ContentManagement.dll Blackbaud.Web.Content.PluginService.dll Blackbaud.Web.Content.Portal.dll |
19 | |
| This change applies to an Enhanced Revenue Batch. Previously, when a user entered revenue in a batch row, entered an amount, and selected an appeal with no benefits, then went back and changed the Amount field, the Receipt amount field was not updated. With this fix, the Receipt amount field updates when a change is made to the Amount field. | 523584 | All assemblies |
94262 | 27 |
| This fix resolves an issue that caused an error message to appear when website users attempted to register for team fundraising events. | 523426 | Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll Blackbaud.Web.Content.Portal.dll |
17 | |
| Previously, in a Revenue Update Batch, an error displayed upon validation if the batch contained a payment for a matching gift claim whose constituent had been changed. With this fix, the error no longer occurs and the batch validates correctly. | 523389 | All assemblies |
94241 | 27 |
| We have updated the Blackbaud Data Warehouse to correctly calculate first gift information in the Giving List report. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 523290 | All assemblies |
94233 | 27 |
| This change applies to settings on the Goal tab for new KPI instances. Previously, when "Good target" and "Satisfactory target" were set to the same value and "High values are good" was selected, the KPI graph and tooltips indicated "Low values are good". With this fix, the KPI displays correct data. | 523227 | All assemblies |
91368 | 21 |
| This fix addresses an issue that sometimes occurred when navigating through folders in the Information Library. Query and KPI folders contain up to 30 queries or KPIs per page. When a folder has more than 30 queries or KPIs, the folder expands to more than one page. Previously, when you navigated from one query folder to another or from a KPI folder to another, the contents of the second folder could sometimes appear blank even when the folder had items in it. This happened when you navigated from a page in the first folder that did not exist in the second folder. For example, if you were viewing the third page of a query folder and then navigated to a query folder that only had two pages, the second query folder appeared blank until you refreshed the list. With this fix, when you navigate from one folder to another, you always see the first page of the second folder, regardless of what page of the previous folder you were viewing. | 522717 | All assemblies |
94181 | 21 |
| Technical Change: This fix addresses an issue with the Appeal Profile report. Previously, this report treated recurring gifts and recurring gift revenue inconsistently with regard to which transactions were included in the Revenue Detail as well as in the Revenue Summary sections of the report. The function "UFN_REPORT_APPEALPROFILE_REVENUE" was changed to include a new "INCLUDEINSUMMARY" field to indicate which revenue should be included in the Revenue Summary section of the report in the "Total revenue", "Number of transactions," and "Number of donors" summary fields. With this fix, the Revenue Details section of the Appeal Profile report now includes recurring gift amounts for both recurring gifts and for recurring gift revenue transactions. The Revenue Summary section of the report includes only recurring gift revenue transactions. After you upgrade, the numbers in the Revenue Summary section may no longer match the previous summary totals. This fix addresses issues reported in 517020 and 522595. | 522595 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
94165 | 19 |
| This fix addresses an issue that sometimes happened on the Segments list in Marketing and Communications. Previously, when you accessed segments on this page, you sometimes did not see the actions that appear underneath each segment, such as "Edit" and "Delete." With this fix, the actions appear correctly for all segments on this list. | 522560 | All assemblies |
94154 | 21 |
| Previously, the median price was used to calculate a stock sale which, at times, caused revenue amounts to be different than the associated General ledger amounts. With this fix, we changed stored procedures to ensure the stock sale calculation is based on the payment amount. | 522541 | All assemblies |
94150 | 27 |
| This fix addresses an issue with the capitalization of constituent names being changed incorrectly in Constituent Update Batch. Previously, if you selected an existing organization, for example, with a name that included all capital letters (such as "AAA Concrete"), the batch could use the "Global data entry settings" from Administration to potentially update the organization name to having only the initial letter capitalized (such as "Aaa Concrete"). The issue could also occur when you imported existing constituents into a Constituent Update Batch. Now when you select an existing constituent or import one into a Constituent Update Batch, the "Global data entry settings" are not automatically applied to the "First name" and "Last/Org/Group/Household name" fields and the capitalization of the existing name in these fields is not changed. If you edit the name of the constituent in these fields, the settings are applied and the capitalization could be changed. | 522402 | All assemblies |
94141 | 27 |
| Previously, in a Revenue Update Batch, when a payment was split between a donation and a pledge and the batch was saved and reopened, the designation was not visible on the Apply to commitments screen. With this fix, the designation appears correctly. | 522145 | Blackbaud.AppFx.Fundraising.UIModel.dll Blackbaud.Web.Content.Common.dll Blackbaud.Web.Content.Core.dll |
94121 | 15 |
| This fix addresses an error which occurred when running the receipt process. Previously, if a constituent had more than one address of the same type, the receipt process sometimes encountered an error when trying to determine which address was the correct one to use. | 521829 | All assemblies |
27 | |
| New Feature/Technical Change: With the CRM 4.0 release, we introduced constituent summary tiles to offer quick views of constituent information such as contact information, relationships, and memberships. With Service Pack 4, we introduce a more streamlined way to create and deploy new constituent tiles. For more information, see the SDK documentation. If you already created custom constituent tiles on version 4.0 prior to Service Pack 4, your customizations will continue to work after you upgrade; however, we recommend you plan to upgrade your custom tiles to take advantage of the streamlined tile development and deployment process. | 521660 | Blackbaud.AppFx.AddressValidation.Server.dll Blackbaud.AppFx.Browser.exe Blackbaud.AppFx.Browser.exe Blackbaud.AppFx.Browser.exe Blackbaud.AppFx.Browser.ImageLibrary.dll Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Constituent.Common.UIModel.dll Blackbaud.AppFx.Constituent.UIModel.dll Blackbaud.AppFx.Deployment.exe Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Platform.Catalog.dll Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Platform.UIModel.dll Blackbaud.AppFx.ReportDB.Installer.exe Blackbaud.AppFx.Reports.Deploy.exe Blackbaud.AppFx.Server.dll Blackbaud.AppFx.SpWrap.dll Blackbaud.AppFx.SqlClr.SpWrap.dll Blackbaud.AppFx.XmlTypes.dll CreateDB.exe |
19 | |
| This fix addresses an issue with Constituent Update Batch when the batch included phone numbers or email addresses. Previously, the duplicate matching logic did not always detect an exact match for the constituent's phone number or email address and treated it as a new entry. Now the existing phone number or email address is detected and the batch is able to validate and commit properly. | 521088 | All assemblies |
92079 | 21 |
| This fix addresses an issue with certain fields in the Blackbaud Data Warehouse. After applying Service Pack 3 for version 4.0 of Blackbaud CRM, some fields in the ETL were not updated. The fields affected were bbdw.FACT_FINANCIALTRANSACTION.TRANSACTIONBALANCE, bbdw.FACT_FINANCIALTRANSACTION.INSTALLMENTCOUNT, bbdw.FACT_FINANCIALTRANSACTIONLINEITEM.TRANSACTIONBALANCE, and bbdw.FACT_FINANCIALTRANSACTION.LINEITEMBALANCE. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete a full refresh. | 520725 | BBDW.ServiceRevisions.dll BBDWETL - SSIS Reporting Package Blackbaud.Web.Content.Common.dll Blackbaud.Web.Content.Core.dll |
92966 | 14 |
| Previously, in an Enhanced Revenue Batch, when a constituent was automatically matched to an existing record, their recognition credits were duplicated. With this fix, recognition credits are correctly re-defaulted (not duplicated) after the constituent is matched. | 520271 | All assemblies |
92962 | 27 |
| This fix resolves an issue that caused the benefit screen for a membership form to not include decimal digits when the benefit value is a whole number. | 520261 | Blackbaud.Web.Content.Portal.dll |
19 | |
| This fix addresses an issue with queries when using Google Chrome as your browser. Previously, you sometimes did not see the action options underneath queries in the Information Library. This occurred when you used Chrome and searched for queries using the search box in the Information Library. After your results appeared, you were not able to see the actions, such as "Edit" and "Delete," underneath the query name. You were still able to access those actions by right-clicking on the query name. With this fix, the actions appear correctly underneath the query name. | 519669 | All assemblies |
92924 | 21 |
| New Feature: We have added a new field in queries for masked account numbers. The existing field "Account number" on the "Direct Debit Account" node in queries displays the entire account number. When used in printed materials such as acknowledgement letters, this could result in security issues if an entire account number is included. To offer an alternative, we have added the field "Account number (masked)," which masks the account number except for the last four digits (for example, ****5678). To take advantage of this new field in existing queries that include account numbers, you must edit the queries and change the selected field from "Account number" to "Account number (masked)." You can continue to use the "Account number" field for situations in which you want the entire account number to appear. | 519495 | All assemblies |
27 | |
| This fix addresses an issue where solicitors on a prospect plan appeared twice on payments linked to an opportunity associated with the prospect plan. | 519095 | All assemblies |
92108 | 27 |
| Previously, when opening a revenue batch that was committed prior to upgrading to version 4.0, the following error message displayed: "The given key was not present in the dictionary." With this fix, the error no longer displays. | 518884 | All assemblies |
92070 | 27 |
| The default field label that appears for the image prompt on eCard forms that include reCAPTCHA images is changed. Previously, the label instructed users to "type the words" shown in the reCAPTCHA image. Since the images typically include characters that do not form words, the text now informs them that the image is "a security measure to help prevent fraud." To change the new default message, navigate to the Language tab on the part, select the reCAPTCHA category, and update the text in the "Subheading" row. A similar change was made in the 6.64 Maintenance release for the Donation Form, Payment, Payment 2.0, and User Login parts. | 518795 | Blackbaud.Web.Content.Portal.dll |
19 | |
| This fix addresses a performance issue with committing membership dues batches when benefits are awarded to new memberships. With this fix, the commitment time for these membership dues batches has been reduced. | 518648 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
90822 | 19 |
| This fix eliminates the error message 'Could not download transaction with ID 999. The error was: String was not recognized as a valid DateTime' that appeared when a website user attempted to submit a profile update on your Blackbaud Internet Solutions website. This was caused by email addresses that use a start or end date with the date format dd/mm/yyyy. With this fix, the dates for an email address now save properly when your organization's web server settings are set to dd/mm/yyyy so profile transactions successfully process to Blackbaud CRM. | 518469 | All assemblies |
92023 | 21 |
| This fix helps improve a performance issue which occurred sporadically when adding a single payment using a finder number. Previously, if a direct marketing effort was in the process of being activated, adding a single payment using a finder number could time out or take a long time to process. | 518294 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| This fix addresses an issue were you previously could not enter a date of birth for new user registrations in the standard date formats for Finland (dd.mm.yyyy) and Germany (dd-mm-yyyy) in Blackbaud Internet Solutions. Also, date of birth values did not appear in sign up transactions in Blackbaud CRM if Blackbaud CRM was set to a different culture than Blackbaud Internet Solutions. | 517949 | All assemblies |
91988 | 27 |
| This fix addresses an issue which occurred when adding media links, attachments, or interactions from the "Documentation and Interactions" constituent summary tile for a group or household. Previously, the add screens that appeared were the ones for adding those items to individual constituents and not groups. Therefore they did not include the "Constituent" field so that you could select whether the item was for the group/household or for a specific constituent in the group/household. Adding notes from the "Documentation and Interactions" constituent summary tile worked correctly. Now adding media links, attachments, and interactions correctly uses the group version of the add screens which includes the "Constituent" field. | 517719 | All assemblies |
91975 | 27 |
| Previously, adjusted pledges were incorrectly calculated on the Donor Information tab of a purpose record. With this fix, adjusted pledges are calculated correctly. | 517717 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Fundraising.UIModel.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| This fix addresses an issue where users attempting to view posted pledges that had been adjusted multiple times resulted in the data list being unable to load. | 517715 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Fundraising.UIModel.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
89347 | 19 |
| This fix addresses an error that occurred when committing a Membership Dues Batch that included a donor who purchased a membership via the BBIS membership part and was auto-matched to a constituent in Blackbaud CRM with an expired membership in the same program of the online purchase. | 517443 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Membership.Catalog.dll |
89286 | 19 |
| New Feature: To satisfy the Canadian Revenue Agency's requirements for donation receipts, the Donation Form, Payment, and Payment 2.0 parts in Blackbaud Internet Solutions now include the Middle name field under Additional fields. | 517407 | Blackbaud.AppFx.BBNCSvc.dll Blackbaud.AppFx.CMS.FCL.ShoppingCart.BaseClassLibrary.dll Blackbaud.AppFx.ContentManagement.Parts.ShoppingCart.UI.dll Blackbaud.Web.Content.Core.dll |
19 | |
| This fix eliminates an issue with decimal amounts for international customers who use the Membership Form part. Membership installment amounts now display correctly. Previously, installment amounts that included a decimal were displayed in US format. | 517377 | Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
19 | |
| This fix resolves an issue that prevented the files for the 6.64 version of the product from installing on 32 bit systems. | 517348 | Blackbaud.Web.Content.Core.dll |
17 | |
| This fix addresses a performance issue when upgrading your database to Blackbaud CRM version 4.0 and above. Previously, the database upgrade process was slower than expected. With this fix, performance has been improved. | 517209 | Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.SqlClr.dll |
19 | |
| Technical Change: This fix addresses an issue with the Appeal Profile report. Previously, this report treated recurring gifts and recurring gift revenue inconsistently with regard to which transactions were included in the Revenue Detail as well as in the Revenue Summary sections of the report. The function "UFN_REPORT_APPEALPROFILE_REVENUE" was changed to include a new "INCLUDEINSUMMARY" field to indicate which revenue should be included in the Revenue Summary section of the report in the "Total revenue", "Number of transactions," and "Number of donors" summary fields. With this fix, the Revenue Details section of the Appeal Profile report now includes recurring gift amounts for both recurring gifts and for recurring gift revenue transactions. The Revenue Summary section of the report includes only recurring gift revenue transactions. After you upgrade, the numbers in the Revenue Summary section may no longer match the previous summary totals. This fix addresses issues reported in 517020 and 522595. | 517020 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| This fix addresses an issue with direct marketing email jobs. Previously, the time specified on the "Start email job" screen was ignored so an email job set up to be sent at any time on a given date was sent at midnight on that date. If you scheduled a job for a later time in the same day, the email job was processed immediately. | 516819 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Marketing.NetCommunityIntegrationCatalog.dll Blackbaud.AppFx.Marketing.UIModel.dll |
91344 | 19 |
| This fix improves a performance issue where the BBIS Sponsorship Search part would perform poorly and occasionally time out when multiple requests were made to the page in a short period of time. | 516581 | All assemblies |
91310 | 21 |
| Previously, users received an operation time-out message when viewing the Revenue History tab with a revenue filter. With this fix, we made performance improvements to ensure the error no longer appears. | 516474 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Fundraising.UIModel.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
741198 | 19 |
| New Feature: We have added some address-related enhancements to PeopleFinder to help fix an issue with new addresses for constituents found by the PeopleFinder process. Previously, if the constituent already had an address in CRM marked as "Primary" and PeopleFinder returned a new address for the constituent, the primary address in CRM was no longer marked as primary and the address type was set to "PeopleFinder-former." The new address from PeopleFinder was added to the constituent and was marked as "Primary." In order to offer more flexibility, we have added some additional options to the Edit PeopleFinder process options screen. On this screen, you can now choose whether or not to add new addresses from PeopleFinder to constituents at all. If you do, you can select the address type and information source to use for the new addresses. You can also choose the address type to use for the former primary addresses for constituents. In addition, you can choose whether or not to make the new addresses from PeopleFinder the primary ones. In order to support these changes, the PEOPLEFINDER process table in the CRM database has been updated with these additional columns: UPDATEADDRESS, OLDADDRESSTYPECODEID, NEWADDRESSTYPECODEID, NEWADDRESSINFOSOURCECODEID, and MARKADDRESSASPRIMARY. Existing PeopleFinder processes will remain unchanged; however, the Edit PeopleFinder process options screen will have the new options. If you want to take advantage of these changes, you can edit the existing PeopleFinder process options. | 516404 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.PeopleFinder.Catalog.dll Blackbaud.AppFx.PeopleFinder.UIModel.dll |
19 | |
| Technical Change: This fix resolves an issue with date attributes on the Donation Form part on a Blackbaud NetCommunity web page. When you process these to The Raiser's Edge, the program now changes the format to a short date so the transactions download successfully. | 516337 | Blackbaud.Web.Content.Portal.dll |
12 | |
| This fix addresses a formatting issue with export files that include year fields. Previously, when you generated an export file in .xlsx format that included a year field such as "Class of," the formatting for the year could be incorrect because the export handled it as a number instead of a year. Depending on your locale settings, years could appear in your export output with additional characters such as thousand separators. | 515786 | All assemblies |
83020 | 21 |
| This fix optimizes the processing of the ATTRIBUTEISCURRENT flag in the Blackbaud Data Warehouse. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 515511 | BBDW.ServiceRevisions.dll BBDWETL - SSIS Reporting Package |
74234 | 19 |
| This fix eliminates an issue with decimal amounts for international customers who use the Event Registration Form part for Blackbaud NetCommunity. When a website user progresses through the event steps for the part on a web page, amounts that include a decimal are no longer multiplied by 100. With this fix, amounts accurately reflect the exact amount the user entered and also process correctly to Blackbaud Raiser's Edge. | 515503 | Blackbaud.Web.Content.Portal.dll |
19 | |
| This change fixes the SQL 2008 revision error for Blackbaud NetCommunity version 4.0 Service Pack 2. | 515362 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This fix addresses an issue with degree and program information for non-affiliated educational institutions not appearing correctly on the Education tab of a constituent record. | 515113 | All assemblies |
90922 | 21 |
| This fix addresses an issue in Enhanced Revenue Batch which occurred when you changed the constituent after you entered the payment application and designation information for the transaction. Previously, the application and designation information was removed from the row when you changed the constituent. | 515091 | All assemblies |
90916 | 21 |
| Previously, when you assigned seats for an event, if you chose to sort the list of registrants by the Name, Host, Group, Guest count, or Seat columns, sort order was lost when you assigned a registrant to a seat. With this fix, sort order is now maintained when you assign seats. | 515071 | All assemblies |
90914 | 27 |
| Previously, when a prospect manager, primary manager, or secondary manager appeared consecutively, the history was deleted even if the dates did not overlap. With this fix, the history of consecutive managers without overlapping dates are retained correctly. If dates do overlap, and the new manager does not have an end date, the history deletes and the current manager's start date will default to the start date of the latest history that overlapped. If the newest manager's dates overlapped with the latest history, and an end date exists, the history record will be updated with the end date you previously entered. | 515052 | All assemblies |
90902 | 27 |
| This fix addresses an issue with deleting a merged constituent record associated with a PeopleFinder batch. Previously, if you merged two constituent records and the source constituent was in a PeopleFinder batch, you received an error if you tried to delete the source constituent. This occurred because the PeopleFinder batch still referenced the source constituent record. Now, the PeopleFinder batch is updated when you merge the constituents so that it references the target constituent instead and you can successfully delete the source constituent record. | 515042 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| Technical Change: This fix eliminates the error message 'Input string was not in a correct format' when your web server uses a culture setting that formats currency different than the United States. As a result of this resolution, currency amounts now display in the language format selected by the website user. This change applies to Blackbaud Internet Solutions and Blackbaud Netcommunity. | 514947 | Blackbaud.Web.Content.Portal.dll |
12 | |
| This fix addresses an issue where the Opportunities tile would not refresh after adding a prospect plan to a constituent group or household. | 514558 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll |
19 | |
| This fix addresses an inconsistency with the way the primary manager was displayed on a prospect plan. Previously, former managers were displayed as current on the Opportunities tile and the Prospect Plan List View. | 514556 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.MajorGiving.Catalog.dll |
19 | |
| Previously, for the Household revenue dates smart field, when "Earliest date" or "Latest date" was selected in the Value to return field, incorrect values displayed for all households after records were processed. With this fix, the values display correctly. | 514538 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Fundraising.UIModel.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
89002 | 19 |
| This change applies to editing a posted payment with associated gift fees. Previously, upon saving the edit, the following message appeared: "The adjustment reason must be set if the payment is being adjusted." After the user clicked OK, the adjustment fields were disabled even though, in some cases, they were required for a successful edit. With this fix, the message still appears, but after clicking OK, the fields are enabled and the payment can be saved. | 514393 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Fundraising.UIModel.dll |
90827 | 19 |
| Technical Change: We have changed the way revenue is calculated for marketing efforts. Previously, if someone made a pledge payment and included an additional donation associated with an appeal on a marketing effort, the pledge payment portion was also included in the totals toward the marketing effort. Now, in this situation, only the additional donation is counted. You must refresh your marketing efforts that may contain pledge payments in order to take advantage of the updated calculation. | 514264 | Blackbaud.AppFx.Marketing.Catalog.dll |
79863 | 19 |
| New Feature/Technical Change: With this release, Blackbaud CRM 4.0 Service Pack 5 now requires .NET 4.5.2 to support the Transport Layer Security (TLS) 1.2 protocol for enhanced communication security over the Internet. Before you upgrade, you must upgrade all servers that run any component of Blackbaud CRM (such as database and web servers) to .NET 4.5.2. If you have any customizations, they will continue to work after the upgrade. However, if you edit a customization or create a new one, you must update the target framework in the project properties to use .NET 4.5.2 before you recompile the customization. For more information, see the SDK new features information at https://www.blackbaud.com/files/support/guides/infinitydevguide/infsdk-developer-help.htm#../Subsystems/new-features-developer-help/content/newfeatures/4.0/sp5_netupgrade.htm. | 514051 | All assemblies |
21 | |
| This fix addresses an issue which sometimes occurred when changing the application of a payment in a Revenue Update Batch. Previously, if the revenue transaction had an appeal that was associated with business units, if you changed the application in a Revenue Update Batch, you could receive an error message. Now, the business unit information is reset whenever you update the revenue’s application and the error no longer occurs. | 513743 | All assemblies |
97651 | 32 |
| This fix addresses an issue which occurred when importing new constituents into a Sponsor Batch. The issue occurred only when you have Address Validation in the Data Tune-Up section of Administration. Previously, when you added constituents by importing them into a Sponsor Batch, the "Omit from validation" checkbox for the constituent's address was always marked. If you added constituents manually to the Sponsor Batch, the checkbox for the address was not marked by default. Now, in either situation, the "Omit from validation" checkbox for the address is not marked by default, which is consistent with adding or importing constituents in Enhanced Revenue Batch. | 513610 | All assemblies |
90761 | 30 |
| This fix addresses an issue when using the query "Constituents (from the Blackbaud Data Warehouse)." Previously, when you used the field "Educational Program" for the query results, you received an error and were not able to see the results of the query. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse. | 513293 | Blackbaud.AppFx.BBDW.Query.Catalog.dll |
90725 | 12 |
| This change applies to the "Constituent revenue application counts" smart field with a specific number of years for consecutive giving. Previously, after the smart field processed, results displayed the total number of years of consecutive giving instead of the number specified in the smart field. With this fix, results reflect the correct timeframe from the smart field even if the actual number of giving years exceeds that timeframe. | 513268 | All assemblies |
90728 | 27 |
| This fix addresses an error that could occur when you saved queries without a static selection. If you had the Blackbaud Data Warehouse deployed and you selected the option to copy static selections, saving a query without a static selection resulted in an error in your event log for the web server. In addition, if your web server were running .Net version 4, your web server could crash as a result of this error. With this fix, saving a query without a static selection no longer results in an error in your event log. In the event of a legitimate error, we have also updated the background task on the event log to prevent issues with .Net version 4. | 513166 | Blackbaud.AppFx.Server.dll |
90720 | 19 |
| This fix eliminates an issue with decimal amounts for international customers who use the Membership Form part. Membership prices now display and process correctly. Previously, amounts that included a decimal were multiplied by 100. | 513085 | Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
12 | |
| Previously, when any revenue was loaded into a Revenue Update Batch with an associated note, errors displayed. With this fix, we updated the code that loads the Revenue Update Batch and the errors no longer display. | 512960 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
90669 | 19 |
| This fix addresses an issue that could sometimes cause Gift Aid refunds to be processed more than once. When you edit a processed payment made to a designation that qualifies for Gift Aid and change the designation to one that does not qualify for Gift Aid, the Gift Aid amount needs to be refunded and the refund information needs to be included the next time the R68 process runs. Previously, this process worked correctly. However, if you opened the payment record and saved it again after the initial refund was included in the R68 file, the refund was added again. This could result in multiple refunds for the same transaction. With this fix, the refund is only added once, even if you open and re-save the payment record. | 512909 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| This fix improves a performance issue which sometimes occurred when merging two individual constituents with the same primary business information. Previously, if the source and the target constituents each had a relationship with the same organization and the relationships had the "This is the primary business" checkbox marked, the constituent merge task could be slow or could time out. | 512772 | All assemblies |
90659 | 21 |
| Previously, in an Enhanced Revenue Batch, when a pledge record with installments was imported and committed without opening and validating the batch, the pledge record was created without installments. With this fix, the pledge record is created correctly with the associated installments. | 512694 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
89644 | 19 |
| This fix addresses a performance issue loading uncommitted batches. We have improved performance so that uncommitted batches load faster when you access them. | 512659 | Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Security.Catalog.dll |
66612 | 19 |
| This fix eliminates an issue with decimal amounts for international customers who use the Event Registration Form part for Blackbaud Internet Solutions and the Event Registration Form (Classic) part for Blackbaud NetCommunity. When a website user progresses through the event steps for the part on a web page, amounts that include a decimal are no longer multiplied by 100. With this fix, amounts accurately reflect the exact amount the user entered and also process correctly to Blackbaud CRM and The Raiser's Edge. | 512455 | Blackbaud.AppFx.BBNCSvc.dll Blackbaud.Web.Content.Portal.dll |
12 | |
| Previously, when accessing the Employee Information report on the Corporate Information page for a constituent, the report loaded slowly. This fix improves the performance and response time of the report. | 512428 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
89340 | 19 |
| This fix addresses an issue where incorrect values were being returned for consecutive years a constituent was a member of a recognition program. This issue occurred for constituents who were awarded multiple recognition levels in the same year, and then continued their membership in the following year at one of those levels. With this fix, the correct values are now returned. | 512379 | All assemblies |
89333 | 21 |
| This change applies to a payment with overwritten business units in a Revenue Update Batch. Previously, when a payment's amount was updated to zero, the following validation error displayed: Business unit's amount cannot exceed its application applied amount. With this fix, the error no longer displays and the batch can commit. | 512349 | All assemblies |
89318 | 21 |
| This fix addresses two Marketing and Communications-related issues which could occur when importing direct marketing efforts into a Direct Marketing Effort Batch. The first issue dealt with "Test segment codes." Previously the combination of the "Test segment name" and the "Test segment code" had to be unique. The same "Test segment code" could not be used for more than one test segment. Now, only the "Test segment name" must be unique and the same code can be used on multiple test segments. The second issue dealt with direct marketing packages. Previously, if a package was associated with a direct marketing effort segment, you could not update the marketing effort segment with a different package during import. This fix addressed two work items: 512314 and 572140. | 512314 | All assemblies |
89308 | 27 |
| Technical Change: This fix resolves an issue with a recurring gift that does not start payments 'today' on the Advanced Donation Form part on a Blackbaud Internet Solutions web page. When a website user establishes a future date for a recurring gift payment, the program now navigates the user to the BBSP Store Card page for the user to enter credit card information. The page only stores the data for a future charge. Previously, the program navigated users to the BBSP Credit Card Payment page that always makes a payment 'today.' | 512289 | Blackbaud.Web.Content.Core.dll |
19 | |
| Previously, the immediate origin and destination numbers on bank accounts were limited to 9 characters. With this fix, we expanded the immediate origin and destination numbers on bank accounts to accommodate 10 characters. | 512286 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Treasury.Catalog.dll Blackbaud.AppFx.Treasury.UIModel.dll |
89294 | 19 |
| This fix resolves an issue that prevented membership and donation form users from entering more than eight characters in the "Account Number" field for direct debit payments. The issue occurred after websites with United Kingdom version of The Raiser's Edge were upgraded to the 6.64 version of Blackbaud NetCommunity. | 512049 | Blackbaud.Web.Content.Common.dll Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
14 | |
| This fix addresses an issue that sometimes happened when you tried to load certain specifications through Catalog Browser. Previously, you received an error when you used the AlterExistingPages function to add a detail view form to a data list. You only received this error when you were adding a detail view form to a data list that previously did not have a detail view form. | 511936 | Blackbaud.AppFx.Platform.SqlClr.dll Blackbaud.AppFx.XmlTypes.dll |
88996 | 19 |
| Previously, a funding request could not be removed even after all posted grant awards associated with the request were removed. With this fix, funding requests can be removed successfully without error. | 511871 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Fundraising.UIModel.dll |
19 | |
| This fix addresses an issue which occurred when importing into a Constituent Update Batch with specific constituent update options set on the "Configure options" tab of the batch template. Address, phone numbers, and email addresses were added as primary contact information even when the settings on the "Constituent updates" tab of the "Configure options" tab of the batch template were set to "Add as new" and "Make new address/phone/email address primary" was set to "Only if the current primary address/phone/email address has the same type" or "Never." If the new contact information didn't have the same type as the existing primary contact information, the new contact information was still being imported and marked as primary. Now, importing into a Constituent Update Batch will respect the rules set up on the batch template when the "Use batch template settings" is marked on the "Constituent updates" tab on the "Set options" tab of the import process. | 511714 | All assemblies |
88992 | 27 |
| This fix addresses issues with the Batch Entry page that could cause errors in security handling. In some cases, this prevented some users from seeing batches that they had security rights to see. | 511362 | Blackbaud.AppFx.Platform.Catalog.dll Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Security.Catalog.dll |
88948 | 19 |
| With this fix, we improved performance when running an incremental refresh for the following smart field types: Constituent revenue application, Constituent recognition credit amounts, Constituent recognition credit dates, Constituent revenue application amounts, Constituent revenue application annual renewer, Constituent revenue application counts, and Constituent revenue application dates. | 511205 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.Web.Content.Core.dll |
88443 | 13 |
| This fix improves the performance of the Export Definitions page. Previously, the list on this page could take a long time to load. With this fix, load time has been improved. | 510508 | Blackbaud.AppFx.Platform.Catalog.dll Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.ServiceRevisions.Specs1490.dll |
88826 | 19 |
| This fix addresses an issue which occurred when refreshing direct marketing efforts. Previously, if the marketing effort contained only acquisition lists as segments, refreshing the direct marketing effort could take a long time to process. With this fix, we have optimized the refresh process. | 509821 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Marketing.Catalog.dll |
86310 | 19 |
| When a Blackbaud Internet Solutions donation web page uses German or Italian and the currency separator uses a comma, the donation amount is no longer incorrect. This fix corrects the actual donation amount and format on the web page. The amounts are also now correct for acknowledgements and receipt emails. However, they display using the United States currency format (addressed in 509641). If you have a customization for currency values with periods, please be aware there may be an impact to the web page when you view it in a different language. | 509643 | Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
88518 | 12 |
| When a Blackbaud Internet Solutions donation web page uses German or Italian and the currency separator uses a comma, the amount format is now correct for acknowledgements and receipt emails. Previously, these amounts displayed using the United States currency format. | 509641 | Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
88516 | 12 |
| This fix addresses a performance issue with certain ad-hoc queries. Previously, ad-hoc queries that used an attribute category as a criteria could have performance issues when the attribute category was set up with a data type of code table. With this fix, we have optimized performance so these queries run more efficiently. | 509443 | Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.SqlClr.dll |
88519 | 19 |
| This fix addresses a performance issue with certain ad-hoc queries. Previously, ad-hoc queries that used an attribute category as a criteria could have performance issues when the attribute category was set up with a data type of code table. With this fix, we have optimized performance so these queries run more efficiently. | 509422 | Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.SqlClr.dll |
88519 | 19 |
| Previously, push date functionality did not allow for more than one row in the Expiration dates grid. With this fix, the grid now allows for multiple rows. This fix addresses issues reported in 497343, 507829 and 508294. | 508294 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Membership.Catalog.dll Blackbaud.AppFx.Membership.UIModel.dll |
88336 | 19 |
| This fix addresses an issue that could sometimes occur when opening batches or data forms. Previously, if your timeout settings were set to a value larger than 180 seconds, you could receive an error when you tried to open batches or data forms. Timeout options for the WebShell.DefaultClientAppInfoTimeoutSeconds web.config setting used to be limited to 180 seconds. With this fix, this restriction has been removed. | 507917 | Blackbaud.AppFx.Server.dll |
87219 | 19 |
| Previously, push date functionality did not work correctly when using membership terms longer than a year. With this fix, this functionality now pushes membership expiration dates properly. This fix addresses issues reported in 497343, 507829 and 508294. | 507829 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Membership.Catalog.dll Blackbaud.AppFx.Membership.UIModel.dll |
88289 | 19 |
| This fix resolves an issue that caused an error to appear when you attempted to send emails to large recipient lists. This issue occurred after you upgraded to the 6.64 version of the product. | 507641 | Blackbaud.AppFx.ContentManagement.Platform.Email.Catalog.dll |
12 | |
| In Blackbaud CRM 2.91 and subsequent versions, we made enhancements to several of the main functional areas, including Events, Prospects, and Memberships. These functional areas were converted to actual pages to improve functional flexibility and overall usability. While you cannot assign tasks to pages, pages can have actions. To add actions to these pages, you edit the page properties while in design mode. You can create custom action groups, similar to custom task groups; however, before this fix, you could not control the placement of these groups on the page. Previously, custom action groups appeared only on the left side of the screen above the Shortcuts, Recent searches, and Recently accessed lists. With this fix, you can change the placement of these groups on the page. You can leave the custom action groups on the left side of the screen. However, you can now also add these directly to the page. To change the placement of the action groups, click "Edit action groups" in design mode. Select the action group you want to edit and use the RenderLocation field on the Action group screen to change the location. Placement for the action group defaults to "ExplorerBar," which places the action group on the left side of the screen where the group was located before. You can now also select "Tab" if you want the action group to appear on the page instead. | 507521 | All assemblies |
88256 | 21 |
| This fix addresses an issue when adding a plan participant to a major giving plan for a prospect. This issue was introduced in Service Pack 2 for Blackbaud CRM 4.0. When you added a major giving plan for a prospect from the prospect's record, your participant appeared on the screen with the record ID for the person rather than the participant's name. This happened if you selected the participant from the drop-down menu. If you searched for a participant instead, you did not encounter this issue. With this fix, the name displays correctly. | 507460 | Blackbaud.AppFx.Server.dll Blackbaud.AppFx.UIModeling.RestServices.dll Blackbaud.AppFx.WebShell.WebUI.dll |
88254 | 12 |
| This fix addresses an issue with duplicate constituent matching in Constituent Batch. Previously, Constituent Batch did not use the "In batch" match settings as configured in "Global data entry settings" in Administration. In addition, the duplicate constituent matching in Constituent Batch now more closely resembles the behavior found in other batch types, such as Constituent Update Batch and Enhanced Revenue Batch. Before this fix, Constituent Batch considered only the first and last name fields, in addition to the address fields. Now, Constituent Batch also considers matches in the following additional fields: middle name, title, suffix, lookup ID, alternate lookup ID, phone number, and email address. For information about duplicate matching, see the "Duplicate Constituents and Merge Tasks Guide." This fix addresses issues reported in 481470 and 507278. | 507278 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Constituent.UIModel.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
86662 | 19 |
| We have optimized the performance of the FACT_INTERACTION ETL package in the Blackbaud Data Warehouse. Because this package processes more data in version 4.0 of Blackbaud CRM than it did in previous versions, the performance enhancements may not be noticeable compared to versions prior to 4.0. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 507250 | BBDW.ServiceRevisions.dll BBDWETL - SSIS Reporting Package |
87211 | 19 |
| This fix improves a performance issue when calculating the "Constituent revenue application amount" smart field when revenue recognition is selected on the Parameters tab. | 506715 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
69349 | 12 |
| This fix addresses an issue that could sometimes occur with the Database Growth Analysis Process. Previously, this process would fail if you had made a copy of a business process output table on a schema other than the dbo schema. | 506535 | Blackbaud.AppFx.DbMaintenance.Catalog.dll |
19 | |
| When you select Support Community from the Help menu, you are now directed to the new Blackbaud CRM and Blackbaud Internet Solutions Community at https://community.blackbaud.com/products/blackbaudcrm. | 506490 | Blackbaud.AppFx.ContentManagement.Platform.Core.dll Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
19 | |
| Previously, in an Enhanced Revenue Batch, when an event registration commitment was created and added to a batch row, an error displayed in the following scenario: If, prior to saving the batch row, another row in the same batch was deleted or any other Enhanced Revenue Batch was deleted, the event registration commitment was deleted and an error message displayed upon save. With this fix, the batch saves correctly. | 506307 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
86293 | 12 |
| Previously, in an Enhanced Revenue Batch, donors did not receive recognition credits for matching gift claim payments. This occurred when the donor on the matching gift claim was not the same constituent as the donor on the matching gift payment. With this fix, the donor accurately receives recognition credits for the payment. | 506297 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
86294 | 19 |
| This fix addresses an issue with the "Given anonymously" field in Enhanced Revenue and Revenue Update Batch. Previously, if you entered a transaction, marked the "Given anonymously" field, and then opened the "Apply to commitments" screen, the "Given anonymously" field was cleared after you clicked OK on the "Apply to commitments" screen. Now, when you mark "Given anonymously," the field remains marked after you close the "Apply to commitments" screen. | 505963 | All assemblies |
84470 | 30 |
| With this fix, we improved the performance of queries, such as Revenue application, that use the Designation name field. For custom SQL code that references UFN_DESIGNATION_BUILDNAME or UFN_DESIGNATION_BUILDNAME_BULK to retrieve Designation name, we suggest you rewrite the code to reference DESIGNATION.NAME directly. In addition, the NAME column in the DESIGNATION table was previously a SQL-calculated field. With this fix, it is now a text field populated by database triggers on the DESIGNATION and DESIGNATIONLEVEL tables. Note that SQL queries should never insert or update the NAME column directly; however, "select" operations from this column now perform better in many instances. | 505735 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| This fix addresses a performance issue that some users could experience when viewing the Export Definitions page. Previously, when users who did not have administrative rights tried to view the page, the page could sometimes time out and the users were not able to see the contents of the page. This was not an issue for administrative users. With this fix, we have improved the performance of this page to prevent timeouts for all users. In addition, the Export Definitions page now respects the "Allow access to all query views" system privilege. | 505685 | Blackbaud.AppFx.Platform.Catalog.dll Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.ServiceRevisions.Specs1490.dll |
80415 | 19 |
| This fix addresses an issue that sometimes happened when creating forms using the SDK. Previously, when you created a form that included a collection field and set the EnablePaging property of the field to "true," the collection included a "Refresh" button in the final rendering of the form. This button was unnecessary and could cause problems with the form if a user clicked it. To prevent this issue, we have removed the "Refresh" button so that it no longer appears in these forms. | 505584 | All assemblies |
21 | |
| This fix addresses an error that could occur when you saved queries without a static selection. If you had the Blackbaud Data Warehouse deployed and you selected the option to copy static selections, saving a query without a static selection resulted in an error in your event log for the web server. In addition, if your web server were running .Net version 4, your web server could crash as a result of this error. With this fix, saving a query without a static selection no longer results in an error in your event log. In the event of a legitimate error, we have also updated the background task on the event log to prevent issues with .Net version 4. | 505457 | Blackbaud.AppFx.Server.dll |
19 | |
| New Feature: The constituent record now includes the Prospect Tile, which summarizes information for major giving prospects. You can view and edit a constituent's prospect information from the tile, including the prospect status and the prospect manager. From the Prospect Tile, you can also flag the prospect for tracking purposes. | 505111 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Constituent.UIModel.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.MajorGiving.Catalog.dll |
12 | |
| This fix addresses an issue that sometimes occurred with query folders in the Information Library. Previously, when you switched between query folders, some folders could incorrectly appear empty. This could happen when you paged through the queries in one folder and then switched to another folder that did not have as many pages of queries as the previous one. With this fix, folders display their content correctly when you switch between them. | 504822 | All assemblies |
82252 | 21 |
| New Feature: Your System Administrator can now use the settings BlockAllEmails and BlockScheduledEmails in both web.config files for Blackbaud Internet Solutions and Blackbaud CRM to block sending email messages and scheduled email. Use these settings to prevent email from inadvertently sending from a test environment. By default, these settings are <add key="BlockAllEmails" value="False" /> and <add key="BlockScheduledEmails" value="False" />. To prevent sending messages or scheduled email, enter True in each web.config file for both programs. To implement this setting, the ProcessCMSEmail.BusinessProcess.vb file has been updated for the Process CMS Email Business Process in Blackbaud CRM. | 504521 | Blackbaud.AppFx.BBNCSvc.dll Blackbaud.AppFx.ContentManagement.Platform.Email.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll |
12 | |
| This fix addresses an issue when editing posted payments with adjustments linked to deposits. Previously, when editing a posted payment, the following error displayed: "Data could not be saved. Payments cannot be added to locked deposits". With this fix, this error no longer displays and the form saves correctly. | 504507 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
80370 | 12 |
| Previously, when a recognition filter was applied for a constituent, the Recognition History and Recognition Summary tabs displayed incorrect records for transactions and payments. With this fix, records now display correctly. Note that this fix addresses issues reported in 499701, 501624, and 504122. | 504122 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
80917 | 19 |
| When a Blackbaud Internet Solutions or Blackbaud NetCommunity donation web page uses culture settings set to display date formats as dd/mm/yyyy, this fix eliminates the message 'String was not recognized as a valid DateTime' that potentially occurred when the page included a date attribute field. | 504066 | Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
12 | |
| This fix addresses a performance issue with the Constituent Recognition Revenue data list. Previously, users encountered an error when viewing information on the Recognition Credit History tab on the constituent recognition record. | 504056 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Membership.Catalog.dll |
80664 | 19 |
| This fix addresses an issue where users without security permissions to forms related to recurring gifts received an error when navigating through rows in an Enhanced Revenue Batch. | 504032 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
80409 | 19 |
| This fix addresses an issue with user-defined smart queries. When you create user-defined smart queries, you can specify output fields to use as filters on the "Set save options" tab of the query. These filters are used on the Parameters tab of smart queries you create from this user-defined smart query definition. You can use one or more output fields of the same record type (such as GUID fields) and select one or more as filters on the "Set save options" tab of the user-defined smart query definition. Previously, you could have two or more output fields of the same record type and the same name on the "Set save options" tab (such as "Constituents\Name" and "Constituents\Spouse\Name") and select only one to be used as a filter. When you re-opened the query, both fields were selected as filters on the "Set save options" tab. If you did not re-save the query, the original single filter option remained unchanged. However, if you re-opened and re-saved the query, both fields were saved as filters and both filters appeared on the Parameters tab of smart queries you created from this user-defined smart query definition. With this fix, the filters you select on the "Set save options" tab of the user-defined smart query definition are saved correctly. When you re-open the query, the original single filter you selected remains unchanged. Even if you re-save the query, only the output fields you selected as filters on the "Set save options" tab are saved to appear on the Parameters tab of smart queries you create from this user-defined smart query definition. | 503578 | Blackbaud.AppFx.Platform.UIModel.dll Blackbaud.AppFx.WebShell.WebUI.dll |
19 | |
| Technical Change: This fix addresses an issue with the names of AddressFinder processes and AddressFinder Submit processes. Previously, when you attempted to add an AddressFinder Submit process to a queue, all of the AddressFinder Submit processes had the same generic "AddressFinder Submit Process" name. If you had more than one, you could not differentiate them to tell which one you wanted to select. Now, new AddressFinder Submit processes are named whatever the process is named on the "Add (or Edit) AddressFinder process" screen; however, the Submit process names must be unique and will be truncated at a maximum of 100 characters. After you upgrade, the names of any existing AddressFinder processes will remain the same on the "Add (or Edit) AddressFinder process" screen for each process. The names of the AddressFinder Submit processes will be updated in existing queues to be the name of the AddressFinder process, but will be unique and truncated at a maximum of 100 characters. Any new queues you create after the upgrade will display the new unique AddressFinder Submit process names. | 503572 | Blackbaud.AppFx.AddressManagement.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
79873 | 19 |
| Previously, the Link Tank window on the Wealth and Ratings screen was not populating links to online data resources correctly. With this fix, these resources now appear in the window. | 503556 | Blackbaud.AppFx.Server.dll Blackbaud.AppFx.WebShell.WebUI.dll |
19 | |
| Previously, in an Enhanced Revenue Batch where the default application was set, the Apply to commitments screen displayed even when no commitments existed for a constituent. With this fix, the screen no longer displays unnecessarily. | 503359 | Blackbaud.AppFx.Fundraising.UIModel.dll |
83019 | 12 |
| Resolve an issue when attempting to authenticate to the Designer Toolbox web service. | 503239 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1480.dll Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
10 | |
| Technical Change: This fix addresses an issue which occurred when creating a test marketing effort for a direct marketing effort. The issue occurred only if the direct marketing effort was created with a communication template that had one or more required solicit code exclusions. Previously, when you set up a test marketing effort, required solicit code exclusions were copied to the new test effort as a both default solicit code exclusions and as required solicit code exclusions. Now, the required solicit code exclusions are no longer copied to the new test marketing effort; instead, they are added automatically to all direct marketing efforts and test efforts as required exclusions whenever the solicit code is marked required. To address this issue, we made a change to USP_MKTCOMMUNICATIONTEMPLATE_COPY so that it now removes any required solicit code exclusions from the copied exclusions before the new template is created. Solicit codes that are set as required appear automatically on every communication template and on every marketing effort. You can make solicit codes required from the "Solicit codes" task under Configuration on the Marketing and Communications page. On the "Select features and defaults" tab on the communication template, you can click "Exclusions" to view required solicit codes. You can also click on the Exclusions tab of the marketing effort to view required solicit code exclusions. You can create a test marketing effort from a marketing effort that has not yet been activated by clicking "Test efforts" under Testing. | 503012 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Marketing.Communications.Catalog.dll |
79823 | 19 |
| This fix improves the performance of the Recognition Credits report. | 502771 | All assemblies |
79797 | 27 |
| Technical Change: This fix addresses an issue direct marketing efforts with source codes that contain a user-defined source code part in "Marketing and Communications." Previously, if the user-defined source code part was assigned as a default on a communication template, you could receive errors when adding segments to direct marketing efforts. We updated USP_DATAFORMTEMPLATE_ADD_MKTCOMMUNICATIONEFFORT to properly handle this situation. When you upgrade, existing marketing efforts that have already been created with a default user-defined source code part will need to be recreated. | 502697 | All assemblies |
79794 | 27 |
| Technical Change: This fix addresses a site security issue which occurred when importing updated constituent information using Constituent Update Batch. Previously, if a constituent in CRM was associated with site A and you updated that constituent through an import, but the import file had the constituent in site B, after the import the constituent in CRM would be associated with site B only. The import process removed site A since that wasn't in the import file. Additionally, if the import file had no site information for the constituent, after the import the constituent in CRM would have no site. Now, the import process using Constituent Update Batch simply adds any site information for the constituent to the constituent in CRM. If a constituent in CRM has site A and the import file has site B for the constituent, after the import the constituent in CRM will have sites A and B. If the import file had no site information for the constituent, after the import the constituent in CRM would still have site A. With manual data entry in Constituent Update Batch, as opposed to import, if you remove a site from a constituent in a batch row, the site will still be removed from the constituent record in CRM. The BATCHCONSTITUENTUPDATE table (ConstituentUpdateBatch.Table.xml spec) now has a new column "ROWFROMBATCHUI" that indicates whether the data in the row was populated through manual data entry or through import. Four other specs changed to accommodate the "ROWFROMBATCHUI." USP_ADD_BATCHCONSTITUENTUPDATEBATCHROW.xml, which adds a row to the batch, now saves the "ROWFROMBATCHUI" value to the new table column. USP_EDITLOAD_BATCHCONSTITUENTUPDATEBATCHROW.xml, which loads the batch row for editing, now reads the "ROWFROMBATCHUI" value from the table column. USP_EDITLOAD_BATCHCONSTITUENTUPDATEBATCHROW_1.xml, which saves edits made to the batch row, now saves the "ROWFROMBATCHUI" value from the table column. When you save and commit the batch, the "ROWFROMBATCHUI" value is used to remove sites that are not in the batch from constituents in CRM if the information was added through manual data entry. | 502525 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| Previously, in an Enhanced Revenue Batch, an error displayed when installments were edited and the batch template included a default revenue type of pledge. With this fix, the error no longer displays. | 502465 | Blackbaud.AppFx.Fundraising.UIModel.dll |
83021 | 12 |
| When you use Blackbaud Internet Solutions or Blackbaud NetCommunity, this fix resolves an issue that prevented the Volunteer Opportunity part from processing volunteer transactions to batch in Blackbaud CRM or The Raiser's Edge. | 502435 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| Previously, when a constituent had both an active membership and a cancelled membership, and their membership was renewed through the BBIS membership part, the part would attempt to rejoin the cancelled membership and result in a download error in Membership Dues Batch. Now, the part will choose to renew the active membership. | 501924 | Blackbaud.Web.Content.Portal.dll |
73499 | 19 |
| This fix addresses an issue importing fixed-width files that was introduced in Service Pack 2. Item 447418 in Service Pack 2 addressed a problem with import exception files not properly handling fields with commas or quotation marks. That fix inadvertently caused fixed-width import files to fail. Now, fixed-width files import and process correctly, as they did before Service Pack 2. | 501673 | Blackbaud.AppFx.TextFileParser.dll |
19 | |
| Previously, when a recognition filter was applied for a constituent, the Recognition History and Recognition Summary tabs displayed incorrect records for transactions and payments. With this fix, records now display correctly. Note that this fix addresses issues reported in 499701, 501624, and 504122. | 501624 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| This fix addresses an issue with "Sponsorship effort templates" found in Marketing and Communication and in Sponsorships. Previously, if you added a sponsorship effort template and added a rule from the Sponsorship Rules tab of the effort template, you could mark the "Exclude from effort but show counts" checkbox. However, after you marked the checkbox, the Sponsorship Rules tab on the effort template would not load and you would receive the error: "The section could not be loaded. Input string was not in a correct format." Now the error no longer appears and the Sponsorship Rules tab is displayed correctly. | 501460 | All assemblies |
BB751947 | 27 |
| This fix addresses an issue with performance of ETL packages in the Blackbaud Data Warehouse. Previously, the BBDW_FACT_FINANCIALTRANSACTIONLINEITEMSITE ETL package could take a long time to complete. This happened if you had a large number of records in your SITE table. With this fix, the package runs more efficiently. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 501214 | BBDW.ReportDB.Catalog.dll BBDW.ServiceRevisions.dll BBDWETL - SSIS Reporting Package Blackbaud.Web.Content.Core.dll |
74394 | 9 |
| This fix improves a performance issue with the Fundraising Purpose Types data list. Previously, a timeout message sometimes appeared before the data was available. | 501105 | All assemblies |
27 | |
| Technical Change: This fix improves a performance issue with the generation of query views when querying on constituents in a recognition program assigned to large amounts of constituents. This fix only applies to newly generated recognition program query views. Existing query views will need to be regenerated on demand via a script. | 500968 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Membership.Catalog.dll |
74016 | 19 |
| Previously, the status of a membership card was set to "Canceled" after adding a payment to an installment plan. With this fix, the status remains unchanged when adding the payment. | 500964 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Membership.Catalog.dll |
74440 | 19 |
| This issue addresses an issue when trying to add Show Report actions in WebUI. Previously, when you tried to add a Show Report action using Page Designer in WebUI, you were unable to fill out the required report parameter "ID" field because the drop-down menu was empty. With this fix, you are able to add these types of actions normally. | 500875 | Blackbaud.AppFx.Platform.UIModel.dll |
9 | |
| Previously, when attempting to delete a posted matching gift claim and its associated payment, the following error displayed: "There are matching gift claims against this payment. Delete those matching gift claims before deleting this payment." With this fix, we changed the stored procedure to delete all related records, and the error no longer displays. | 500193 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This fix addresses an issue where users were unable to delete memberships after the associated payment was deleted if the payment was posted. | 499962 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Membership.Catalog.dll |
83346 | 19 |
| Previously, when a recognition filter was applied for a constituent, the Recognition History and Recognition Summary tabs displayed incorrect records for transactions and payments. With this fix, records now display correctly. Note that this fix addresses issues reported in 499701, 501624, and 504122. | 499701 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
83342 | 19 |
| This fix addresses an issue which occurred when importing new constituents into a Constituent Update Batch. Previously, when a constituent's gender was blank in the import file, the import process into the batch did not include the logic to map the gender of the constituent based on the constituent's title or first name, as determined by the "Title code defaults" and "First name" configuration tasks in Constituents. The gender for the new constituent was set to "Unknown" instead. Now when you import new constituents and the gender is blank, the gender for the constituents is set based on the settings of the "Title code defaults" and "First name" configuration tasks. If the gender cannot be determined based on the configuration settings, the constituent's gender is set to "Unknown" when imported into the batch. | 499466 | All assemblies |
86599 | 21 |
| This fix addresses an issue that sometimes happened when you tried to load a custom QueryViewSpec using the Blackbaud SDK. Previously, you could sometimes get an error when importing a selection of a particular record type. This happened when the BBAppFxServiceRole did not have Select permissions for that record type's base table. | 499370 | All assemblies |
73273 | 21 |
| This fix addresses an issue that could occur when you edited a scheduled business process. Previously, when you edited a scheduled business process with a schedule type of "One time," the time reverted to 12:00am when you saved the schedule, regardless of the time you entered before saving it. | 499090 | Blackbaud.AppFx.Platform.Catalog.dll Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Platform.UIModel.dll Blackbaud.AppFx.SpWrap.dll Blackbaud.AppFx.UnitTesting.dll |
19 | |
| This fix addresses an issue with BBIS forms with multiple pages. Previously, when you had multiple pages in a workflow and there was an unformatted text part in the header or footer, the content in the header or footer was carried over to the subsequent pages in the workflow. | 498861 | Blackbaud.Web.Content.Portal.dll |
12 | |
| This fix addresses a formatting issue with export files that include year fields. Previously, when you generated an export file in .xlsx format that included a year field such as "Class of," the formatting for the year could be incorrect because the export handled it as a number instead of a year. Depending on your locale settings, years could appear in your export output with additional characters such as thousand separators. | 498852 | Blackbaud.AppFx.Platform.Export.dll |
83020 | 19 |
| Technical Change: This fix addresses an issue that occurred when you ran the database integrity utility after upgrading to Blackbaud CRM version 4.0. Previously, when you ran the utility after the upgrade you could notice that constraints in the DATAFORMFIELDCHARACTERISTIC table were not respected. To avoid this problem, we have removed the constraints from the table. The constraints are now enforced by the Data Form Field Characteristic Edit data form. | 498833 | Blackbaud.AppFx.Platform.DataForm.Catalog.dll Blackbaud.AppFx.Platform.ServiceRevisions.Specs1490.dll |
87217 | 19 |
| This fix addresses an issue that prevented users from searching for revenue that was not associated with an opportunity when the designations on the opportunity matched designations on the revenue. | 498616 | Blackbaud.AppFx.MajorGiving.Catalog.dll |
83602 | 19 |
| Previously, an error occurred when trying to complete a sponsorship where a constituent was sponsoring an opportunity via BBIS and the constituent was not created properly. Now, a record operation called "Retrieve constituent" appears in the Sponsorship Purchases data list for rows that are missing constituents. Running this record operation will retrieve the constituent information. You can then either complete or delete the BBIS sponsorship. However, records in the data list that are missing constituent information prior to this fix will retrieve the constituent information from BBPS, so the constituent will not be matched and the full name of the constituent will be created in the Last name field in the constituent table. To fix this issue, you can separate out the constituent name after retrieving the constituent. | 498569 | Blackbaud.AppFx.ContentManagement.Catalog.dll Blackbaud.AppFx.ContentManagement.Parts.ShoppingCart.UI.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Programming.Catalog.dll Blackbaud.AppFx.Programming.SPWrapProgramming.dll Blackbaud.AppFx.Sponsorship.Catalog.dll Blackbaud.Web.Content.Core.dll |
12 | |
| This fix changes the requirements for addresses located in Hong Kong. With this fix, Hong Kong addresses no longer require a post code and province in order to be saved. | 498477 | Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
12 | |
| This fix addresses an issue where target dates were not being calculated correctly when adding steps from a template on the Add Stewardship Plan form. | 498458 | Blackbaud.AppFx.Stewardship.UIModel.dll |
12 | |
| Previously, an error occurred when adding a new sponsorship from the constituent record using a credit card as the payment method. With this fix, the sponsorship is now added successfully. | 497481 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Sponsorship.Catalog.dll |
90753 | 19 |
| Previously, push date functionality did not push membership expiration dates into the next year correctly if the push date was after the expiration date. With this fix, this functionality now pushes membership expiration dates properly. This fix addresses issues reported in 497343, 507829 and 508294. | 497343 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Membership.Catalog.dll Blackbaud.AppFx.Membership.UIModel.dll |
74357 | 19 |
| When your Blackbaud Internet Solutions Donation Form is configured for pledges only, the part no longer displays a configuration error on your donation web page. This fix removes the error so the pledge only form displays successfully on your website. | 497216 | Blackbaud.Web.Content.Portal.dll |
74371 | 12 |
| Previously, in a Revenue Update Batch, when editing installment designation amounts on specific posted pledges, an error displayed. With this fix, the error no longer displays. | 497025 | Blackbaud.AppFx.Fundraising.UIModel.dll |
74387 | 12 |
| This fix addresses an issue when you tried to edit a special link in the Blackbaud Direct Marketing email editor. Previously, once you inserted a special link, you were not able to edit it. If you wanted to make changes to an existing link, you had to delete it and re-insert it. With this fix, you are now able to edit special links. | 496933 | Blackbaud.AppFx.Communications.UIModel.dll |
74236 | 19 |
| This fix addresses an issue with performance of ETL packages in the Blackbaud Data Warehouse. Previously, the BBDW_FACT_FINANCIALTRANSACTIONLINEITEMSITE ETL package could take a long time to complete. This happened if you had a large number of records in your SITE table. With this fix, the package runs more efficiently. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 496712 | BBDW.ReportDB.Catalog.dll BBDW.ServiceRevisions.dll BBDWETL - SSIS Reporting Package |
74394 | 12 |
| This fix addresses an error that could occur when you were running a business process. Previously, while a business process was running, you could sometimes receive an error indicating that the business process was already running. This message was redundant and did not actually represent an error in the process. With this fix, you no longer receive this unnecessary error message and you receive a standard notification when the process is complete. | 496700 | Blackbaud.AppFx.Server.dll Blackbaud.AppFx.UIModeling.RestClient.dll Blackbaud.AppFx.UIModeling.RestServices.dll Blackbaud.AppFx.WebShell.WebUI.dll |
74388 | 19 |
| This fix addresses an issue that prevented some users from the same site to see uncommitted batches owned by other users on the site. Previously, a user who did not have administrative rights had to be both the batch owner and have access to the site for the batch template in order to see an uncommitted batch. This was an unintended limitation. With this fix, users can still see uncommitted batches if they own the batch, but now they can also see them if they have access to the site for the batch template, even they do not own the batch. | 496577 | Blackbaud.AppFx.Platform.Catalog.dll Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.ServiceRevisions.Specs1490.dll |
74398 | 12 |
| This fix addresses an issue when you used the "Contacting Support" link from the legacy help in Blackbaud CRM. Previously, when you tried using that link, you sometimes received an error. The link has been updated so that it now works consistently. | 496527 | Blackbaud.AppFx.Server.dll Blackbaud.AppFx.WebShell.WebUI.dll |
73585 | 12 |
| To improve usability of global changes in Administration, we have converted the Global Changes page to a list builder list. List builder lists include functionality that makes it easier to navigate items on the list. For example, on list builder lists you are able to sort and filter by column, select and rearrange columns, search the list, and navigate directly to any page on the list. | 496510 | All assemblies |
74412 | 21 |
| When you use Blackbaud Internet Solutions or Blackbaud NetCommunity to send email, this fix resolves the broken tracker image at the end of the email. This image is used to send received and opened information to Blackbaud. To resolve this issue, the EmailJob.vb file has been updated. | 496125 | All assemblies |
74442 | 21 |
| Technical Change: Previously, on the Prospect Team tab, the edit and delete options for primary manager, secondary manager, and secondary solicitor were disabled. Now, the edit and delete options are hidden for those team members. | 495949 | All assemblies |
BB752425 | 21 |
| This fix addresses an issue with constituent auto-matching based on Lookup ID and Alternate Lookup ID when importing into Constituent Update Batch. In Administration, you can click "Enable/disable matching" to then enable or disable the "Auto-match duplicates in batch" setting. On the "Set options" tab of the import process, there are two options related to matching: "Check for records that match existing constituents" and "Process automatically." If either of these options are disabled, auto-matching is not performed on the imported batch during batch validation. However, previously, the automatic matching functionality was not properly disabled during import so auto-matching was still taking place. Now when either of these settings are disabled, the automatic matching functionality is disabled completely when importing into a Constituent Update Batch. | 495831 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.Web.Content.Core.dll |
74450 | 9 |
| With this fix, users are now prevented from adding duplicate mappings when a composite segment mapping includes a large number of items. | 495503 | Blackbaud.AppFx.Accounting.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| This fix improves committal performance when using a Revenue ID in Import and Enhanced Revenue Batches. | 494621 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
74128 | 19 |
| Technical Change: This fix addresses an issue which occurred when viewing constituent groups; the information about the group members on the Summary tab of the constituent group record would not load. This issue occurred because we allowed you to add the same constituent more than one time to the same group in some places. We have added a trigger "TR_GROUPMEMBER_DUPLICATEGROUPMEMBER" on the GROUPMEMBER table to prevent duplicate members. | 494546 | All assemblies |
BB727712 | 21 |
| Technical Change: This fix addresses an issue which occurred when viewing constituent groups; the information about the group members on the Summary tab of the constituent group record would not load. This issue occurred because we allowed you to add the same constituent more than one time to the same group in some places. We have added a trigger "TR_GROUPMEMBER_DUPLICATEGROUPMEMBER" on the GROUPMEMBER table to prevent duplicate members. We have also modified the "Group Add" functions for Auction Item Batches, Sponsorship Batches, and Enhanced Revenue Batches to prevent duplicates. | 494545 | Blackbaud.AppFx.Auction.Catalog.dll Blackbaud.AppFx.ConstituentGroups.Catalog.dll Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Sponsorship.Catalog.dll |
12 | |
| This fix addresses an issue when adding a task in Shell Design with an action type of "BrowseQueryResults." This problem occurred when you selected a query type of "SmartQueryInstance." Previously, when you attempted to search for the smart query instance, the Ad-hoc Query Search screen appeared so you were not able to select a smart query. Now, the Smart Query Search screen appears instead. | 493859 | Blackbaud.AppFx.Platform.UIModel.dll |
73282 | 19 |
| In a Constituent Update Batch, if there were multiple members of a household and there were conflicts with any of the phone numbers, such as with which number should be marked primary, the program created an exception batch and included an unfriendly error message. Now a more helpful error explaining the conflict is displayed. | 493700 | All assemblies |
27 | |
| This fix addresses an issue that sometimes happened when saving user-defined smart queries. Previously, if you made changes to the output fields on a user-defined smart query and then tried to save it without first viewing the "Set save options" tab, you were not able to save the query. With this fix, saving works correctly, even if you do not first access the "Set save options" tab. | 493563 | All assemblies |
21 | |
| New Feature/Technical Change: This fix addresses an issue with how multiple household members were included in the same general correspondence process in Marketing and Communications. Previously, the way this was handled was different than how multiple household members were included in direct marketing efforts even though users expected general correspondence to work the same way. Now, when you add or edit a correspondence process, when multiple members of a household are included in the mailing, you can click Edit in the "Output format" field and mark a new "Mail to primary household member when available" checkbox on the "Processing options" screen. Previously, before we added this option, the correspondence output for the household would use the name of the household record in the Addressee and Salutation fields, with addressee information for one of the household members for the Contact Addressee field. Now, when the new checkbox is marked, the Addressee and Salutation fields will contain the information for the primary member of the household and not the information from the household itself. If the household does not have any members, the output for the household will still use just the household information. We created a new USP_DATAFORMTEMPLATE_EDIT_CORRESPONDENCEPROCESS_5 to be used in place of USP_DATAFORMTEMPLATE_EDIT_CORRESPONDENCEPROCESS_4. The old USP still exists but does not contain the new functionality. The new USP will be used automatically after you upgrade and contains the new checkbox which, by default, is not marked. In order to take advantage of the new functionality, you will need to edit existing general correspondence mailings and mark the checkbox after you upgrade. | 493402 | All assemblies |
73312 | 27 |
| This fix improves sporadic performance issues with the Appeal Performance report and the Appeal Profile report. In addition, when using the UK version of Blackbaud CRM, this fix also changes the reports to now use the Gift Aid tax claim amounts that are pre-calculated by the "Gift Aid refresh process" in Revenue. | 493358 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This change applies to an Enhanced Revenue Batch created from an import process. Previously, when importing benefits, the receipt amount did not calculate correctly on a pledge record. With this fix, the receipt amount calculates correctly. | 493293 | Blackbaud.CRM.Financial.Domain.dll |
74655 | 12 |
| The Refresh UI Model utility in Visual Studio now supports C#. When you create a UI Model with C# in the SDK, you can now use the Refresh UI Model utility to update the UI Model's partial class to reflect changes to the data form spec. Previously, the Refresh UI Model utility in Visual Studio only supported Visual Basic. You could still create a UI Model with C#, but you could not use the Refresh UI Model utility to update the UI Model's partial class. | 492190 | All assemblies |
74113 | 21 |
| This fix addresses an issue in databases with two or more data warehouses configured. Previously, when you tried to delete an attribute category in a Blackbaud CRM database that had two or more data warehouses, you received an error. This fix addresses the issue so you can now delete attribute categories without receiving the error. | 492065 | Blackbaud.AppFx.Platform.SqlClr.dll |
57926 | 12 |
| This change applies to exceptions in an Enhanced Revenue Batch. Previously, when an exception occurred, and the batch row contained multiple applications as well as multiple solicitors or recognitions (or a combination of both), empty exception batches were created. With this fix, empty exception batches are no longer created. | 491964 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This fix improves the performance of adding and updating GL accounts for systems associated with a large number of GL accounts. | 491856 | Blackbaud.AppFx.Accounting.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
72073 | 19 |
| This fix addresses an issue with the Pledge Receivables Report. Previously, when payments were applied to pledges, posted, and then removed from those pledges, the payments were incorrectly included in the Pledge Receivables Report. This caused the Payments and Balance columns to be incorrect. With this fix, adjusted payments to pledges are correctly excluded from the report. | 491661 | All assemblies |
32 | |
| Previously, when multiple solicitors and designations existed in a Revenue Update Batch, and the solicitor and designation fields were changed in a batch row, an error displayed during validation. With this fix, the batch validates without error. | 491517 | All assemblies |
74355 | 21 |
| With this fix, the Adjusted revenue report now respects site security. | 491515 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| This fix addresses an issue when attempting to import constituents into the Auction Item batch using their lookup ID. With this fix, constituents can be imported using their lookup ID without error. | 491427 | Blackbaud.AppFx.Auction.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
73761 | 12 |
| This fix addresses an issue that occurred when users registered invitees for a multi-level event configured to use a registration package. Previously, the Add a registrant form would default an incorrect event. | 491142 | All assemblies |
BB750030 | 21 |
| This fix addresses an issue with comments displaying on the Memberships page. Previously, a row containing comments always appeared for the membership, even if no comment was present. With this fix, rows only show if a comment has been provided. | 491131 | All assemblies |
73489 | 21 |
| This fix improves a performance issue that occurred when non-administrator users searched for designations. | 491115 | Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Security.Catalog.dll |
73430 | 12 |
| This fix addresses an issue which occurred when changing which email address was marked as primary for a constituent in Constituent Update Batch. Previously, when you changed which email address was marked as primary for a constituent, you sometimes received the error "Constituent can only have one primary email," even though only one email address was marked as primary. The error no longer appears when only one email address is marked as primary. | 490822 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
74181 | 19 |
| This fix addresses an issue which occurred when changing which phone number was marked as primary for a constituent in Constituent Update Batch. Previously, when you changed which number was marked as primary for a constituent, you sometimes received the error "Constituent can only have one primary phone," even though only one number was marked as primary. The error no longer appears when only one number is marked as primary. | 490820 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
74184 | 19 |
| Previously, Related Staff records were not merging during the constituent merge process. With this fix, these records now merge correctly. | 490507 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
73474 | 12 |
| Technical Change: This fix addresses an issue with submitting addresses through the AddressFinder process with the "For households, submit shared addresses once along with primary contact name" option selected. Previously if two spouse records were included but the household was not, neither individual record's address was included in the submission file. The household record for the two spouse records was not included either. Now the members of the household are all submitted for processing as individuals. If the selection includes the household and the individual household members, the process includes only the primary member of the household as the option states. The database function UFN_COAUPDATE_GETMATCHINGHOUSEHOLDS has been changed to return only the addresses that are shared with a household that is in the selection for the process. | 490340 | Blackbaud.AppFx.AddressManagement.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| New Feature: To improve the performance when users screen a group of constituents through WealthPoint, Target Analytics is making a few updates that will focus on returning the key relationships from GuideStar. On group screenings, known relationships (both people have been screened through WealthPoint and have a connection through a nonprofit found in GuideStar), regardless of form year, and a representative sample of the other relationships from the most recent years will return. For some nonprofit connections, we've seen the total number of relationships returned could be up to 20,000. For you to sort through 20,000 relationships and get the most pertinent information is unrealistic. Therefore, we have simplified the process. These initial results will then help you determine if it is worth the effort to review the additional relationships. And, we want to ensure that you have the choice when to return thousands of relationships for a constituent. If a user does want to see all the relationships, individual WealthPoint screenings will continue to return all relationships. Also, we added an indicator on the wealth and ratings record for constituents who have more network connections available from GuideStar. This indicator plus the initial information returned can help you decide if you want to run an individual WealthPoint screening. In addition, the known relationships will display at the top of the network connections list. With these changes we can improve your WealthPoint group screenings without sacrificing the ability to see all relationships for a constituent. We hope these performance updates will improve your experience group screening constituents in WealthPoint. | 490167 | All assemblies |
8 | |
| This fix resolves an issue in Blackbaud NetCommunity version 6.64 that caused email reports to not record clicks from messages to links outside of the program. | 490143 | Blackbaud.Web.Content.Common.dll Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
BB756184 | 6 |
| Technical Change: This fix addresses an issue with upgrade time in Blackbaud CRM. Previously, upgrades that included revisions to batch type specifications could take an unusually long time. To improve upgrade time, we have optimized the performance of batch revisions. Previously, revisions processed all batch templates, whether or not the templates were active. This could negatively impact upgrade performance and was unnecessary. Now, the upgrade only processes batch revisions for active batch templates. If, after the upgrade, you reactivate a batch template that was inactive at the time of the upgrade, the revision for that batch template is processed at that time. In rare cases, this could cause the reactivation of inactive batch templates to take longer than normal. As part of this fix, we have added a new stored procedure with improved SQL performance. The new procedure, USP_BATCHTEMPLATE_TEMPLATESTOPROCESS, returns the templates to process and replaces the legacy procedure USP_BATCHTEMPLATE_GETLIST. | 490132 | All assemblies |
27 | |
| This fix resolves an issue in Blackbaud NetCommunity version 6.64 that caused organization fields to appear below individual fields on the second step of Event Registration forms after website users opted to register as organizations. | 489938 | Blackbaud.Web.Content.Common.dll Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
BB756162 | 6 |
| This fix addresses an issue when manually editing the conversion rate on a payment record for databases using multicurrency functionality. Previously, when you manually changed the exchange rate when editing a payment, you received an error when you tried to save your changes. | 489725 | All assemblies |
27 | |
| Previously, when the Household Revenue Amounts smart field scans a large amount of data, the process times out and an error appears. With this fix, we updated code to improve the performance of the smart field. | 489496 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
73824 | 12 |
| Previously, when the Household Revenue Dates smart field scans a large amount of data, the process never completes. With this fix, we updated code to improve the performance of the smart field. | 489495 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
74655 | 12 |
| This fix addresses an issue that could occur when a user who is not a system administrator tried to add a user-defined smart query. In certain rare situations, when users who were not system administrators tried to add a user-defined smart query, they would receive the error, "The current user does not have rights to use this simple list." This happened when the users clicked the Results tab of the query. | 489391 | Blackbaud.AppFx.WebShell.WebUI.dll |
74799 | 12 |
| This fix addresses an issue with query performance. The speed at which results are retrieved has improved for all queries referencing the Modeling and Propensity query view. | 489324 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.ProspectResearch.Catalog.dll |
74030 | 12 |
| Previously, the pledge reminder process sometimes produced duplicate rows in its output. This occurred when using either the "Standard reminder output" format or the "Seasonal address reminder output" format for constituents with both a primary addressee and a primary salutation name format and those name formats were different. The V_QUERY_PLEDGEREMINDERPROCESS and V_QUERY_PLEDGEREMINDERPROCESS_SEASONALADDRESSOUTPUT views were modified to address the duplicate rows. | 489020 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
73536 | 12 |
| This fix addresses an issue when clicking through tabs on certain pages. Previously, when you navigated through tabs on a page that had tabs of different lengths, you sometimes would see that your location on the page was not kept when you switched tabs. With this fix, when you click through the tabs, your position on the page does not change. | 488916 | Blackbaud.AppFx.Server.dll Blackbaud.AppFx.WebShell.WebUI.dll |
73241 | 12 |
| This fix addresses an issue with some labels on web dashboards. Previously, when you accessed a web dashboard that contained a gauge (such as a thermometer or a speedometer), a ticker, or a chart, non-alphanumeric characters in the title or other labels were not always readable. | 488780 | Blackbaud.AppFx.WebDashboard.dll |
19 | |
| This fix addresses an issue with appeal queries when they are filtered by something in the query's Appeal > Business unit node and the queries are being run by users who are not system administrators. Previously, the business unit filter was not properly filtering the query results because it was using an incorrect record type. | 488461 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
74771 | 12 |
| This fix addresses an issue in Enhanced Revenue Batch and on the "Add a payment," "Add a pledge," and "Add a recurring gift" screens. Previously, if you changed the constituent or removed the finder number for the revenue, the Effort, Source code, and Appeal fields were set back to blank and you had to re-enter that information. Now, when you change the constituent or remove the finder number, you receive a prompt asking if you want those marketing-related fields to be reset. | 488447 | Blackbaud.AppFx.Fundraising.UIModel.dll |
73556 | 12 |
| This fix addresses an issue with address validation in batch. Previously, any addresses with cities without corresponding state/county values were not able to be validated and the batch process would fail. You must re-run the Address Validation Service Deployment utility from the application start page under "Utilities" in order for this change to take effect. You must then run any address validation processes again in order to validate these addresses. | 488434 | Blackbaud.AppFx.AddressValidation.Server.dll |
72873 | 12 |
| This change applies to an Enhanced Revenue Batch. Previously, when an application was selected on the Apply to commitments screen and the screen was saved and closed, the selected application did not appear correctly in the batch grid. With this fix, the application appears correctly. | 488281 | Blackbaud.AppFx.Fundraising.UIModel.dll |
73566 | 12 |
| This fix addresses an issue including blank results in some ad-hoc queries. Previously, when you used an ad-hoc query field in a "Not one of" filter, and no fields from the field's node were included in the output, the "Include blanks" checkbox for the filter did not work properly. This could sometimes incorrectly omit results from the query. To take advantage of this fix for dynamic selections you saved since upgrading to version 4.0, you must resave those selections. | 488274 | Blackbaud.AppFx.Server.dll |
BB756071 | 7 |
| With this fix, we changed validation when editing payments so incorrect error messages are not displayed when editing payments. Previously, error messages were displayed when editing any split payment with an associated campaign. | 487953 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
74463 | 12 |
| This fix addresses an issue where canceled prospects appeared in the No. prospects column on the My prospect research page. With this fix, canceled prospects are now excluded from this column. | 487675 | All assemblies |
74483 | 21 |
| This fix addresses an issue with some ad-hoc queries in version 4.0 and higher. Starting in version 4.0, you could sometimes get the wrong results in an ad-hoc query if you used the "is not one of" filter for an attribute value, checked both "Include blanks" and "Only return records that do not match any of the selected values," and did not include the attribute as an output field. | 487668 | Blackbaud.AppFx.Server.dll |
BB756042 | 7 |
| Previously, in Enhanced Revenue Batch and Revenue Update Batch, users were not prompted to default recognition credits when manually entering a constituent. With this fix, users are prompted appropriately. | 487604 | Blackbaud.AppFx.Fundraising.UIModel.dll |
74485 | 12 |
| This fix addresses an issue with Direct Marketing emails, which can be accessed from the Marketing and Communications page by clicking "Email marketing" and then "View emails." Previously, if you had an email and used the HTML Source Editor to enter a hyperlink, you would sometimes receive an error because the validation for the required links did not handle the hyperlink correctly. | 487601 | Blackbaud.AppFx.Communications.UIModel.dll |
70151 | 12 |
| Previously, when you edited a payment encumbered by a donor challenge and changed the amount, the payment saved and no error message appeared. Now, an error appears and the payment will not save until you adjust the donor challenge. | 487336 | All assemblies |
74659 | 27 |
| This fix addresses an issue which occurred when editing a group or household record from Enhanced Revenue Batch or Revenue Update Batch. Previously, the "Validate" button was missing when you attempted to edit the address information for these constituents. | 487045 | Blackbaud.AppFx.Constituent.UIModel.dll |
12 | |
| This fix addresses an issue when searching for constituents with the "Check alternate lookup IDs" checkbox marked. Previously, the search could contain fewer results when that that checkbox was marked. | 486941 | Blackbaud.AppFx.Constituent.Catalog.dll |
73608 | 12 |
| Technical Change: When a website user submits a new phone number on the Profile Update Form on your Blackbaud Internet Solutions website and the linked constituent record in Blackbaud CRM does not have phone number data, the number now becomes the primary phone number for the constituent after it downloads to Blackbaud CRM. | 486631 | Blackbaud.AppFx.ApexForm.Web.dll |
12 | |
| Technical Change: When a website user submits organization position data without submitting organization name data on the Profile Update Form on your Blackbaud Internet Solutions website, the 'Could not update the constituent's primary business position because no organization was specified' batch exception occurred in Blackbaud CRM. To avoid this, Blackbaud Internet Solutions now requires the Organization name field when submitting data for the Organization position field. Also, when a user attempts to submit position data without submitting organization name data, the 'Required: Organization name. When you submit position information, you must also submit an organization name' message now displays. | 486594 | Blackbaud.AppFx.ApexForm.Web.dll |
12 | |
| This fix addresses an issue with addresses and the AddressFinder process. Previously, if an address had extra line breaks and it was submitted to Blackbaud using the AddressFinder process, the updated address that was returned sometimes had Address Line 1 duplicated in Address Line 2. The duplicate information no longer appears. | 486498 | Blackbaud.AppFx.AddressManagement.Catalog.dll |
73821 | 12 |
| Previously, an error occurred when users tried to edit an interaction to change the status to pending. With this fix, the form now saves correctly. | 486487 | All assemblies |
74717 | 21 |
| This change applies to a posted revenue record linked to a locked and posted deposit in a Revenue Update Batch. Previously, the adjustment post date was incorrectly added to the revenue record as today's date. With this fix, the adjustment post date is accurately reflected on the revenue record. We also added a warning message communicating that the deposit will be unlinked if the adjustment date is changed. | 486481 | All assemblies |
74716 | 27 |
| Previously, user-defined data lists did not include a time added or time changed on the "Date added" and "Date changed" fields. You could see the date the data lists were added or changed, but not the time. In addition, you were not able to see time stamps when viewing data lists through the web dashboard. To take advantage of this fix for existing user-defined data lists that are displaying the date fields incorrectly, you must open them and re-save them. | 486008 | Blackbaud.AppFx.Platform.WebDashboardParts.dll Blackbaud.AppFx.Server.dll |
71188 | 12 |
| This change applies to an Enhanced Revenue Batch. When multiple, identical addresses exist on a single constituent record where the only difference is that one address is spelled out while the other uses an abbreviation, the following error may display: "The address you entered already exists for this constituent." With this fix, we modified the auto-match process to take into account subtle differences in the address block spellings so that the correct address is matched. | 485991 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll |
68908 | 19 |
| This fix addresses an issue that prevented users from editing a recognition level if the level had a past effective date for the future minimum recognition amount. | 485952 | All assemblies |
74744 | 21 |
| We've updated the login and Add Users Utility to leverage a new process for enhanced security for password management for OCC/OLA/OLRE clients. There are not steps required by clients to take advantage of these changes; however, please test any custom SSO procedures as changes have been made to improve security of passwords and may require an update to customizations to utilize the new procedures. | 485787 | Blackbaud.Web.Content.Common.dll Blackbaud.Web.Content.Core.dll |
BB755912 | 5 |
| This fix addresses a performance issue in the Blackbaud Data Warehouse introduced in version 4.0 of Blackbaud CRM. When using SQL Server 2014 with version 4.0, row-store indexes were replaced with clustered columnstore indexes, which affected performance and could lead to timeout errors when running queries and reports. This fix restores the use of row-store indexes for all supported SQL Server versions. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. If you have already redeployed the Blackbaud Data Warehouse after upgrading to Blackbaud CRM 4.0, we recommend that you reset the warehouse before you apply the service pack, and then perform the refresh after you upgrade to Service Pack 2. You are not required to reset the warehouse before you apply the service pack. However, this specific sequence of tasks will greatly reduce the time it takes to perform the incremental refresh. Otherwise, the incremental refresh could potentially take an hour or more to process. | 485677 | All assemblies |
BB755906 | 8 |
| Technical Change: This fix addresses an issue with the Appeal Performance report. Previously, this report did not include recurring gift revenue. The function "UFN_DESIGNATION_RAISEDBYAPPEAL_INCURRENCY_INLINE" was changed to include revenue generated from recurring gift payments. Report totals after you upgrade may no longer match the previous amounts since recurring gift revenue is now included. | 485371 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This fix addresses an issue with entering constituents and revenue from a list segment used in more than one direct marketing effort into Enhanced Revenue Batch. Previously, if the constituent was committed into a prior batch and then the same constituent and list segment for a different marketing effort was used in another batch, the error "The constituent does not match to this finder number" appeared. This error occurred when constituent matching was enabled in the "Enable/disable matching" configuration task in Administration. | 485261 | All assemblies |
73413 | 30 |
| This fix eliminates a null reference error message when you include the Profile Update Form on your Blackbaud Internet Solutions website and a website user leaves the Date from, Date to, or Graduation date fields blank. To resolve this, the code has been updated to display blank dates successfully when a website user visits the web page. | 485237 | All assemblies |
8 | |
| This fix resolves an issue that caused registrants to appear twice on an event record in The Raiser's Edge when they entered spaces at the end of the First Name field on the Event Registration Form. | 485146 | Blackbaud.Web.Content.Portal.dll |
73426 | 12 |
| Previously, an error message appeared when attempting to access the KPI dashboard from the Mobilize page. With this fix, this error no long occurs. | 485131 | Blackbaud.AppFx.WebShell.WebUI.dll |
73421 | 12 |
| Previously, regardless of what was entered in the threshold value on the Sponsorship greatest need rule set, the dynamically generated rule set always set the value to zero. Now, the greatest need rule set works correctly. In order to utilize this fix, the affected rule set will need to be edited in order to refresh the programs that reference it. | 485036 | Blackbaud.AppFx.Server.dll |
73429 | 12 |
| New Feature: When you design the Profile Update Form for your Blackbaud Internet Solutions website, the Email addresses element under Contact information has changed. To improve email address privacy for website users, the new 'Make my primary email address private' checkbox appears in the design area when you add the element to a form. To display the checkbox on your web page so users can select whether to mark the primary email address as private, select "Yes" in the Privacy enabled row on the Properties pane. Note: When users select this new checkbox on your web page, it also designates their primary email address as private for the Directory and Profile Display parts on a web page. | 484998 | All assemblies |
8 | |
| This fix addresses an issue when loading SQL stored procedures in customizations. Previously, when you used load spec to load a SQL stored procedure, you could sometimes receive an error indicating that the stored procedure already existed. With this fix, existing stored procedures are updated correctly, and new ones are added without error. | 484993 | All assemblies |
21 | |
| Previously, the membership contribution process would not upgrade a member to a higher level when set to renew. With this fix, the process now allows a member to renew and upgrade at the same time if they have given enough to qualify for a higher level. | 484794 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1480.dll Blackbaud.AppFx.Membership.Catalog.dll Blackbaud.Web.Content.Common.dll Blackbaud.Web.Content.Core.dll |
BB749417 | 4 |
| This fix addresses potential query and export performance issues that occur when they are being run by users who are not system administrators and the queries need to check site and constituent record security permissions. If you have created new or edited and saved existing queries prior to this fix in CRM 3.0 SP10, you must open and re-save those queries in order for the changes and performance improvements to take place. | 484375 | All assemblies |
BB755759 | 8 |
| This fix addresses an issue with exclusions for direct marketing efforts. Previously, if you had more than one selection listed on the Exclusions tab of the direct marketing effort and at least one of those selections was not marked as "Locked," you could mistakenly delete a locked selection from the marketing effort. This occurred if you used the multi-select functionality in the "Selections to exclude" list and marked an unlocked selection first and then marked a locked selection. The Delete button for the list was still enabled which allowed you to delete both the marked unlocked and locked selections. Now if you click Delete when you have unlocked and locked selections marked, you receive an error and only the unlocked selections are deleted. The locked selections still appear in the list. | 484148 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Marketing.Catalog.dll |
73475 | 12 |
| This fix addresses an issue when editing second-tier tabs using Page Designer. Second-tier tabs are found in different areas of the program, such as on most tabs of the Constituent record. For example, the Revenue tab of a constituent record has a number of second-tier tabs, such as Revenue Summary and Revenue History. Previously, when you were using Page Designer and tried to edit the properties for a second-tier tab, you could receive an error when you tried to save your changes. With this fix, you are now able to save your changes to properties on second-tier tabs. | 484066 | All assemblies |
21 | |
| This fix addresses an error that you sometimes received when you tried to run a query that included a Site query node. Previously, when you included a filter or output field from the Site query node on your queries, you could receive the error "Object reference not set to an instance of an object." | 483932 | Blackbaud.AppFx.Security.Catalog.dll |
73486 | 12 |
| This fix addresses an issue where users would see duplicate Status columns when mapping the fields of an Event Registrant Batch import. | 483819 | All assemblies |
73493 | 21 |
| This fix improves a slow performance issue when searching for constituents using phone numbers. You can configure search list fields in Administration under Search List Configuration so that a constituent search includes phone numbers. | 483739 | Blackbaud.AppFx.Constituent.Catalog.dll |
12 | |
| Previously, when a source constituent that had a prospect manager with a start and end date was merged to a target constituent with no prospect manager, the source start and end date were not merged along with the source prospect manager. With this fix, the start and end dates are now included. | 483522 | Blackbaud.AppFx.Constituent.Catalog.V1_1.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
73514 | 12 |
| This change applies to pledge and recurring gift records for appeals associated with multiple business units. Previously, upon saving, full amounts were not distributed to all business units. With this fix, full amounts are distributed correctly. | 482854 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This fix addresses an issue when setting feature permissions using Page Designer. Previously, when you used Page Designer to assign page permissions, sometimes the tabs available within the Page permissions screen were duplicated, so that you could see more than one tab with the same name. With this fix, we have corrected the unnecessary duplication of tabs on the screen. | 482636 | All assemblies |
95081 | 21 |
| This fix addresses a performance issue in the Blackbaud Data Warehouse introduced in version 4.0 of Blackbaud CRM. When using SQL Server 2014 with version 4.0, row-store indexes were replaced with clustered columnstore indexes, which affected performance and could lead to timeout errors when running queries and reports. This fix restores the use of row-store indexes for all supported SQL Server versions. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. If you have already redeployed the Blackbaud Data Warehouse after upgrading to Blackbaud CRM 4.0, we recommend that you reset the warehouse before you apply the service pack, and then perform the refresh after you upgrade to Service Pack 2. You are not required to reset the warehouse before you apply the service pack. However, this specific sequence of tasks will greatly reduce the time it takes to perform the incremental refresh. Otherwise, the incremental refresh could potentially take an hour or more to process. | 482577 | All assemblies |
BB755721 | 8 |
| This fix resolves an issue that sometimes caused incorrect values to appear for drop down options in grids on forms. | 482494 | Blackbaud.AppFx.Server.dll Blackbaud.AppFx.UIModeling.RestServices.dll Blackbaud.AppFx.WebShell.WebUI.dll |
67411 | 19 |
| This fix addresses issues with the Prospects and Plans data list and the Prospect Assignments data list found on the Constituent record and My Fundraiser page. Previously, the data lists hid records linked to historical plans. Now, you can mark a check box for these records to appear. Also, the warning icon indicating 90 days of inactivity on the record will not show for historical plans. Finally, records linked to historical plans will be italicized when they are displayed. | 482339 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.MajorGiving.Catalog.dll Blackbaud.AppFx.MajorGiving.UIModel.dll |
73685 | 12 |
| Previously, in an Enhanced Revenue Batch, business units associated with appeals did not display correctly and an error displayed upon committal. With this fix, we made code changes to ensure business units save and commit properly. | 482058 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This fix removes the "Smart Query Instance Edit Data Form" permission from system roles. This feature cannot be granted to or removed from a role because it is not dependent on security. Every user has access to this feature because it is an integral part of the system platform. To eliminate confusion, we have removed it from any roles that had rights to it, since it does not require explicit rights. | 481986 | Blackbaud.AppFx.Platform.ServiceRevisions.dll |
73714 | 12 |
| This fix addresses an issue which occurred when importing constituent information through a Constituent Update Batch. Previously, if a constituent had the constituent ID from Blackbaud CRM in the import file, the "Address is primary" flag in the import file was ignored regardless of the import or batch constituent update settings. Now, if the constituent ID and the ID of the contact information (address, phone, or email) is included in the import file, the update settings are ignored based on the assumption that if you know the constituent ID and the ID of the contact information, you know exactly which records to update through the import. If you do not know the constituent ID and the contact information ID, we assume you are not sure of the exact match with the constituent. Therefore, if you do not include the contact information ID, we do not accept the "Address is primary" flag from the import batch when adding those addresses, regardless of the settings on the import or batch constituent matching settings. | 481812 | All assemblies |
73720 | 27 |
| This fix addresses an issue with site security and revenue batches which occurred when a user was assigned to multiple system roles restricted to different sites. If one system role had site security record access set to "All records," it was assumed the user assigned to that role, in addition to any other roles with more restricted access, would still be able to access all records. In Enhanced Revenue Batch and Revenue Batch, this meant the user could add revenue to or edit revenue for a constituent the user should not have access to. The user received an error in the constituent view window in the batch, but the transaction could still be committed through the batch. Now, that user cannot add or update revenue information using revenues batches. | 481700 | All assemblies |
73743 | 30 |
| Now when you use The Raiser's Edge 7.94 to process profile updates that include email or phone changes, the options to download information on the NetCommunity Page more intuitively affect the Telephone Numbers, Email Addresses, Links, Fax Numbers, and Other tabs of constituent records. For detailed information, see the "NetCommunity Page in The Raiser's Edge" topic in the online help. | 481671 | Blackbaud.Web.Content.Common.dll Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
6 | |
| This fix addresses a performance issue when searching for constituents with a constituency of "Student" or "Alumnus." The Constituency field can be added to constituent searches from "Search list configuration" in Administration. | 481547 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Education.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
73757 | 12 |
| This fix addresses an issue with duplicate constituent matching in Constituent Batch. Previously, Constituent Batch did not use the "In batch" match settings as configured in "Global data entry settings" in Administration. In addition, the duplicate constituent matching in Constituent Batch now more closely resembles the behavior found in other batch types, such as Constituent Update Batch and Enhanced Revenue Batch. Before this fix, Constituent Batch considered only the first and last name fields, in addition to the address fields. Now, Constituent Batch also considers matches in the following additional fields: middle name, title, suffix, lookup ID, alternate lookup ID, phone number, and email address. For information about duplicate matching, see the "Duplicate Constituents and Merge Tasks Guide." This fix addresses issues reported in 481470 and 507278. | 481470 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Constituent.UIModel.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| This change applies to payments previously associated with a matching gift claim. When a payment's constituent was changed, an error displayed upon saving. With this fix, we changed stored procedures to delete all related records, and the error no longer displays. | 481205 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
73774 | 12 |
| Previously, in a Revenue Update Batch, when a user increased the pledge payment amount and left the increased amount unapplied, the message "The payment amount must be fully applied" did not display. With this fix, the message displays correctly. | 481131 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| Previously, evenly split business units for pledges did not default correctly on pledge payments. With this fix, we made code changes to ensure business units default correctly. | 481077 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This fix addresses a security option for batches. Previously, users were able to update projected batch totals from the batch even when they did not have security rights to that option. With this fix, we have removed the "Update projected batch totals" option from the batch screen for users who do not have security rights to update projected batch totals. | 481065 | Blackbaud.AppFx.BatchUI.dll |
73789 | 19 |
| The LoadSpec utility has been updated so that computed columns and constraints which reference the Blackbaud function UFN_BUILDFULLADDRESS will not prevent country address formats from being updated. | 480841 | All assemblies |
8 | |
| This fix addresses an issue with site security and marketing efforts. Previously, a user who did not have site security for a specific site could incorrectly create a marketing effort from a communication template that was restricted to that site. In addition, a user was not able to create an effort from a template even if they did have the proper security when the template used a communication name pattern that was restricted to that site. Now, the user who did not have site security for a specific site is restricted from being able to create an effort based on the site security of the communication template. However, if a communication template uses a name pattern that is restricted by site, users can still create efforts based on the communication template with proper site security even if the users cannot access or edit the name pattern itself. | 480769 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Marketing.Communications.Catalog.dll |
19 | |
| This fix addresses an issue where the Plan participant drop down would not populate correctly when editing a step while adding a prospect plan. | 480686 | All assemblies |
73829 | 21 |
| This fix addresses performance issues which occurred when calculating segment counts for a marketing effort. Previously when you clicked "Calculate segment counts" under Tasks on the marketing effort record, there could have been performance issues if segments were based on a query which had simple data list or code table fields used as filters. To address this, we added additional metadata to several query views in Service Pack 2 with item 475518. With this item, we have made the same changes to additional query views. | 480284 | Blackbaud.AppFx.Campaign.Catalog.dll Blackbaud.AppFx.CommPrefs.Catalog.dll Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.ConstituentGroups.Catalog.dll Blackbaud.AppFx.Education.Catalog.dll Blackbaud.AppFx.EventManagement.Catalog.dll Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.MajorGiving.Catalog.dll Blackbaud.AppFx.Marketing.Catalog.dll Blackbaud.AppFx.Membership.Catalog.dll Blackbaud.AppFx.ProspectResearch.Catalog.dll |
73579 | 12 |
| This fix addresses a problem when trying to add new collection fields in the SDK. In version 4.0, when you attempted to add a collection field using the SDK, sometimes the add procedure did not work. | 480205 | All assemblies |
8 | |
| This fix addresses an issue with marketing-related emails in CRM. Previously, conditional tags in the HTML in the body of the email message were not supported, but now they are. | 480182 | BBUIModelLibrary.dll Blackbaud.AppFx.Communications.UIModel.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.HtmlProcessor.dll Blackbaud.AppFx.Marketing.NetCommunityIntegrationCatalog.dll Blackbaud.AppFx.UIModeling.Core.dll Blackbaud.AppFx.XmlTypes.dll |
73863 | 12 |
| Technical Change: This fix addresses an issue which occurred when copying communication templates in Marketing and Communications. The issue occurred only if the template was set up to exclude constituents with one or more required solicit codes. Previously, when you made a copy of the template, the required solicit code exclusions were copied to the new template as default solicit code exclusions. The required solicit codes do not need to be copied at all as they appear automatically on every communication template. If you made a copy of the new template, you received an error message because the original required solicit code exclusions were copied to the newest template a second time--once from the original template and once from the copy of the original template. Templates cannot have multiple instances of the same solicit code exclusions. To address this issue, we made a change to USP_MKTCOMMUNICATIONTEMPLATE_COPY so that it now removes any required solicit code exclusions from the copied exclusions before the new template is created. Solicit codes that are set as required appear automatically on every communication template. You can make solicit codes required from the "Solicit codes" task under Configuration on the Marketing and Communications page. On the "Select features and defaults" tab on the communication template, you can click "Exclusions" to view required solicit codes. | 480147 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Marketing.Communications.Catalog.dll |
73865 | 19 |
| Technical Change: Previously, auction item donors and purchasers could not receive donor constituency since auction items were not included in the revenue filter. Auction items have now been added to the filter so that these donors and purchases can now receive donor constituency. | 480111 | All assemblies |
73867 | 21 |
| Previously, the smart field list would not load when the sites list for any smart field was longer than 255 characters. This fix truncates the sites list at 255 characters and the list loads normally. | 480091 | All assemblies |
BB755495 | 8 |
| This fix addresses an issue which occurred when transactions downloaded into Enhanced Revenue Batch in CRM contained existing constituents with new contact information: addresses, email addresses, or phone numbers. Previously, the constituent in the batch would get flagged for review as a potential duplicate. When the match was confirmed, the transaction was processed, but the new contact information did not have the correct information source. The information source is specified on the "Configure integration" screen accessed from the Web Transactions page in CRM. Now the transaction is processed and the new contact information does have the correct information source. | 480021 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| When you applied Service Pack 10 for version 3.0 of Blackbaud CRM, some revisions could take a long time to run if your database had a large number of batch templates or attributes. With this fix, the revisions run more efficiently and the process is completed faster. | 479886 | All assemblies |
BB751635 | 8 |
| This fix addresses an issue with site security and direct marketing efforts. Both marketing plans can be associated with a specific site. Previously, if a direct marketing effort was created from a marketing plan with one site, but then associated with an appeal from a different site, an error occurred and the marketing effort could not be saved. Now you can save the marketing effort successfully even when the related plan and appeal have different sites. | 479844 | All assemblies |
BB755483 | 27 |
| This fix addresses a usability issue in the constituent record. Previously, when you navigated content in a constituent record by clicking on tabs, the page would jump back to the top every time you clicked a tab, even if you had scrolled down the screen before you clicked the tab. With this fix, the screen remains at the same place as it was before you clicked the tab. | 479699 | All assemblies |
8 | |
| Technical Change: This change affects contact information in Constituent Update Batch. Previously, when you imported information into a Constituent Update Batch, the only contact information that would appear in the imported batch was the contact information found in the import file. Starting in version 3.0, we made a change and included all contact information for the constituents in the imported batch instead. To mitigate the risk of impacting customizations due to the change, we have now added ROWORIGINCODE flags on the ADDRESSES, PHONES, and EMAILADDRESSES collection fields in Constituent Update Batch. This field will have a value of 2, 1, or 0. A value of 2 indicates that the contact information previously existed on the constituent and was automatically added to the batch row by the system during import, even though it was not present in the import file. A value of 2 could also indicate that the contact information record was matched to an existing constituent's address through the duplicate matching functionality. A value of 1 indicates that the contact information was present in the import file or was added manually when adding a batch row. A value of 0 indicates that the origin of the contact information was not determined. The record could have been added to the batch row by any method, including those that would normally give a value of 1 or 2. The ROWORIGINCODE value could change from a value of 1 to a value of 0 if you use manual duplicate resolution in the batch. | 479135 | All assemblies |
8 | |
| New Feature: To improve flexibility in managing pending activity information, the Pending Activity data list has been converted to list builder format to include more advanced options for sorting, navigating and customizing data in the list. You can access the Pending Activity list builder on the Pending Activity second-tier tab on the Fundraiser tab of the constituent record or the Pending Activity tab on the My Fundraiser page. In order to opt-in to the Pending Activity list builder, you will need to access design mode on the current Pending Activity datalist, and change the list builder "Visible" setting to "True" and the datalist "Visible" setting to "False." | 478926 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.MajorGiving.Catalog.dll Blackbaud.AppFx.MajorGiving.UIModel.dll |
12 | |
| This fix addresses a performance issue with the ETL refresh. Previously, the ETL refresh could take longer to run after you upgraded to Blackbaud CRM version 4.0 or later. This performance issue affected the total refresh time as well as refresh time for individual packages. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 478500 | BBDW.ReportDB.Catalog.dll BBDW.ServiceRevisions.dll BBDWETL - SSIS Reporting Package |
74234 | 12 |
| New Feature: You can now choose whether you want to use the primary address on a record or choose a specific address for a Gift Aid Tax Declaration. You can also choose whether you want to use the constituent's name or an alias in the declaration. By default, all existing declarations use the constituent's name and primary address. To choose a different address or alias, you must update those associated declarations. The selected name and address are then used for R68 Gift Aid processing. | 478446 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.GiftAid.Catalog.dll Blackbaud.AppFx.GiftAid.UIModel.dll |
19 | |
| This fix eliminates an [ArgumentNullException: Value cannot be null.Parameter name: s] error message on the Payment 2.0 part on your website. To resolve this, the code has been updated to handle the occasional case of XMLTYPES being NULL in the CMS_SessionVariableBackup table. This applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 478443 | All assemblies |
BB755405 | 8 |
| This fix addresses an issue that occurred when merging two constituents who are members of the same group or household record. Previously, the group membership start and end dates did not always accurately reflect the total duration of the individual's group membership. If the individual constituent was a member of the same group for consecutive, but not overlapping, periods of time, the merged constituent showed only the most recent group membership term start and end dates. | 478441 | All assemblies |
BB753326 | 8 |
| New Feature: This fix allows UK clients to use gross amounts in recognition programs. When you add a recognition program, you can now select to use the gross amount. You can also now query on either net or gross amounts. These calculation changes are reflected in the Constituent Recognition Program Process and in the Recognition Revenue Report. | 478439 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.GiftAid.Catalog.dll Blackbaud.AppFx.Membership.Catalog.dll Blackbaud.AppFx.Membership.UIModel.dll |
19 | |
| This fix updates the schema for submitting R68 Gift Aid claims in the United Kingdom to HRMC from version 1 to version 2. As a part of this schema change, overseas addresses are now marked as such, instead of including a postcode element. | 478430 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.GiftAid.Catalog.dll |
12 | |
| This fix addresses an issue introduced in Service Pack 1 which could generate an error during the ETL refresh. Previously, the ETL refresh process would fail when the BBDW.FACT_FINANCIALTRANSACTIONLINEITEM table had a designation list that was too long. This fix truncates the designation list at 4,000 characters and you no longer receive this error when you refresh the ETL. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 478272 | All assemblies |
8 | |
| This change applies to the Corporate Structure page for a constituent record. Previously, when a large amount of information existed for a constituent, the Corporate Structure page timed out. With this fix, the page loads in an appropriate amount of time. | 478044 | All assemblies |
BB737594 | 8 |
| This fix addresses an issue where users received an error message when adding matching gift claims to payments with multiple splits when a solicitor had been added to at least one split. | 477752 | All assemblies |
94406 | 21 |
| This fix eliminates an "Object reference not set to an instance" error message when you download a Blackbaud Internet Solutions profile transaction in Blackbaud CRM that generated from a User Interests Form, a deprecated Profile Form part, or a deprecated User Email Preferences Form. This error occurred when the website user's constituent record did not contain an education 'From' date on the education history record found on the Education tab of the constituent in CRM. This happened because the program did not check for a previous education 'From' date when the batch download process began. With this fix, transactions process successfully and the error message does not appear. | 477537 | All assemblies |
BB749537 | 8 |
| This fix addresses the error "Error: Conversion failed when converting from a character string to unique identifier" which sometimes occurred when viewing KPIs for a direct marketing effort from the KPIs tab on the Effort Settings tab. | 477510 | All assemblies |
BB755341 | 8 |
| Previously, when a planned gift addition was added as revenue and the Generate GL distributions checkbox was not selected, the addition showed a post status of "Not posted" and included a post date. Now, the form uses the Generate GL distributions checkbox to calculate the post date and post status code. | 477387 | All assemblies |
74313 | 21 |
| This fix addresses an issue with deleted attributes in the Blackbaud Data Warehouse. Previously, when you deleted modeling or propensity attribute values, these deleted values still appeared in your queries. With this fix, the deleted attributes no longer appear. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete a full refresh. | 477276 | BBDW.ReportDB.Catalog.dll BBDW.ServiceRevisions.dll BBDWETL - SSIS Reporting Package |
74319 | 12 |
| This fix addresses an error which occurred when importing an Educational History Update Batch. The error occurred when the import process was set up to use the "Quick find" option for "Search list fields." | 477161 | All assemblies |
BB754241 | 8 |
| This fix addresses an issue that could sometimes occur when you tried to use legacy help in Blackbaud CRM. Previously, you were not able to access legacy help in a new Blackbaud CRM 4.0 installation. With this fix, you now see no errors when you access help after choosing to use the legacy help. To change the type of help used in your database, under Administration, click "Configure help type" and select whether you want to use the standard help panel or the legacy help option. | 477109 | All assemblies All assemblies |
74331 | 27 |
| When you use Blackbaud Internet Solutions, this fix eliminates a "gateway specified does not support tokenizing" message when a website user submits a recurring gift on the Advanced Donation Form part. This change updates how the token is stored so the transaction processes successfully. This is an update to 445906 that was previously resolved in Service Pack 10. | 476797 | All assemblies |
8 | |
| This fix eliminates an "Object reference not set to an instance" error message when you download a Blackbaud Internet Solutions profile transaction in Blackbaud CRM that generated from a User Interests Form, a deprecated Profile Form part, or a deprecated User Email Preferences Form. This error occurred when the website user's constituent record did not contain an education 'From' date on the education history record found on the Education tab of the constituent in CRM. This happened because the program did not check for a previous education 'From' date when the batch download process began. With this fix, transactions process successfully and the error message does not appear. | 476433 | All assemblies |
8 | |
| This fix addresses an issue with the Revenue History tab of a constituent record. Previously, the content was especially slow to load or timed out when using a revenue filter. | 476395 | All assemblies |
BB750317 | 8 |
| Previously, when manually entering a constituent in an Enhanced Revenue Batch, users were not prompted to reset recognition credits. This caused duplicate constituents to be created through the batch. With this fix, users are prompted appropriately and duplicates are no longer created. | 476376 | Blackbaud.AppFx.Fundraising.UIModel.dll |
74775 | 12 |
| This fix addresses an issue with the Ask Ladder Response report. Previously, when you selected to include "All marketing efforts" and clicked "View report," you sometimes received the error: The 'CURRENTAPPUSERID' parameter is missing a value. The error was caused by a timeout when retrieving the data for the report. | 476327 | All assemblies |
BB752513 | 8 |
| This fix removes the character limit on the Essay element of Survey parts in Blackbaud Internet Solutions. Previously, the Essay element was limited to 225 characters. With this fix, the limit has been eliminated. | 476254 | All assemblies |
8 | |
| The Donation Form, Payment, and Payment 2.0 parts now include the Middle name field under Additional fields. The change allows you to include it so your organization meets the Canadian Revenue Agency's requirements for donation receipts. | 476044 | Blackbaud.AppFx.ContentManagement.Catalog.dll Blackbaud.AppFx.ContentManagement.Parts.ShoppingCart.UI.dll Blackbaud.Web.Content.Portal.dll |
74793 | 12 |
| This fix addresses performance issues which occurred when calculating segment counts for a marketing effort. Previously when you clicked "Calculate segment counts" under Tasks on the marketing effort record, there could have been performance issues if segments were based on a query which had simple data list or code table fields used as filters. To address this, we have added additional metadata to several query views, including the Address Processing Option Addresses, Designations, Educational History, Prospect Plans, Relationships, and Revenue Recognition Credits query views. | 475518 | All assemblies |
BB755213 | 8 |
| Previously, when annual recognition programs with the same program levels occurring in different years were merged during constituent merges, the status of the earlier program record was set to "Inactive (Merge)." With this fix, the status of the program record sets to "Inactive (Merge)" when you merge constituents with annual recognition programs at the same level and with the same date achieved. | 475489 | All assemblies |
BB755210 | 8 |
| This fix addresses an issue with social media accounts for constituents. Previously, when you added a social media account on the constituent's Contact tab, the "User ID" field was not required and was not always automatically populated based on the "Profile page URL." A hyperlink to the social media account appeared in the "Contact information" column only when a "User ID" was entered. Now the hyperlink to the social media account appears in the "Service" column of the data list regardless of whether a "User ID" was entered. | 475486 | All assemblies |
BB753723 | 8 |
| New Feature: The constituent record now includes the Opportunity Tile, which summarizes opportunity information for constituents who are major giving prospects. You can add and edit a constituent's opportunity information from the tile, including the opportunity's plan, the plan's primary manager, and other information about the opportunity. | 474696 | All assemblies |
8 | |
| This fix addresses an issue with attributes marked as "Allow only one per record" sometimes not showing up in the Blackbaud Data Warehouse. This could happen when attributes were deleted and then re-added to a record before the Data Warehouse was refreshed. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 474462 | All assemblies |
8 | |
| This fix addresses an issue with the Revenue Gift Aid query. Previously, different application gift aid refresh dates in the query could incorrectly display multiple rows per revenue. The query now shows the most recent refresh data across the applications. | 474447 | All assemblies |
BB754777 | 8 |
| This fix addresses an issue that sometimes happened with where fully qualified email links from BBIS and BBDM emails that directed to a BBIS site with a different domain from the default site lost the email tracking information in the redirect, meaning that email conversions to donations might not be tracked. | 474446 | All assemblies |
8 | |
| This change applies to the GL setup area of Administration. Previously, the GL mapping to a Constituency did not respect the Constituency end date. With this fix, we made changes to ensure expired Constituencies are not used with GL mapping. | 473961 | All assemblies |
BB754164 | 8 |
| This fix addresses an issue with deleted attribute categories. Previously, deleted attribute categories were incorrectly still appearing in Blackbaud Internet Solutions and in ad-hoc queries in Blackbaud CRM. Because these deleted attribute categories were still in use, if you tried to add a new attribute category with the same name and record type as a deleted one, you received an error. This happened because attribute categories of the same record type must have a unique name. With this fix, deleted attribute categories are fully deleted, including deleting them from Blackbaud Internet Solutions and Query. This now allows you to add a new attribute category that matches the properties of a deleted one without receiving an error. While this fix prevents this situation going forward, it does not address existing attribute categories that were already deleted before this fix is applied. For attribute categories that were deleted before this fix, you may receive an error if you try to add a new attribute category matching their name and record type. | 473248 | All assemblies |
21 | |
| This fix addresses an issue with the data list on the Review Receipts tab of the Receipts page. Previously, if the list took longer than 30 seconds to load, the list would time out. To address this, we have increased the length of the list's timeout setting. | 473088 | All assemblies |
BB754528 | 8 |
| This fix addresses an issue with segment and package information when you add payments. Previously, if the payment was added without using a source code, the segment and package information did not appear on the payment. | 472879 | All assemblies |
74577 | 32 |
| This fix addresses an issue with certain ad-hoc queries. Previously, if you used a field from the Selections node as an aggregate field in the output of an ad-hoc query, and you used the field as a filter on the "Set sort and group options" tab, you sometimes received an error. This prevented you from previewing or saving the query. | 472399 | Blackbaud.AppFx.Server.dll |
74628 | 12 |
| This fix addresses an issue with the History tab on the Marketing Effort Activation Status page. You can now download exceptions successfully. | 472075 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This fix improves a performance issue which occurred when exporting an ad-hoc query which contained another ad-hoc query. | 471872 | Blackbaud.AppFx.CommPrefs.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
19 | |
| This fix addresses an issue with constituent merge that occurred when the merge process included an "Excluded constituents" selection which excluded all of the source constituents that would be merged. In that situation, the merge process terminated unexpectedly or started to run but never completed with a status message of "Beginning merge..." Now, the merge process will skip those constituents without experiencing the issue. | 471543 | Blackbaud.AppFx.Constituent.Catalog.dll |
74818 | 19 |
| This fix addresses an issue when you edited the date format for import processes. Previously, the date field was not case-sensitive, which could create confusion between using "m" for minutes and "M" for months. When you tried to enter an uppercase letter such as "M," the system would automatically change it back to the lowercase "m." With this fix, you can now enter uppercase or lowercase letters and the format respects your entry. Date formatting still considers the lowercase "m" to mean minutes and the uppercase "M" to mean months. To take advantage of this change, you may need to edit import format options for formats that are not working as expected. | 471454 | All assemblies |
8 | |
| This fix addresses an issue with the Plan Status report for marketing plans in Marketing and Communications. Previously, if the marketing plan had an activated marketing effort associated with it and you tried to view the Plan Status report, you received an error. Now the report runs without the error. | 471085 | All assemblies |
BB754920 | 8 |
| This fix addresses an issue that sometimes occurred when you ran a query using constituency filters. Previously, when you used constituency filters on a query and selected the option to "Only return records that match all selected values," you could receive an error. | 470672 | Blackbaud.AppFx.Server.dll |
74858 | 12 |
| This changes fixes the failing revisions for a Revenue Update Batch. By increasing the Rejection message field size, the revisions run successfully. | 469431 | All assemblies |
BB754873 | 8 |
| This fix addresses an issue saving attribute form extensions. Previously, when you tried to add and save an attribute form extension from Administration, you sometimes received an error. | 469285 | Blackbaud.AppFx.Platform.SqlClr.dll |
12 | |
| This fix addresses an issue with committee member information on the Members tab of the committee. Now, the committee member's start and end dates appear for each role on the committee in the data list. | 468999 | All assemblies |
BB737666 | 21 |
| New Feature: To help you find and track social media accounts for your prospects, we added a new data service to WealthPoint screens. PeopleGraph, a Dun & Bradstreet company, uses name and email address information from your constituent records to find social media data in their Social Media Finder service. The social media data that returns on a wealth screen is stored on a new Social Summary tab on the wealth and ratings record. On the Social Summary tab, you can track the social media accounts for your prospects and if you have the Social Media Finder subscription, social media accounts, profile images, demographics, and ratings appear here after a WealthPoint screen. | 468251 | All assemblies |
2 | |
| Previously, when entering a new pledge or recurring gift through an Enhanced Revenue Batch, a message prompted users to reset recognition credits. With this fix, the prompt no longer displays. | 468127 | Blackbaud.AppFx.Fundraising.UIModel.dll Blackbaud.AppFx.Fundraising.UIModel.dll |
74064 | 12 |
| This fix addresses an issue that could occur when upgrading to version 4.0 of Blackbaud CRM. Previously, when you upgraded from version 3.0 Service Pack 6 to version 4.0, you could receive a revision error. | 467825 | All assemblies |
21 | |
| Previously, navigation tree grids loaded with every node expanded. To improve performance, now all navigation tree grids only expand to the record the tree is being launched from, and the rest are minimized. | 467787 | All assemblies |
BB755068 | 8 |
| With this change, we improved performance for an Enhanced Revenue Batch and a Revenue Update Batch in the following scenarios: when entering constituent information in a batch row and when entering information on the Apply to commitments screen for constituents associated with a large number of commitments. | 467706 | All assemblies |
8 | |
| Previously, a time zone conversion error displayed when trying to run the Download Exchange Data process and the version of Exchange being used was unestablished. With this fix, the default processing mode is now set to Exchange 2010 when the version is unestablished to help prevent this error message in the future. | 467670 | All assemblies |
BB747213 | 8 |
| When you schedule a Blackbaud Internet Solutions email for the second week in a month, this fix prevents the program from sending it prematurely the first week of the month. To resolve this, an integer division error in the date calculation has been fixed. | 467664 | All assemblies |
8 | |
| New Feature: To improve efficiency with group management, you now have the ability to add multiple constituents to a group at once, rather than just one constituent at a time. When you add a new group, you now have the option to pick a selection of constituents, in addition to selecting individual constituents. You also have the option to use a selection when you add additional members to an existing group. There is a separate security permission so that you can decide which system roles should have rights to do this. There is no undo for this feature nor is there "delete group members in bulk" functionality, so choose your selection carefully. When someone in a selection is already an active member of the group, nothing changes with the group member. When someone in a selection is a previous or inactive member of the group, the constituent becomes an active group member again and start date for the constituent's group membership is reset to the date entered. | 467462 | All assemblies |
27 | |
| When you use a Profile Update Form on your Blackbaud Internet Solutions website, this fix prevents the "An item with the same key has already been added" error message from appearing when a website user attempts to submit the form. This message appeared when multiple email address types were designated as private for the Email Addresses element. To resolve this issue, the USP_CODETABLE_TABLEENTRY_DATALIST has been replaced with the USP_EMAILADDRESSTYPECODE_GETLIST stored procedure for this action. | 467433 | All assemblies |
BB754790 | 8 |
| This fix eliminates error messages related to notification failures (and other unknowns) that potentially occurred during the BBPS Transaction Reconciliation Business Process. Now, valid transactions download successfully to Blackbaud CRM and The Raiser's Edge. This fix applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 467420 | All assemblies |
BB754706 | 8 |
| To improve performance for Blackbaud Internet Solutions, the index IX_TEAMFUNDRAISINGTEAMCAPTAIN_CONSTITUENTID has been added. | 467387 | All assemblies |
8 | |
| Previously, revenue deleted via an adjustment appeared in search results. With this fix, deleted revenue is no longer returned. | 467237 | All assemblies |
BB753465 | 8 |
| Previously, when using a custom batch template derived from an Enhanced Revenue Batch, the Apply to commitments screen did not automatically display for a constituent with outstanding commitments. With this fix, we updated code to ensure the screen automatically displays when outstanding commitments exist. | 466965 | All assemblies |
BB754159 | 8 |
| With this change, we modified SQL function to ensure the correct set of tables are used during validation. | 466753 | All assemblies |
8 | |
| This fix addresses an issue which occurred when adding an education history item to a constituent on the Education tab. Previously, when you searched for the educational institution and selected a country such as Canada, the list of states was not limited to those associated with Canada. Now the list of states or provinces is limited to the ones set up for the country in the "Countries and states" configuration task in Administration. | 466592 | All assemblies |
73954 | 21 |
| This change applies to a Revenue Update Batch. Previously, when a user changed a posted pledge payment through a batch, adjustment fields were disabled. This resulted in an error during validation. With this fix, a user can now enter correct values for adjustment fields and commit the batch. | 466382 | All assemblies |
BB753367 | 8 |
| As part of our normal product improvement processes, we review our security measures, protocols, and infrastructure on an ongoing basis. Blackbaud Internet Solutions was automatically updated in this release to include security improvements which address vulnerabilities that could potentially compromise the integrity of our product. | 464759 | All assemblies |
8 | |
| New Feature: With this release, we improved functionality for pledge installments to improve quality, and increase reliability, accuracy, and consistency. These improvements ensure accurate and consistent behavior when adding or editing a pledge through a record, Enhanced Revenue Batch, or Revenue Update Batch in the following fields: Installment amount, No. installments, and No. installments remaining. | 464595 | All assemblies |
BB752100 | 8 |
| This fix resolves an issue when you commit a BBIS Event Registration Transaction Batch for event registration transactions from Blackbaud Internet Solutions. Previously, when the expense (for example, a cost or benefit) exceeds the event fee for a registration, the total receipt amount became negative instead of zero. This caused a constraint violation message to appear. To resolve this issue, the USP_BBNC_COMMITEVENTREGISTRATIONPAYMENTADD stored procedure has been updated. | 464027 | All assemblies |
BB754404 | 8 |
| This fix resolves an issue when you commit a BBIS Event Registration Transaction Batch for event registration transactions from Blackbaud Internet Solutions. Previously, when the expense (for example, a cost or benefit) exceeds the event fee for a registration, the total receipt amount became negative instead of zero. This caused a constraint violation message to appear. To resolve this issue, the USP_BBNC_COMMITEVENTREGISTRATIONPAYMENTADD stored procedure has been updated. | 464026 | All assemblies |
BB754404 | 8 |
| The names of direct marketing efforts are based on Communication Templates which use a Communication Name Pattern. The name pattern gives a marketing effort a name such as "Channel-LaunchDate-Appeal" to uniquely identify each effort. The "Trailing separator" in the name pattern is what indicated whether or not the different name parts were separated by hyphens, underscores, asterisks, and so on. If the "Trailing separator" was set to <Space>, the separator was ignored and no space was used. This fix corrects the issue so name patterns with a "Trailing separator" of <Space> correctly include spaces in the name of the direct marketing effort. | 463794 | All assemblies |
BB754606 | 8 |
| Technical Change: This fix resolves an issue with long designation names on the Donation Form part in Blackbaud Internet Solutions. When you previously configured the part and selected a designation with a long name, the field did not adjust to display the entire name. With this fix, the designation field now displays the entire designation name so you can confirm you selected the intended designation for your website. The Designation field on a web page also now displays the entire designation name when a donor clicks the drop down menu. To resolve this, the DesignationLink.ascx and DonationDisplay.ascx files have been updated in the back end of the database. | 463584 | All assemblies |
21 | |
| New Features: In Blackbaud Internet Solutions, to improve performance and delete email messages and newsletter issues in bulk, you can now run a process to permanently delete these from your database. In Email, when you delete an email message or newsletter issue, it only soft deletes. When you soft delete email, it removes from the user interface, but the data remains in the database. To delete this email permanently from the database, schedule the new Delete email permanently organization setting in Administration. Tip: To prevent the program from running this process, select Never. By default, this is selected when you upgrade to this version. | 462873 | All assemblies |
21 | |
| This fix resolves an assembly mismatch issue for a third party time zone component. Services such as the CMS Data Integration Business Process would fail with a method not found exception. | 462599 | Blackbaud.Web.Content.Common.dll Blackbaud.Web.Content.Core.dll |
1 | |
| This fix addresses an issue that happened with split designations when downloading transactions from Blackbaud Internet Solutions when using the UK version of Blackbaud CRM. Previously, transactions could download without Gift Aid numbers. This only happened for databases that used multiple sites. | 462581 | All assemblies |
27 | |
| Technical Change: When you create or edit a web page, this fix forces a 100 character limit on the page name. This avoids potential errors that may occur when page names exceed this character limit. This change applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 462411 | All assemblies |
69432 | 21 |
| Technical Change: This fix addresses an issue with correspondence processes and households when the output format is set to "Formatted mail correspondence output." Previously if the "Include household member processing" checkbox was marked on the output format Processing options screen of a correspondence process and the process was set to include a household and one individual member of the household, the mailing included both the individual as well as the household. Now the mailing excludes the household so the constituent can be addressed individually. From the Add or the Edit correspondence process screens, when the Output format is set to "Formatted mail correspondence output," you can click the edit button for the Output format field to access the Processing options screen. | 461892 | All assemblies |
BB754146 | 2 |
| This fix increases the default font size for all HTML fields including the view, add, and edit forms for constituent notes. The new font size is now larger for ease of reading. | 461809 | All assemblies |
BB743530 | 2 |
| Previously, query filter options sometimes did not appear correctly in WebUI. In some instances, the query filter did not display the 'Only return records that do not have a value equal to the selected value,' 'Only return records that match all selected values,' or 'Only return records that do not match any of the selected values' checkboxes. With this fix, these filter options now appear correctly. | 461316 | All assemblies |
BB753784 | 8 |
| This fix increases the details provided in the business process status messages for the Full Constituent Duplicate Search and the Incremental Constituent Duplicate Search. You can now also see the additional details in the Windows application event log after you run duplicate search processes. To take advantage of the additional details in the Windows application event log, you must edit the health monitoring section of your web.config file to record more detailed event logs for these processes. This detailed logging can help when you work with Blackbaud Customer Support to research an issue with the process. | 460865 | Blackbaud.AppFx.Constituent.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This fix addresses an issue with the Membership contribution process. Previously, if revenue was added after the initial qualifying revenue but outside of the membership's renewal window, the subsequent revenue was counted toward the next renewal rather than as additional revenue. For example, for a given membership program, a donation was made on 1/1/2013 for $50 and the constituent then qualified for level one in the membership program. A second donation of $50 was made two months later, which was before the membership program's renewal window was open. The following January, the constituent made a donation of $50 to renew the level one membership. However, the renewal was counted as $100 as a combination of the second and third donations. | 460801 | All assemblies |
2 | |
| This fix allows you to add child tabs (or second-level tabs) to a tab, or edit the child tabs on an existing tab using the Blackbaud SDK. Now, when you use the SDK to author specs that support the AlterExistingPages element, you can add AlterTabs elements to AlterTab elements. | 460765 | Blackbaud.AppFx.Platform.SqlClr.dll Blackbaud.AppFx.XmlTypes.dll |
12 | |
| Previously, the Export process page sometimes did not respect the 'rights to all query view' system privilege. This caused some users who had rights to see all query views to have problems when accessing export processes from this page. With this fix, users with rights to all query views can now see the appropriate export processes on this page. | 460750 | All assemblies |
BB754004 | 8 |
| This fix addresses an ETL failure that sometimes happened when the Recognition field on the RPT_GIVINGLIST table was more than 4,000 characters long. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 459868 | All assemblies |
2 | |
| With this fix, a Blackbaud Internet Solutions password reset email no longer sends to the intended recipient plus all users linked to the recipient (possibly as a result of a duplicate merge or duplicates in the database). Now, a password reset email only sends to the user with the most recently created account. | 459525 | All assemblies |
8 | |
| This fix addresses a "The current user does not have the rights to use this form" error which occurred for users without explicit rights to the Default Country View Form who tried to search for a committee. With this fix, the error no longer appears. | 453508 | All assemblies |
BB755222 | 8 |
| This fix resolves an issue that caused the program to use a large amount of server memory when it generated downloadable export and data list files in XLSX format. | 453496 | All assemblies |
BB716079 | 2 |
| This fix addresses an issue with the "PAIN.008" file generated with the direct debit process for bank accounts with "Europe (SEPA)" selected as the banking system. Previously, the creditor IBAN was truncated at 19 characters. The file now includes all 24 characters of the IBAN. Previously, the debtor address information in the file did not include the country code, post code, or city information. This information has been added to the "PAIN.008" file. With the additional information included in the file, the direct debit transactions can now be processed. | 453404 | All assemblies |
BB753950 | 2 |
| This fix addresses an issue which occurred when you deleted rows from a batch with more than 65 rows, which meant the batch had more than one page. Previously, if you deleted rows from the first page of the batch, saved the batch, and then went to the second page of the batch, you could have received an error or lost a row from the second page of the batch. Now, when you do that, no errors occur and the batch rows remain intact. | 453283 | All assemblies |
BB753446 | 2 |
| Previously, the ETL process would not complete if you had too many constituent attributes. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 453206 | All assemblies |
2 | |
| This fix addresses an issue when deleting attribute categories. Previously, you were able to delete an attribute category in Administration, even if that attribute category was in use on a record. This was not intentional, since attribute categories that are in use should not be deleted. With this fix, the program does not allow you to delete an attribute category that is in use on any record. | 453059 | All assemblies |
71172 | 21 |
| Previously, when opening an existing batch that contained no applications, an error displayed and the batch could not be opened. With this fix, we updated the batch edit load stored procedure to check whether a designation exists for additional applications before updating them. The error no longer displays and the batch opens correctly. | 453016 | All assemblies |
BB733534 | 2 |
| Previously, the ETL process could fail if you merged a dynamic selection and a static selection. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 452245 | All assemblies |
2 | |
| This fix addresses a formatting issue with email messages that included a receipt grid from a Payment 2.0 part from Blackbaud Internet Solutions. Previously, when you changed the format of the receipt grid in the part, your formatting changes did not carry over to emails that included the receipt grid. Now, any styling changes you make to the receipt grid in the Payment 2.0 part are also reflected in email messages that include the receipt grid. | 452070 | All assemblies |
BB742662 | 27 |
| This fix addresses an issue with sponsorships in Blackbaud Internet Solutions where an error occurred when you entered a new user registration and sponsorship at the same time and selected the "Enable CRM security for linked CMS users" option. | 451907 | All assemblies |
BB742214 | 27 |
| This fix resolves an issue with the Donation Form on your Blackbaud Internet Solutions website. Previously, when a donation web page included a default source, the website user was unable to navigate to the donation form from the donation summary page after selecting the designation. With this fix, the donation form now appears correctly. To resolve this, the DonationDiaplay.ascx.vb file has been updated. | 451886 | All assemblies |
BB753479 | 2 |
| This fix addresses an issue with deceased constituents in queries. Previously, when you queried on deceased constituents, the Date changed and Changed by fields in the query did not always represent the most recent change. | 451720 | All assemblies |
BB753327 | 2 |
| To improve email performance, this fix significantly reduces the time it takes to process a Blackbaud Direct Marketing email effort. | 451645 | All assemblies |
BB750474 | 2 |
| Previously, a constraint error appeared during database revisions if the database contained bad data for Job Occurrence date ranges. Now, the revision runs successfully and the data is repaired. To utilize this fix, you will need to run the repaired revision. | 451582 | All assemblies |
8 | |
| Previously, the timeout settings controlled by the web.config file did not impact timeout for user-defined data lists, so these could still time out even when you had extended the timeout options in your web.config file. With this fix, the timeout settings on the web.config file apply to user-defined data lists. | 451361 | All assemblies |
8 | |
| This fix extends the character limit for job titles. Previously, job titles associated with relationships and employment history were sometimes limited to 50 characters. With this fix, job titles throughout the program are now limited to 100 characters. | 451213 | All assemblies |
BB747732 | 2 |
| This fix addresses an issue when you edited the date format for business process output such as exports. Previously, the date field was not case-sensitive, which could create confusion between using "m" for minutes and "M" for months. When you tried to enter an uppercase letter such as "M," the system would automatically change it back to the lowercase "m." With this fix, you can now enter uppercase or lowercase letters and the format respects your entry. Date formatting still considers the lowercase "m" to mean minutes and the uppercase "M" to mean months. To take advantage of this change, you may need to edit export format options for formats that are not working as expected. | 451207 | All assemblies |
8 | |
| This change applies to the process of adjusting a posted payment paid by stock. Previously, if a stock was sold and set to "do not post," when the payment form was saved, an error displayed that no mapping existed for sold stock sale payment methods. With this fix, when the payment adjustment is saved, the error no longer displays even when no mapping exists. | 451172 | All assemblies |
BB754095 | 8 |
| New Feature: The "Delete audit data" global change now includes the option to select "Constituent images." When you add or edit profile pictures for constituents, each instance of the image is saved to the constituent audit tables, which can take up an unexpected and unwanted amount of space in the database. Now when you run the "Delete audit data" global change, you can specify to also delete constituent images from the audit tables. The images are not deleted from the constituent records, just from the audit tables. Existing "Delete audit data" global changes remain the same after you upgrade. In order to take advantage of the new setting, you must edit existing "Delete audit data" global changes and mark "Constituent images." | 450915 | All assemblies |
27 | |
| Technical Change: In Marketing and Communications, you can click Segments to view information about segments and segment groups. With this fix, on the Segments tab, we have added three additional filters: Group, Type, and Category. To do this, we created a new function UFN_QUERY_MKTSEGMENT_2 that is now used instead of UFN_QUERY_MKTSEGMENT. | 450685 | Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll Blackbaud.AppFx.Marketing.Catalog.dll Blackbaud.AppFx.Marketing.UIModel.dll |
73190 | 12 |
| This fix resolves an issue that prevented you from entering paperless direct debit instructions after you downloaded transactions from Blackbaud Internet Solutions to Enhanced Revenue Batches. The issue occurred when donors entered direct debit information for financial institutions in the United Kingdom that were not previously entered into the database. | 450607 | All assemblies |
BB749167 | 2 |
| This fix eliminates extra carriage returns (for example, when you press the Enter key on the keyboard multiple times) from appearing on a constituent record in the Address field. This occurred when a website user entered the carriage returns for address information when submitting donation information on your Blackbaud Internet Solutions website. To resolve this, the file AddressUIBase.vb has been updated. | 450593 | All assemblies |
BB753503 | 2 |
| This fix resolves an issue for education updates on the Profile Update form on your Blackbaud Internet Solutions website. As of version 3.0 service pack 9 and higher, no action occurred after the website user clicked Update to submit the transaction. With this fix, the Submit button now appears after the user clicks Update so the transaction can be sent successfully to Blackbaud CRM. To resolve this, the DateFormatHelper.vb file has been updated. | 450462 | All assemblies |
BB740054 | 2 |
| This fix addresses an issue with the number of scholarships listed on the Education tab of a constituent. Previously we counted the scholarship "Total funds" summary row as an instance of a scholarship, even when the constituent did not have any scholarships. So even constituents with no scholarships had "Scholarships (1)" in the data list. Now, the "Total funds" are displayed in the Scholarships list, but the data list count is shown as zero when there are no scholarships for the constituent. | 450273 | All assemblies |
73216 | 27 |
| New Feature: When a website user submits an event registration on your Blackbaud Internet Solutions website, and you process it in the BBIS Event Registration Transaction Batch, you can now select "Donor" in the Registrant column on the Guests tab when you view transaction details. You can also change the registrant from Donor to Linked constituent, New constituent, or Unknown guest. Previously, you could select "Donor" in the ClickOnce version of Blackbaud CRM. | 450183 | Blackbaud.AppFx.BBNCSvc.dll Blackbaud.AppFx.BBNCSvc.UIModel.dll Blackbaud.AppFx.BBNCSvc.UIModel.dll |
19 | |
| This change applies to environments where CRM and BBIS are hosted on different servers. Previously, in this environment, users who logged into BBIS were denied access to download attachments from their sponsorships. With this fix, modified code now provides proper credentials to be passed and allows the attachments to download. | 450026 | All assemblies |
BB745967 | 2 |
| This fix addresses an issue when entering fuzzy dates when the date elements are separated by periods, such as in 01.10. For Hungarian and Bulgarian users who use this date format, this resulted in fuzzy dates not working properly in the system. With this change, you can now use periods to separate elements in fuzzy dates in fields such as Birth date. | 449767 | All assemblies |
8 | |
| Previously, when querying on registrant restrictions, the Type and Options fields were text fields. Now, users can select registrant restriction types and options from a drop-down menu instead of typing in the value. | 449225 | All assemblies |
73221 | 21 |
| New Feature: To improve password reset security in email messages, you now select a user login password reset page from the 'Create link to a special page' option on the HTML Editor when you design an email message. When you use this link in an email and a recipient clicks the link, a secure page appears with a Forgotten Password field for the user to enter their email address. After the email address is submitted, another email sends to the user. That email contains another link that returns the user to the password reset page on your website. Use this new functionality in place of the Password merge field in email messages with a Registered Users data source. This change applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 449144 | All assemblies |
2 | |
| This fix addresses an error that could sometimes occur when you merged a Microsoft Word document from an export. Previously, when the memo field on the export was longer than 255 characters, you received an error when you tried to complete the merge. | 449110 | All assemblies |
8 | |
| Previously, activated marketing efforts that had gifts returned and were linked to an effort were not appearing on the Breakeven analysis report. The package page view calculates total cost per piece as unit cost plus insert cost per piece. The breakeven data list was only using unit cost. Now, the insert cost per piece is included, so the marketing effort will appear on the Breakeven analysis report. | 448337 | All assemblies |
2 | |
| This fix resolves an issue where incorrect last payment dates and amounts were displaying on cancelled membership records and the Lifetime tile did not correctly update for recurring membership programs. | 448230 | All assemblies |
8 | |
| This fix resolves an issue for the error message 'The INSERT statement conflicted with the CHECK constraint CK_BBNCTRANID_ISUNIQUE' that may appear when special characters exist in a profile transaction from Blackbaud Internet Solutions and you download it to Blackbaud CRM. When special characters exist, the program fails the transactions. Previously, the program also assigned each transaction the same ID. With this fix, the program now assigns different IDs that appear on the Failed Transactions tab to help identify the problem. | 448105 | All assemblies |
BB753565 | 2 |
| Previously, members of membership programs with recurring payments were not being returned in constituent searches filtered by member constituency. With this fix, these members now appear in search results. | 447956 | All assemblies |
BB753598 | 8 |
| Previously, when expanding a recognition record, the detail form would not load. This fix improves the load performance of the detail view on the Recognition Programs data list on the Constituent page. | 447952 | All assemblies |
BB753521 | 8 |
| When you use an Advanced Donation Form part on your Blackbaud Internet Solutions website to process recurring gifts, the credit card token is now processed in the transaction and saved to the database so future recurring gift payments can process successfully. Previously, the part did not process and save the token which prevented the program from charging future payments. | 447887 | All assemblies |
BB753346 | 2 |
| Previously, when validating or saving a Revenue Update Batch that included duplicate recognition credits, a timeout error displayed. With this fix, we updated stored procedures to ensure the error no longer displays and no further duplicate recognitions are created. | 447884 | All assemblies |
BB752113 | 2 |
| This change applies to a Revenue Update Batch. Previously, an error displayed during the validation of payments with multiple installments and business units. With this fix, we updated stored procedures to ensure the batch is saved and validated appropriately. | 447829 | All assemblies |
BB753470 | 2 |
| This fix addresses an issue with the disposition field on the pledge one-off form. Previously, the disposition field was unavailable for Enterprise customers when unlocking the basic development module. With this fix, the disposition field is available when unlocking the basic development module. | 447822 | All assemblies |
BB752821 | 2 |
| This change applies to non-administrative users using a radius search in Blackbaud CRM. Previously, users could not perform a radius search from the Mapping page in Prospects. With this fix, we changed stored procedures to ensure users can now perform a radius search with optimal performance. | 447810 | All assemblies |
BB753337 | 2 |
| This change applies to an Enhanced Revenue Batch. Previously, when a user created a recurring gift, added a payment, and committed the batch, the account system defaulted to the user's default account system. With this fix, we updated stored procedures to ensure the order of account system assignment is respected for recurring gifts upon commit. | 447809 | All assemblies |
BB753169 | 2 |
| This fix addresses an issue with revenue audit history report date formats. Previously, dates in the revenue audit history report would display in the United States format when set to a non-United States system locale. With this fix, the dates display in the correct format. | 447806 | All assemblies |
BB745602 | 2 |
| Previously, when a list was imported and the State field was mapped to State instead of State Abbreviation, the segment member data list would show a blank for State. With this fix, the segment member data list now shows State, if mapped, and if State Abbreviation is not mapped. | 447688 | All assemblies |
BB753721 | 2 |
| This fix resolves an issue that caused the program to revert to the default context record type when you edited user-defined data lists. | 447553 | All assemblies |
BB753537 | 2 |
| Previously, Currency was a drop down when only one option, Organization, was available. With this change, Currency is now a text label. | 447468 | All assemblies |
BB753717 | 2 |
| This fix resolves an issue that caused an error message to appear in Blackbaud Internet Solutions when you attempted to update the advanced properties of an appeal element for the Email Signup form after the appeal category was removed from the program. Now the appeal category is highlighted in red in the properties section and "Invalid Category" appears as the name. Also, a message appears to indicate the category no longer exists in the program. | 447464 | All assemblies |
BB753423 | 2 |
| Previously, import exception files did not properly handle fields that contained commas or double quotes. Existing import exception files will still present this issue if they have fields containing a comma and not properly wrapped by double quotes, so you may need to update your exception files if this issue persists. | 447418 | All assemblies |
BB753550 | 8 |
| This fix resolves an issue that caused an error message to appear when you created a data list from an ad-hoc query that used the "Value (Money)" field from the "KPI Values" node in the KPIs query view. | 447414 | All assemblies |
BB753556 | 2 |
| This change applies to a batch template based on an Enhanced Revenue Batch type with additional attribute category columns. Previously, when the batch using this template was edited and saved, the program erased installment receipt amounts. With this fix, we updated batch template code to ensure all installment receipt amounts are correctly applied when editing and saving the batch. This fix also applies to all pre-existing batch templates. | 447408 | All assemblies |
BB753348 | 2 |
| This fix addresses an issue with membership transactions downloaded from your website into a Blackbaud Internet Solutions membership dues batch. Previously, if the transaction caused an exception when the batch was committed, the exception batch did not always contain the membership transaction or the error message. | 447402 | All assemblies |
BB741311 | 2 |
| This fix addresses an error that could occur when you tried to synchronize Active Directory or LDAP groups of users to Blackbaud CRM system roles. In rare cases, while synchronizing, you could receive the error "Object reference not set to an instance of an object." | 447391 | Blackbaud.AppFx.RoleSync.exe Blackbaud.AppFx.RoleSync.exe Blackbaud.AppFx.Security.Catalog.dll Blackbaud.AppFx.Security.ClientComponents.dll Blackbaud.AppFx.Security.UIModel.dll |
70189 | 12 |
| This fix addresses a performance issue with the Giving Activity report. Previously, the Giving Activity report would sometimes not complete and would time out. With this fix, the Giving Activity report should perform as intended. | 447340 | All assemblies |
BB752427 | 2 |
| This fix addresses an issue that occurred when selecting "base" for the currency on the Designation Progress report and Fundraising Hierarchy Progress report in a multicurrency environment. Previously, the report would always run with the "organization" currency selected, regardless of what currency the user selected. With this fix, the report runs with the selected currency. | 446785 | All assemblies |
BB753566 | 2 |
| Technical Change: Auction donations and auction purchases are now included in the Constituent revenue amounts and Constituent revenue application amounts smart fields as filtering parameters. | 446781 | All assemblies |
BB751059 | 21 |
| This fix addresses an issue where an error displayed when job occurrence dates for volunteers were reassigned. Now, job occurrences can be reassigned to new dates, and the error no longer displays. | 446776 | All assemblies |
BB750594 | 2 |
| This fix addresses an issue when using the quick search field. Previously, if you searched for a member and typed "Firstname Lastname" into the quick search field, the Member Search screen appeared with "Firstname Lastname" in the Last/Org/Group name field. Now, the first name and last name are correctly parsed on the Member Search screen. | 446771 | All assemblies |
BB747943 | 2 |
| Previously, several membership forms displayed currency for amounts only in US dollars. With this fix, these amounts now display the appropriate currency. | 446742 | All assemblies |
BB740546 | 21 |
| This fix addresses an issue with constituents who are members of a member program with levels that are both dues-based and contributions-based. The issue occurred for a constituent who had qualified for a membership in a contributions-based level for a program, but then that membership lapsed. If the constituent was also a member of a dues-based membership program, the constituent was not automatically renewed or rejoined to the contributions-based level even when the constituent had enough qualified revenue for the level. | 446636 | All assemblies |
BB735163 | 2 |
| When you use API endpoints that allow custom donation parts to use Blackbaud's secure payment page, an error no longer occurs when the URL of the custom page contains a query string parameter. Previously a Null Reference error appeared when the user returned from the secure page back to the custom page. | 446603 | All assemblies |
2 | |
| Previously, when a user attempted to edit a recurring job occurrence, the date range would default to 1/1 to 12/31 of the current year. With this fix, the correct dates now appear. | 446224 | All assemblies |
BB753599 | 2 |
| This fix addresses an issue with post dates and expiration dates in Membership Dues Batch. Previously, if you changed these dates in the batch grid view while in Review mode, saved the batch, and then re-opened the batch, the original dates still appeared in the "Enter membership dues" form view. However, the correct dates were used when you committed the batch. Now when you edit the dates, the information is updated in both views of the batch. | 446221 | All assemblies |
BB753574 | 2 |
| This fix resolves an issue that sometimes caused the Blackbaud Internet Solutions Communication Preferences form to not save data that was entered by website users. The issue occurred when their historical appeal preferences were associated with invalid email addresses and those preferences were not related to the form. Now, the form only saves appeal preferences that are related to the form. | 446000 | All assemblies |
BB751250 | 2 |
| This change applies to the Assign prospects in bulk process in Prospects. Previously, historical (completed) plans were included and updated when the process ran. With this fix, we changed stored procedures to ensure only active plans are filtered and included in the process. | 445886 | All assemblies |
BB753384 | 2 |
| This change applies to the Apply to commitments screen through an Enhanced Revenue Batch when the following is true: A split gift is entered, Multicurrency is enabled, and a UK account system is used. Previously, currency symbols in the Additional application row displayed incorrectly. With this fix, currency symbols display correctly. | 445885 | All assemblies |
BB753124 | 2 |
| Previously, prospect plan participants were not appearing in the drop-down field when filing an unplanned contact report. With this fix, prospect plan participants now correctly appear in the drop-down field on the "File an unplanned contact report" screen. | 445884 | All assemblies |
BB752339 | 21 |
| This change applies to Opportunities and Asks within Major Giving Management. Previously, the Total revenue committed values displayed in organization currency instead of base currency when no fundraiser was provided. With this fix, we updated stored procedures to ensure organization currency is used. | 445882 | All assemblies |
BB751744 | 2 |
| The email address in the appeals element of the Blackbaud Internet Solutions Communication Preferences form now defaults to a website user's primary email address unless the user previously selected a different address as the default. If the primary address is invalid, the program uses the first valid address that is saved for the user. | 445853 | All assemblies |
BB751250 | 2 |
| This change applies to an Enhanced Revenue Batch. Previously, when a batch was generated from an import process and a file mapping template was used, the following error displayed during batch validation: UC_CONSTITUENT_LOOKUPID. With this fix, we updated stored procedures and the error no longer displays. | 445713 | All assemblies |
BB752463 | 2 |
| This fix resolves an issue that caused the program to sometimes not save filter operators for user-defined data lists properly. The issue occurred when you included an output field in an ad-hoc query multiple times with different names, created a data list from the query, and then used one or more of the fields as data list filters. To apply this fix to existing user-defined data lists, you must edit or recreate them. | 445588 | All assemblies |
BB753561 | 2 |
| This fix prevents an issue that caused an error message to appear when the primary key field in a user defined smart query did not include a system record ID, and the query definition was used to create selections and export processes. To resolve the issue for existing selections and export processes, you must manually update the primary key field in the smart query definition under Administration, Application, Shell design and then recreate the export process or selection. System record IDs appear in the list of primary key options when you include them as output fields in the ad-hoc query you use to create the smart query definition. Note, for a constituent view smart query, include the "Constituent record" field. For a revenue view smart query, include the "Revenue record" field. | 445583 | All assemblies |
BB753056 | 2 |
| Administrators no longer need to grant modify permissions for a server application pool user to access the Aspose.Words.zip file in the vroot\bin folder where the program is installed. Previously, the application pool user needed to access the file to resolve an error that sometimes appears the first time a Word merge is performed after the 3.0 service pack 8 or 4.0 versions of the program are installed. | 445406 | Blackbaud.AppFx.Platform.ServiceRevisions.dll Blackbaud.AppFx.Platform.UIModel.dll |
1 | |
| New Feature: Now when Blackbaud Internet Solutions website users register for the site with social media login credentials, the program sends them a confirmation email to welcome them to the site. Previously, the program did not send these users an email. The program uses the same welcome email template you configure for other website registrants, but it merges "<social media username> via <social media account>" in the Username field. | 445362 | All assemblies |
2 | |
| New Feature: We have added a new query source view. The query view "Revenue Recognition Credits (from the Blackbaud Data Warehouse)" is similar to the existing "Revenue Recognition Credits" query view, but shows results from the Blackbaud Data Warehouse. Queries from the data warehouse only include fields available in the warehouse, and they only show results as of the last time the ETL process was run. You can see when the data was last updated on the Preview results tab of the New Ad-hoc Query screen or the Edit Ad-hoc Query screen. You can also see the last updated date on the Results page when you run the query. | 445211 | All assemblies |
2 | |
| This change applies to the Fundraising Purpose Revenue report. Previously, pledge write-off amounts were incorrectly added to the New Commitments total rather than subtracted. With this fix, we updated stored procedures to ensure pledge write-off amounts are now subtracted appropriately. | 445156 | All assemblies |
BB753455 | 2 |
| This change applies to a committed Enhanced Revenue Batch. Previously, a user was able to right-click on a batch row and select to edit the constituent. With this fix, we removed the ability to edit a constituent through the right-click option as editing a constituent should not be permitted on committed batches. | 445112 | All assemblies |
BB753351 | 2 |
| New Feature: To improve flexibility in managing interaction information for individual constituents, the Interactions data list has been converted to list builder format to include more advanced options for sorting, navigating, and customizing data in the list. Group and household constituents already use a new list builder format. You can access the Interactions list builder on the Interactions sub-tab on the "Documentation and Interactions" tab of a constituent record. In order to opt-in to the Interactions list builder for individual constituents, you will need to access design mode by clicking the Toggle design mode on button in the upper right corner of the program. On a constituent record, click Edit tabs in the design mode view at the top of the record. On the Edit page tabs screen, find the Interactions tab and edit it. Go to the Sections field. There will be two list builders shown: one for groups and one for individuals. The one for groups will already have the "Visible" setting set to "=CBool(Page.Fields!ISGROUP)" and that should remain unchanged. Change the "Visible" setting for list builder for individual constituents to "=Not CBool(Page.Fields!ISGROUP)" and the data list "Visible" setting to "False." | 445092 | All assemblies |
30 | |
| Previously, an error displayed for the Prospect Plan List API when the API was accessed outside of the application. With this fix, we changed the data type for CONSTITUENTNAME from Guid to String, and the error no longer displays. | 444927 | All assemblies |
BB752999 | 2 |
| This fix addresses an issue with the constituent application amount smart field. Previously, when a constituent application amount smart field was created for household member recognition and a site was selected, an error would occur. With this fix, the smart field functions as designed. | 444925 | All assemblies |
BB752411 | 2 |
| This fix addresses an issue that occurred with General Ledger setup access for user roles. Previously, a user with a role assigned to 'all sites' was able to see all account systems even though the role had no General Ledger rights granted to it. With this fix, a user with an 'all sites' role will be unable to see all of the account systems in General Ledger setup. | 444924 | All assemblies |
BB752575 | 2 |
| New Feature: Additional fields are now captured on a recurring gift's activity timeline. These fields are associated with the payment method of "Direct debit - pay installments automatically" and "Standing order." | 444890 | All assemblies |
2 | |
| New Feature: "Cash" and "Check" now appear as Payment method field options and are reflected in the following locations: Add a recurring gift screen; Edit payment method details screen for a recurring gift, Transaction summary section for a recurring record; amendment details on the Activity tab of a recurring gift; Update recurring gift statuses business process; revenue queries; Revenue Update Batch, Enhanced Revenue Batch, and Sponsor Batch; and the Add, transfer, and reassign sponsorship screens. | 444868 | All assemblies |
2 | |
| This change applies to an Enhanced Revenue Batch. Previously, when a batch included a large number of recognitions in the batch row, an error displayed during validation and committal. With this fix, we changed a stored procedure to improve performance and the error no longer displays. | 444654 | All assemblies |
BB752343 | 2 |
| This fix addresses an issue with revenue in a Direct Debit Return Batch. If a direct debit revenue transaction is added, posted, and adjusted in CRM but the actual charge is rejected by the bank, the transaction is returned to CRM in a Direct Debit Return Batch. Previously, users would receive an error for that transaction when they tried to commit the batch. Now the error no longer appears and the rejected transactions in the Direct Debit Return Batch are committed with the amounts adjusted to zero. | 443774 | All assemblies |
BB750858 | 2 |
| This change applies to an Enhanced Revenue Batch where the application's API is used to create a custom script. Previously, when an Enhanced Revenue Batch was set to ensure manual resolution for duplicate detection, auto-matching was used instead. This occurred when the batch was saved using the API. With this fix, we updated legacy code to ensure auto-matching is disabled. | 443689 | All assemblies |
BB750011 | 2 |
| This fix addresses an error that you sometimes received when you tried to edit user-defined data lists. This would happen when the data list had a deleted smart field included in its output. When this happened and you tried to delete the data list, you received the error "This ad-hoc query has output or filter fields specified that are no longer present in the source query view." | 443620 | All assemblies |
BB753433 | 8 |
| Previously, when accessing the Reconcile Opportunities tab on the Major Giving Management page in Prospects, the tab occasionally timed out due to poor performance. With this fix, the tab loads in a timely manner without error. | 443515 | All assemblies |
2 | |
| This fix addresses an error that occurred when adding or editing volunteer availability information on the Availability tab of a constituent's volunteer record. The error occurred only when the user's browser settings were set to the Finnish language. | 443124 | All assemblies |
BB750756 | 2 |
| When you configure a Query Results Display part in Blackbaud Internet Solutions, smart queries from Blackbaud CRM no longer appear in the results on the Query Search page. This eliminates an error message that occurred when you attempted to select a smart query. You can select any type of ad-hoc query to use with this part, but smart queries are not supported. | 442301 | All assemblies |
BB752959 | 2 |
| When you use Blackbaud Internet Solutions and match guest information in a BBIS Event Registration Transaction Batch, the program no longer matches gift criteria when the guest information includes a blank email address. For example, on the Auto-match tab in the Configure integration task in Blackbaud CRM, you use First name, Last name, and Email address for matching field criteria and you select the Exact match only checkbox. When a website user submits an event registration transaction that includes guest information without an email address, the program does not link the guest to an existing CRM constituent record. Previously, the program matched the guest to an existing record when the email address was blank but first and last names were the same. | 442098 | All assemblies |
2 | |
| When a website user attempts to update an address on the profile update page on your Blackbaud Internet Solutions website, the error message 'Sequence contains no elements' no longer appears. This occurred when the user's address included an inactive country on the constituent record in Blackbaud CRM. To resolve this the ProfileMultiAddressControl.aspx.vb and GeographicalRegions.vb files have been updated. | 442086 | All assemblies |
BB753065 | 2 |
| This fix addresses an issue that occurred when searching for events with search list record security enabled. Previously, events would appear on the Event Search screen even when a user did not have access to the site associated with the event. | 441981 | All assemblies |
BB748775 | 2 |
| 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. | 441447 | All assemblies |
BB752885 | 2 |
| This fix addresses an issue with user-defined data lists in Administration. Previously, when you added a "Registrants" data list with the "Registration type" field included as an output field (found under the node "Registrations\Registration Options"), you received an error when you tried to save the data list. The error occurred only when you marked to filter the "Registration type" field on the "Set save options" tab of the data list. Now the data list saves correctly. | 441389 | All assemblies |
BB753246 | 2 |
| This fix resolves an issue that caused the feature menus to not render properly in Internet Explorer 10. | 441338 | Blackbaud.AppFx.Server.dll Blackbaud.AppFx.WebShell.WebUI.dll |
1 | |
| New Feature: To make it easier to sort an invitation list on a special event record in alphabetical order, invitee names are now formatted as "Last name, First name." | 441286 | All assemblies |
8 | |
| This fix addresses an issue with the "Will attend" field in the event capacity summary section of a multi-level event. Previously, when you marked a registration for the supporting event as canceled, the "Will attend" number on the main event was not updated. Now the "Will attend" number on both the supporting event, as well as the main event, are updated properly. | 440793 | All assemblies |
BB752947 | 2 |
| This fix allows you to see available fields for data lists when you edit expressions using Page Designer in WebUI. Previously, you could only see available fields in the data list when you accessed Page Designer using ClickOnce. You can now see available fields when you access Page Designer through WebUI. | 440548 | All assemblies |
2 | |
| New Feature: You can now customize your KPI dashboard. From the dashboard, click "Customize dashboard" under Tasks. On the new "Customize a KPI dashboard" screen, you can create pages and tabs within pages to organize your KPIs. | 439875 | All assemblies |
BB753380 | 8 |
| New Feature: To help you better sort through and find your queries, we have added the ability to expand all or collapse all query folders in the Information Library. | 439874 | All assemblies |
8 | |
| This fix resolves an issue that sometimes caused an error to appear when you created user-defined data lists and used certain fields from specific query views as filters. For example, an error appeared when you used the Constituents query view and the "Expected date" field from the Constituents\Interactions node as a data list filter. | 439840 | All assemblies |
BB752982 | 2 |
| This fix resolves an issue that required a manual update to the webserver's web.config file when you installed the program. Previously, you added a namespace attribute to the runtime.assemblyBinding element in order for custom workflow assemblies to work. | 439838 | All assemblies |
8 | |
| This fix resolves an issue that sometimes caused the program to not respond when users with slow internet connections clicked the double green arrows in datalists to expand the rows. Although the issue is resolved, users with slow internet connections may still experience a delay between clicking the arrows and the rows expanding. | 439833 | All assemblies |
BB751066 | 2 |
| This fix addresses an issue in Query when calculating how many consecutive years a constituent was a member of a recognition program. Previously, changes in a constituent's recognition level that occurred within the same year were being counted multiple times so the "Years consecutive" counts were incorrect. | 439618 | All assemblies |
BB751435 | 2 |
| 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. | 439229 | All assemblies |
BB752986 | 2 |
| This change applies to a Constituent Update Batch where the following exception messages appear: One or more duplicate constituent exception messages and two or more exception messages of a different kind (for example, an import error message and user set error message). In this scenario, when the duplicate is resolved using the duplicate resolution screen and the "Automatically go to the next duplicate exception" is selected, the batch freezes after resolving the last duplicate exception. This is caused by the other two exception messages processing in an infinite loop. With this fix, the last duplicate exception processes correctly and the batch no longer freezes. | 438937 | All assemblies |
2 | |
| This fix addresses an issue with the constituent search in Enhanced Revenue Batch. Once marked, the "Match all criteria exactly" checkbox now remains marked from search to search. If you no longer want to match all criteria exactly when searching for a constituent, you must click the search button and unmark the checkbox. | 438369 | All assemblies |
8 | |
| Previously, advanced search options in Enhanced Revenue Batches did not carry over the next time you used that batch type. With this fix, the options you select for this batch type are sticky and carry over when you use the batch type again. | 438368 | All assemblies |
2 | |
| This fix resolves an issue that sometimes caused the program to stop responding when you added or edited an export definition that used a custom query view. The issue occurred when the developer who used the Infinity SDK to create the query view included an extra space at the end of the PathAlias element of a relationship node. | 438170 | All assemblies |
2 | |
| This fix resolves an issue that caused the program to sometimes change the sort order of the site hierarchy in places where you can view or edit it. If you manually applied a custom order, we recommend you review the hierarchy to confirm that it appears in the order you selected. | 438168 | All assemblies |
BB752923 | 2 |
| The message 'Data form could not be loaded. String or binary data would be truncated.' no longer appears when you attempt to open transaction details in a BBIS Profile Update Transaction Batch in Blackbaud CRM. Previously, this appeared when the website user submitted a business job title that was longer than supported. | 437971 | All assemblies |
BB751969 | 2 |
| This fix resolves an issue that caused the program to include multiple instances of guest email addresses on constituent records. The issue occurred when you registered the guests for multiple events from a single Blackbaud Internet Solutions event registration form. | 437618 | All assemblies |
2 | |
| Previously, when you accessed data lists through the web dashboard, the Date added and Date changed fields did not include a time added or changed. | 436151 | All assemblies |
BB752926 | 2 |
| This fix helps prevent constituents from receiving duplicate emails sent from Blackbaud Internet Solutions. | 436116 | All assemblies |
BB751626 | 2 |
| New Feature: Now when you export a datalist that includes date fields to Excel, the spreadsheet includes date and time information when a time is saved for any of the dates in the list. Previously, the spreadsheet only included date information, so when a date included the latest time in the day such as 11:59:59.999 PM for a membership expiration, Excel rounded the date to the next day. | 434849 | All assemblies |
BB746722 | 2 |
| This fix addresses an issue that sometimes happened when committing an AddressFinder batch. Previously, when you committed a batch you sometimes received an error for rows updating an address. This happened if some of the constituents sharing that address listed it as their primary address and others listed a different primary address. | 434058 | All assemblies |
BB752719 | 2 |
| When you process a profile update transaction without primary business information from Blackbaud Internet Solutions, an error message no longer appears when you validate the BBIS Profile Update Transaction Batch that includes the transaction in Blackbaud CRM. | 434018 | All assemblies |
BB752292 | 2 |
| This change applies to a Revenue Update Batch that includes split designations for pledges associated with Business Units. Previously, upon saving the batch, a duplicate key exception occurred. With this fix, the exception no longer occurs. | 434002 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Fundraising.UIModel.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| This fix addresses an issue with the grant fundraising request summary widget. Previously, the widget would continually load with an error when the browser was set to a non-English language locale. With this fix, the widget functions as intended. | 433992 | All assemblies |
BB752335 | 2 |
| This fix addresses an issue that occurred when a user selected not to update gift fees when editing a payment. Previously, the message "The sum of the gift fee distribution amounts do not equal the total gift fees for this transaction" would appear and the gift fee amount would be zero. Now, when selecting to not update gift fees, all gift fees are reversed for the related removed applications. Otherwise, the gift fee amounts should remain the same and the message should not display when editing a payment. | 432846 | All assemblies |
2 | |
| New Feature: To prevent accidentally removing a part from an unintended web page (on a single site or shared across multiple websites), you can no longer delete a part that still exists on a page. When you attempt to do this, a message now displays to inform you the part cannot be deleted because it is on a page. To identify the page the part is on, select the part's Usage tab. This applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 431055 | All assemblies |
2 | |
| When you enter a phone number on a constituent record or a Constituent Update Batch, the phone number is formatted according to the country selected for the record. However, when there is no country selected, the phone numbers were left unformatted. With this fix, phone numbers for records without a country selection are formatted according to the format selected for the database's default country. | 430763 | All assemblies |
BB752525 | 2 |
| The additional members drop-down menu and table now include relationship in the name label in the membership dues form and the membership dues batch. | 430315 | All assemblies |
8 | |
| New Feature: Previously, when you clicked "Save" from the Export Definition screen in Administration, the program saved your changes and closed the screen. Now, you have the option to click "Save" to save your changes and continue working with the export definition, or click "Save and close" to save your changes and close the screen. | 429067 | All assemblies |
2 | |
| New Feature: Previously, when you clicked "Save" from the Ad-hoc query screen in Analysis, the program saved your changes and closed the screen. Now, you have the option to click "Save" to save your changes and continue working with the query, or click "Save and close" to save your changes and close the screen. | 429066 | All assemblies |
2 | |
| This fix eliminates an 'Object must be of type String' error message when you attempt to add a designation (or fund) that has not been configured to accept revenue for eStore. This fix applies to Blackbaud Internet Solutions and Blackbaud NetCommunity. | 428630 | All assemblies |
BB748583 | 2 |
| This fix addresses an issue with email addresses added for household members when marked as "Copy email address to household and members," as well as "Do not send email to the address." When the email address was first added, it was copied to the household and member records, but the "Do not send" information was not copied. | 427057 | All assemblies |
BB752215 | 8 |
| This fix addresses an issue with constituent batches and education information. Previously, when you added education information to an individual constituent record, you could have a graduation date with any graduation status, such as for future graduation dates. However, in batches and imports, if you wanted to include a graduation date for a constituent, the graduation status had to be "Graduated." Now you can add education information for constituents in batch with a graduation date and with any graduation status so the two data entry methods are consistent. | 427052 | Blackbaud.AppFx.Constituent.UIModel.dll |
12 | |
| This fix addresses an issue with adding members to a committee. Previously, on the "Add a committee" screen, if you added members to the committee on the Members tab and then added a different constituent as the primary contact on the Details tab, the primary contact was saved as a regular committee member only and not as the primary contact. Now, the primary contact is saved correctly. This fix also makes all of the group add screens ("Add a group" screen; "Add a committee" screen; and "Add a group" screens from Auction Item Batch, Enhanced Revenue Batch, and Sponsorship Batch) behave consistently when you remove the primary contact. Now, when adding a committee or when adding a constituent group from batches, if you add a constituent as the primary contact on the Details tab, the constituent is automatically added on the Members tab. However, if you then remove the constituent from the "Primary contact" field on the Details tab on any of these screens, the constituent will also be removed from the Members tab. Previously, the constituent was removed from the Members tab for only the "Add a group" screen. | 427050 | Blackbaud.AppFx.ConstituentGroups.UIModel.dll |
19 | |
| This fix resolves an issue when clicking search on the Personal Notes part in Blackbaud NetCommunity. | 426552 | Blackbaud.Web.Content.Core.dll Blackbaud.Web.Content.Portal.dll |
BB752359 | 1 |
| The addressee and salutation fields in the write a letter form for households now contain the household name. Previously, these fields were blank for households. You configure the household name using the Edit household screen, where you can choose to use the standard household name or a custom name. In addition, these fields now default to the available name format if only one name format is available for the constituent. For individuals where a primary addressee name format or primary salutation name format is defined, the fields now default to those values. Note that households do not support multiple name formats like individuals do. | 422771 | All assemblies |
BB716877 | 2 |
| Technical Change: Previously, when you replaced the ZIP Code Search with a custom search, the replacement search was not used in Constituent Batch, Constituent Address Update Batch, and other data forms. With this fix, the replacement search is correctly used in these batch types and forms. Custom searches should include the same parameters and output fields as the out-of-the-box search form, but you may hide those fields or add other fields. If you have replaced the ZIP Code Search or the ZIP/Postal Code Search, you should confirm that the parameters and output fields include the fields from the out-of-the-box search form. | 422769 | All assemblies |
BB750775 | 2 |
| New Feature: We have added a Blackbaud Data Warehouse reconciliation report to help you compare summary information about your transactional database and your Blackbaud Data Warehouse. You can access the new Reconciliation report tab on the Blackbaud Data Warehouse page. The report shows you the total number of items by category on your transactional database and on the data warehouse. Where the total counts match, you see a checkmark on the "Reconciled" column. Any exceptions are listed at the bottom of the report. | 421794 | All assemblies |
2 | |
| New Feature: We have added a new query source view. The query view "Revenue (from the Blackbaud Data Warehouse)" is similar to the existing "Revenue" query view, but shows results from the Blackbaud Data Warehouse. Queries from the data warehouse only include fields available in the warehouse, and they only show results as of the last time the ETL process was run. You can see when the data was last updated on the Preview results tab of the New Ad-hoc Query screen or the Edit Ad-hoc Query screen. You can also see the last updated date on the Results page when you run the query. | 421041 | All assemblies |
2 | |
| Previously, when editing a pledge with a zero dollar amount, an error displayed. With this fix, the error no longer displays upon edit. | 419593 | All assemblies |
BB747895 | 8 |
| This change applies to a pledge with multiple splits. Previously, when a designation was changed on a pledge and the next payment was made in a batch, the dropdown value for the Application field still reflected the previous designation. With this fix, the Application field dropdown displays the correct designation. | 414112 | All assemblies |
2 | |
| New Feature: When you create a contributions-based membership program, you determine which giving activity is counted toward the levels of the membership. The options for setting up the criteria are on the Contributions tab when you add a program and on the Rules tab when you edit a program. However, now you can get even more specific by using a Revenue Application selection or Installment Plan Payment selection instead of the predefined checkboxes and options. The criteria you use in the query will determine which giving activity is counted. When you upgrade, existing contributions-based membership programs continue to work the way they did before. However, you can edit the rules for the program to use a selection instead. | 412198 | All assemblies |
2 | |
| This fix addresses an issue with addresses in Constituent Update Batch. Previously, you were not able to save and commit addresses with multiple lines of information, such as an additional apartment or suite number; instead, the line breaks were removed and the address information was included on a single line for the constituent. New Constituent Update Batches will automatically take advantage of this fix. For existing uncommitted Constituent Update Batches, you will need to re-enter any addresses with multiple lines of information in order for the line breaks to be saved. | 404555 | All assemblies |
BB750668 | 8 |
| Technical Change: This fix addresses an issue which occurred when validating addresses in Constituent Batch, Constituent Update Batch, Constituent Address Update Batch, and Enhanced Revenue Batch, as well as any other custom batch types that use address validation. When addresses are validated, rows could receive a message indicating an address validation error. However, even after the address was corrected and re-validated, the message continued to appear. Address validation messages would disappear from both corrected and uncorrected rows after you saved the batch and when you ran standard batch validation. Now the row messages continue to appear for only uncorrected addresses. This fix required changes to all of the USP_<BATCHTABLENAME>BATCHSYSTEMMESSAGES_DELETEBYBATCHID procedures; one for each batch type affected. If you have customized any of these procedures, your changes will be overwritten and will need to be re-added after the fix is applied. Any customizations that simply call these procedures will continue to work as they did before. | 403543 | All assemblies |
8 | |
| This change applies to an Enhanced Revenue Batch and Revenue Update Batch. Previously, when a batch included an event registration payment with a charitable portion associated with the registration, the General Ledger mappings were not validated correctly and the following error displayed: "(ACCOUNT SYSTEM NAME)", account segments have not been defined for the segment 'Designation': Designation <not used>." This error displayed even when General Ledger setup was correct and a mapping existed for the designation. With this fix, the error no longer displays. | 401413 | All assemblies |
BB751606 | 2 |
| This change applies to recurring gifts in a Multicurrency environment. Previously, when editing the exchange rate for a recurring gift, the currency symbol did not update correctly for associated recognition credits. With this fix, we updated the stored procedure to ensure currency symbols update consistently during all steps of the edit process. | 400533 | All assemblies |
BB750615 | 2 |
| Previously, the membership contribution process would not upgrade a member to a higher level when set to renew. With this fix, the process now allows a member to renew and upgrade at the same time if they have given enough to qualify for a higher level. | 398639 | All assemblies |
BB749417 | 8 |
| Previously, from a funding request's pending step on the My Fundraising page, when a user clicked the Contact report link, an error displayed. With this fix, we disabled the Contact report link for funding requests with pending steps. The error no longer displays. | 397226 | All assemblies |
BB752235 | 2 |
| New Feature: You can now mark constituencies as inactive. Inactive constituencies are not available to assign to constituents and do not appear in queries and reports. They will also be considered inactive for the Data Warehouse and will not be included in the ETL refresh process. When you inactivate constituencies you no longer need, you improve system performance because processes such as queries do not need to consider data that is no longer relevant to your needs. To manage constituencies, from Constituents, click Constituencies under Configuration. To mark a constituency as inactive, select it and click Mark inactive. Active constituents show a checkmark on the Active column on the Constituencies page. To reactive an inactive constituency, expand it and click Mark active. | 393018 | All assemblies |
27 | |
| New Feature: The "Add user-defined constituency" and "Delete user-defined constituency" global changes update constituent records with the user-defined constituencies you specify. User-defined constituencies are set up under Code Tables in Administration. For example, if you have a user-defined constituency of "Neighbor," you could add it automatically to all constituents with a local postal code. The "Delete user-defined constituency" global change removes these constituencies when a constituent no longer meets the criteria you define. Now, when you run the global changes, the constituencies are updated as they are when you run the "Constituency stored-value refresh process" from Constituents. The global change processes automatically refresh the appropriate records in your database, so that the constituencies in the "Constituency (Stored Values)" node of a constituent query are updated. | 392513 | All assemblies |
27 | |
| New Feature: We have made some design changes to the way you manage constituency criteria in the Constituencies page. Previously, you managed this information from the "Donor constituency criteria" section of the page. Now, you manage criteria directly from the constituencies themselves. For constituencies that allow criteria settings, which include Donor, Loyal donor, and Major donor, you can now expand the constituency and click "Edit constituency criteria." This new option displays an edit screen for that constituency only. Since you can now mark a constituency as inactive from the constituency itself, this is also where you manage the donor criteria specific to that constituency, when applicable. To determine whether to include recognition credits in constituency definition calculations, you still click Edit on this page. The new "Edit donor constituency criteria" screen appears. To manage constituencies criteria, from Constituents, click Constituencies under Configuration. | 389138 | All assemblies |
27 | |
| This change applies to a revenue batch created through an import process. Previously, when a user changed the applied amount from a matching gift to a recurring gift on the Apply to Commitments screen in a batch, an error displayed upon saving the batch. With this fix, we made code changes to ensure the error no longer displays upon save. | 383630 | All assemblies |
BB745616 | 2 |
| This fix addresses an issue with the constituency of "Student." Previously, when a constituent was an active student at more than one institution, the "Student" constituency appeared twice on the Personal Info tab. With this fix, the constituency appears only one time. The constituent's education-related information for all institutions still appears on the Education tab. | 382855 | All assemblies |
BB748470 | 8 |
| New Feature: Previously, AddressFinder update options did not allow you to only update addresses that had been changed by the AddressFinder process, so you had to either update only forwardable addresses or all addresses. With this change, we have added a new button in the AddressFinder update options called "Update only NCOA changes" which allows you to only update addresses that were changed by the process. | 382847 | All assemblies |
BB740602 | 2 |
| This fix addresses a problem with forwarding addresses in AddressFinder files. Previously, when you received an AddressFinder file that included new addresses, users were given the option to mark new forwardable move addresses as 'Do not mail' even though these addresses were valid. With this fix, the program no longer allows you to mark an address as 'Do not mail' and use as the reason that there is a new forwardable address. | 382839 | All assemblies |
BB740600 | 2 |
| Technical Change: This fix addresses an issue with congressional district information returned as part of the Address Validation service. Previously, for states with a single, at-large congressional district (as opposed to states with 1st congressional district, 2nd, and so on), the Address Validation service was not returning any information for the congressional district. States with a single, at-large district are Alaska, Delaware, Montana, North Dakota, South Dakota, Vermont, and Wyoming. Now, the validated address will have a congressional district value of "AK's at-large" for Alaska at-large or "DE's at-large" for Delaware at-large, for example. This issue occurred when validating addresses manually when adding or editing an address, as well as when you submitted data as part of the Address Validation service from the Data Tune-up page in Administration. To take advantage of this fix, you will need to re-validate addresses in those states in order to get the new values. After you upgrade, you should compare ad-hoc query results as well as any custom processes that rely on the congressional district information for the affected states. | 382831 | Blackbaud.AppFx.AddressValidation.Server.dll Blackbaud.AppFx.AddressValidation.Service.exe |
19 | |
| Previously, when you used address validation in a batch, the addresses could sometimes fail to validate. This happened when an address you were validating had an extra line break at the end. This returned the validation error 'Street name invalid,' even when the address was actually valid. In order to take advantage of this fix, you must redeploy the ClickOnce utility for the address validation service. | 382811 | All assemblies |
BB529862 | 2 |
| Previously, in an Enhanced Revenue Batch, "GL post date" was a required field by default. When the field was left blank, the exception message "Required field missing: GL post date" appeared during validation. With this fix, "GL post date" is no longer required by default, and the batch successfully validates when the field is blank. | 375250 | Blackbaud.AppFx.Fundraising.UIModel.dll |
90793 | 19 |
| This fix addresses an issue with the constituent merge process for constituents with declined constituent recognition levels. Now, the source constituent's declined levels will be transferred to the target constituent's record. If either constituent is a member of a recognition level that the other has declined, the constituents will not be merged and this will be called out as a merge exception. | 375235 | All assemblies |
BB746246 | 2 |
| New Feature: In constituent queries, we have added the "Educational institution record" field under Constituents > Education History > Educational Institution. Previously, you could use only the "Name" field under Constituents > Education History > Educational Institution, which relied on you entering the exact name of the institution, rather than searching for and selecting one. This resulted in potentially inaccurate or unintended results in the query in addition to potential performance issues. Now, when you include the new "Educational institution record" field in a query, you can search for and select the exact educational institution to use. Existing queries will remain unchanged when you upgrade; however, you may consider whether or not to modify them to use the new "Educational institution record" field for more accurate results and better performance. | 363327 | All assemblies |
BB749798 | 27 |
| New Feature: With this release, we replaced the previous "Recurring gift settings" configuration option with the new "Recurring gift payment handling" configuration option. With the new option, you can specify how the program handles payments when more than one past installment has a balance, payments you receive that overpay or underpay installment balances, as well as balances still present on past installments after applying a payment. Several areas of the program are affected including Revenue configuration, the Add and Edit a payment screen, the Activity timeline on a recurring gift record, Batch, and Query. | 353012 | All assemblies |
8 | |
| With this fix, applying a payment towards a $0 recurring gift now results in an error on commit instead of allowing the batch commit to run indefinitely. | 352018 | Blackbaud.AppFx.Fundraising.Catalog.dll Blackbaud.AppFx.Galileo.ServiceRevisions.dll Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll |
12 | |
| New Features: When you use the Advanced Donation Form to create a custom donation web page, Blackbaud Internet Solutions now includes API end points for pledge installments. For information about the API, refer to the Developer Guide at http://developer.blackbaud.com/bbis/. | 338541 | All assemblies |
21 |
| Assembly | Patch |
|---|---|
| BBDW.ReportDB.Catalog.dll | 4.0.157.29 |
| BBDW.ServiceRevisions.dll | 4.0.141.19 |
| BBDWETL - SSIS Reporting Package | 4.0.141.19 |
| BBISModeler.exe | 4.0.163.34 |
| BBNCImport.exe | 4.0.163.34 |
| BBNCServiceExtensions.dll | 4.0.163.34 |
| BBNCTransactionClient.dll | 4.0.163.34 |
| BBUIModelLibrary.dll | 4.0.5.12 |
| Blackbaud.AppFx.Accounting.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.Address.UIModel.dll | 4.0.157.29 |
| Blackbaud.AppFx.AddressManagement.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.AddressValidation.Server.dll | 4.0.5.19 |
| Blackbaud.AppFx.AddressValidation.Service.exe | 4.0.141.19 |
| Blackbaud.AppFx.Advocacy.Catalog.dll | 4.0.163.34 |
| Blackbaud.AppFx.Advocacy.dll | 4.0.163.34 |
| Blackbaud.AppFx.Advocacy.Reports.ClientComponents.dll | 4.0.141.19 |
| Blackbaud.AppFx.Advocacy.Test.dll | 4.0.163.34 |
| Blackbaud.AppFx.Advocacy.UIModel.dll | 4.0.163.34 |
| Blackbaud.AppFx.ApexForm.Catalog.dll | 4.0.163.34 |
| Blackbaud.AppFx.ApexForm.Model.dll | 4.0.163.34 |
| Blackbaud.AppFx.ApexForm.Web.dll | 4.0.163.34 |
| Blackbaud.AppFx.Auction.Catalog.dll | 4.0.141.12 |
| Blackbaud.AppFx.BatchUI.dll | 4.0.5.12 |
| Blackbaud.AppFx.BBDW.Query.Catalog.dll | 4.0.141.12 |
| Blackbaud.AppFx.BBNC.Catalog.dll | 4.0.163.34 |
| Blackbaud.AppFx.BBNC.ClientComponents.dll | 4.0.141.19 |
| Blackbaud.AppFx.BBNC.SPWrapBBNC.dll | 4.0.163.34 |
| Blackbaud.AppFx.BBNCSvc.dll | 4.0.157.28 |
| Blackbaud.AppFx.BBNCSvc.UIModel.dll | 4.0.141.19 |
| Blackbaud.AppFx.BBPay.ServiceProxy.dll | 2.96.134.0 |
| Blackbaud.AppFx.Browser.exe | 4.0.5.19 |
| Blackbaud.AppFx.Browser.ImageLibrary.dll | 4.0.5.19 |
| Blackbaud.AppFx.Campaign.Catalog.dll | 4.0.141.12 |
| Blackbaud.AppFx.CMS.FCL.GiftEditor.dll | 4.0.163.34 |
| Blackbaud.AppFx.CMS.FCL.ShoppingCart.BaseClassLibrary.dll | 4.0.141.19 |
| Blackbaud.AppFx.CommPrefs.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.Communications.UIModel.dll | 4.0.141.19 |
| Blackbaud.AppFx.Constituent.Catalog.dll | 4.0.157.29 |
| Blackbaud.AppFx.Constituent.Catalog.V1_1.dll | 4.0.141.12 |
| Blackbaud.AppFx.Constituent.Common.UIModel.dll | 4.0.141.19 |
| Blackbaud.AppFx.Constituent.SpWrapConstituent.dll | 4.0.155.25 |
| Blackbaud.AppFx.Constituent.UIModel.dll | 4.0.141.19 |
| Blackbaud.AppFx.ConstituentGroups.Catalog.dll | 4.0.141.12 |
| Blackbaud.AppFx.ConstituentGroups.UIModel.dll | 4.0.141.19 |
| Blackbaud.AppFx.ContentManagement.Catalog.dll | 4.0.163.34 |
| Blackbaud.AppFx.ContentManagement.LanguageProvider.dll | 4.0.163.34 |
| Blackbaud.AppFx.ContentManagement.MicrositeParts.dll | 4.0.163.34 |
| Blackbaud.AppFx.ContentManagement.Parts.DonationForm.dll | 4.0.141.12 |
| Blackbaud.AppFx.ContentManagement.Parts.EventRegistrationExpress.UI.dll | 4.0.163.34 |
| Blackbaud.AppFx.ContentManagement.Parts.MembershipExpress.UI.dll | 4.0.163.34 |
| Blackbaud.AppFx.ContentManagement.Parts.PrintAtHome.ETickets.Data.dll | 4.0.163.34 |
| Blackbaud.AppFx.ContentManagement.Parts.PrintAtHome.ETickets.UI.dll | 4.0.163.34 |
| Blackbaud.AppFx.ContentManagement.Parts.ShoppingCart.UI.dll | 4.0.163.34 |
| Blackbaud.AppFx.ContentManagement.Parts.WebFormsUserRegistration.Data.dll | 4.0.163.34 |
| Blackbaud.AppFx.ContentManagement.Parts.WebFormsUserRegistration.UI.dll | 4.0.163.34 |
| Blackbaud.AppFx.ContentManagement.Platform.Core.dll | 4.0.141.19 |
| Blackbaud.AppFx.ContentManagement.Platform.Email.Catalog.dll | 4.0.141.12 |
| Blackbaud.AppFx.DbMaintenance.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.Deployment.exe | 4.0.5.19 |
| Blackbaud.AppFx.Education.Catalog.dll | 4.0.141.12 |
| Blackbaud.AppFx.Education.WebEE7.CMS.dll | 4.0.163.34 |
| Blackbaud.AppFx.EventManagement.Catalog.dll | 4.0.141.12 |
| Blackbaud.AppFx.FAFEvent.AdminWeb.dll | 4.0.163.34 |
| Blackbaud.AppFx.FAFEvent.Catalog.dll | 4.0.163.34 |
| Blackbaud.AppFx.FAFEvent.UIModel.dll | 4.0.163.34 |
| Blackbaud.AppFx.FAFEvent.Web.dll | 4.0.163.34 |
| Blackbaud.AppFx.Fundraising.Catalog.dll | 4.0.163.33 |
| Blackbaud.AppFx.Fundraising.UIModel.dll | 4.0.141.26 |
| Blackbaud.AppFx.Galileo.ServiceRevisions.dll | 4.0.163.33 |
| Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1480.dll | 4.0.141.10 |
| Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1490.dll | 4.0.141.20 |
| Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1500.dll | 4.0.155.25 |
| Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1510.dll | 4.0.157.29 |
| Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1530.dll | 4.0.158.31 |
| Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1540.dll | 4.0.163.33 |
| Blackbaud.AppFx.GiftAid.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.GiftAid.UIModel.dll | 4.0.141.19 |
| Blackbaud.AppFx.HtmlProcessor.dll | 4.0.5.12 |
| Blackbaud.AppFx.MajorGiving.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.MajorGiving.UIModel.dll | 4.0.141.12 |
| Blackbaud.AppFx.Marketing.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.Marketing.Communications.Catalog.dll | 4.0.157.29 |
| Blackbaud.AppFx.Marketing.NetCommunityIntegrationCatalog.dll | 4.0.163.34 |
| Blackbaud.AppFx.Marketing.UIModel.dll | 4.0.141.19 |
| Blackbaud.AppFx.Membership.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.Membership.UIModel.dll | 4.0.141.19 |
| Blackbaud.AppFx.PeopleFinder.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.PeopleFinder.UIModel.dll | 4.0.141.19 |
| Blackbaud.AppFx.Platform.Catalog.dll | 4.0.158.31 |
| Blackbaud.AppFx.Platform.DataForm.Catalog.dll | 4.0.5.12 |
| Blackbaud.AppFx.Platform.Export.dll | 4.0.5.19 |
| Blackbaud.AppFx.Platform.ServiceRevisions.dll | 4.0.160.34 |
| Blackbaud.AppFx.Platform.ServiceRevisions.Specs1490.dll | 4.0.5.19 |
| Blackbaud.AppFx.Platform.ServiceRevisions.Specs1530.dll | 4.0.158.31 |
| Blackbaud.AppFx.Platform.ServiceRevisions.Specs1540.dll | 4.0.160.33 |
| Blackbaud.AppFx.Platform.SqlClr.dll | 4.0.5.19 |
| Blackbaud.AppFx.Platform.UIModel.dll | 4.0.5.19 |
| Blackbaud.AppFx.Platform.WebDashboardParts.dll | 4.0.5.12 |
| Blackbaud.AppFx.Programming.Catalog.dll | 4.0.141.12 |
| Blackbaud.AppFx.Programming.ContentManagement.dll | 4.0.163.34 |
| Blackbaud.AppFx.Programming.SPWrapProgramming.dll | 4.0.141.12 |
| Blackbaud.AppFx.ProspectResearch.Catalog.dll | 4.0.141.12 |
| Blackbaud.AppFx.ReportDB.BuildTasks.dll | 4.0.5.19 |
| Blackbaud.AppFx.ReportDB.Config.dll | 4.0.5.19 |
| Blackbaud.AppFx.ReportDB.Installer.exe | 4.0.5.19 |
| Blackbaud.AppFx.Reports.Deploy.exe | 4.0.5.19 |
| Blackbaud.AppFx.RoleSync.exe | 4.0.5.12 |
| Blackbaud.AppFx.Security.Catalog.dll | 4.0.160.33 |
| Blackbaud.AppFx.Security.ClientComponents.dll | 4.0.5.12 |
| Blackbaud.AppFx.Security.UIModel.dll | 4.0.5.12 |
| Blackbaud.AppFx.Server.dll | 4.0.160.34 |
| Blackbaud.AppFx.Sponsorship.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.Sponsorship.ContentManagement.dll | 4.0.163.34 |
| Blackbaud.AppFx.SpWrap.dll | 4.0.160.33 |
| Blackbaud.AppFx.SqlClr.SpWrap.dll | 4.0.5.19 |
| Blackbaud.AppFx.Stewardship.UIModel.dll | 4.0.141.12 |
| Blackbaud.AppFx.TextFileParser.dll | 4.0.5.9 |
| Blackbaud.AppFx.Treasury.Catalog.dll | 4.0.141.19 |
| Blackbaud.AppFx.Treasury.UIModel.dll | 4.0.141.19 |
| Blackbaud.AppFx.UIModeling.Core.dll | 4.0.5.12 |
| Blackbaud.AppFx.UIModeling.RestClient.dll | 4.0.5.19 |
| Blackbaud.AppFx.UIModeling.RestServices.dll | 4.0.160.33 |
| Blackbaud.AppFx.UnitTesting.dll | 4.0.5.19 |
| Blackbaud.AppFx.WebDashboard.dll | 4.0.5.12 |
| Blackbaud.AppFx.WebOlap.dll | 4.0.153.22 |
| Blackbaud.AppFx.WebShell.WebUI.dll | 4.0.160.33 |
| Blackbaud.AppFx.XmlTypes.dll | 4.0.5.19 |
| Blackbaud.CRM.Financial.Contracts.dll | 1.0.0.0 |
| Blackbaud.CRM.Financial.Domain.dll | 1.0.0.0 |
| Blackbaud.Installer.dll | 4.0.163.34 |
| Blackbaud.Installer.Extractor.exe | 4.0.163.34 |
| Blackbaud.Installer.SFX.exe | 4.0.163.34 |
| Blackbaud.Installer.SFX.FourZero.exe | 4.0.163.34 |
| Blackbaud.Installer.UI.Common.dll | 4.0.163.34 |
| Blackbaud.NetCommunity.EA7Controls.dll | 4.0.163.34 |
| Blackbaud.NetCommunity.EA7Core.dll | 4.0.163.34 |
| Blackbaud.NetCommunity.EA7DataSources.dll | 4.0.163.34 |
| Blackbaud.NetCommunity.EA7Parts.dll | 4.0.163.34 |
| Blackbaud.NetCommunity.EA7Revisions.exe | 4.0.163.34 |
| Blackbaud.NetCommunity.EA7Service.dll | 4.0.163.34 |
| Blackbaud.NetCommunity.EA7SPWrap.dll | 4.0.163.34 |
| Blackbaud.NetCommunity.EEShelbyPlugin.ProfileUpdate.dll | 4.0.163.34 |
| Blackbaud.NetCommunity.Web.CacheHandlers.dll | 4.0.163.34 |
| Blackbaud.RE7Service.dll | 4.0.163.34 |
| Blackbaud.RE7XData.dll | 4.0.163.34 |
| Blackbaud.Web.Content.BuildTasks.Common.dll | 4.0.163.34 |
| Blackbaud.Web.Content.BuildTasks.dll | 4.0.163.34 |
| Blackbaud.Web.Content.Common.dll | 4.0.163.34 |
| Blackbaud.Web.Content.Core.dll | 4.0.163.34 |
| Blackbaud.Web.Content.PluginService.dll | 4.0.163.34 |
| Blackbaud.Web.Content.Portal.dll | 4.0.163.34 |
| Blackbaud.Web.Content.Revisions.exe | 4.0.163.34 |
| Blackbaud.Web.Content.ScorpioCore.dll | 4.0.163.34 |
| Blackbaud.Web.Utils.NetCommunity.UserImport.Library.dll | 4.0.163.34 |
| Blackbaud.Web.Utils.NetCommunity.UserImport.Service.dll | 4.0.163.34 |
| CreateDB.exe | 4.0.5.19 |
| CustomForm.Common.dll | 4.0.163.34 |
| CustomForm.EducationEdgeImporter.dll | 4.0.163.34 |
| CustomForm.EducationEdgeImporter.Plugin.dll | 4.0.163.34 |
| CustomForm.EducationEdgeImporter.Revisions.dll | 4.0.163.34 |
| CustomForm.EE.Admissions.ExporterContext.dll | 4.0.163.34 |
| EEShelbyPlugin.dll | 4.0.163.34 |
| EEUserImport.dll | 4.0.163.34 |
| NCUserImporter.exe | 4.0.163.34 |
| OnlineExpressPlugin.dll | 4.0.163.34 |
| PostSBMergeSync.exe | 4.0.163.34 |
| RE7ShelbyPlugin.dll | 4.0.163.34 |
| SettingsEditor.exe | 4.0.163.34 |
| Setup.exe | 4.0.163.34 |
| Setup.exe | 4.0.163.34 |
| Setup.exe | 4.0.163.34 |
| Setup.exe | 4.0.163.34 |