CRM 4.0 Service Pack 2 Release Notes

This service pack is cumulative. It includes all issues addressed in CRM 4.0 prior to Service Pack 2, 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.

New Features in CRM 4.0 Service Pack 2

For information about all of the new features released in CRM 4.0, see the CRM 4.0 New Features page. For information about new features from CRM 4.0 Service Packs, see the Service Pack New Features chapter in the CRM 4.0 New Features Guide.

Note: For Service Packs 1 and 2 for CRM 4.0, all of the assemblies are rebuilt and have a new date stamp; therefore the Release Notes will not contain information about specific affected assemblies. After Service Pack 2, these Release Notes will contain information about the affected assemblies, as usual.

Note: The version number for this release changed from 4.0.138.2 to 4.0.141.0. The change in version number is attributed to a security-related change with Blackbaud Internet Solutions. Refer to item number 464759 below for additional information.

Database Growth Management (393165)

We have added a new database analysis tool that allows you to view the size of your database and the space taken by different data types. The Database Growth Management page provides insight and tools related to business process history, audit tables, application data, selection data, and customization data.

To access the new Database Growth Management page, from Administration, click Database growth management under Administration. Use the tabs to navigate detailed information about each data type in your database.

In the Summary tab, you can see the overall size of your database and the distribution of data by type and how data size has changed over time. Here, you can also see when the information was last updated and refresh it manually.
In the Business Process History tab you see the amount of data originated by business processes. When you run a business process such as an export in Blackbaud CRM, the program stores a copy of the output. To regularly delete these outputs when you no longer need them, you can use the Business process output delete global change. Blackbaud CRM also keeps copies of batch output, which you can delete using the Batch report delete global change.
The Audit Tables tab shows the amount of data used by audit tables. Audit tables keep details of changes made to the database by different users. You can use the Delete audit data global change to delete old audit table information you no longer want to keep.
The Application Data tab itemizes the data that makes up your actual database, including records, attributes you created, data related to marketing efforts, and smart field calculations.
In the Selection Data tab, you see the data taken up by selections, whether created by users, imported into the database, or generic selections that were created by other elements of the system.
In the Customization Data tab, you can see information about custom tables you created using the Blackbaud CRM SDK.
In the Other Data tab, you see the total amount of data that does not fall into any of the previous categories. This is usually blank, but can show data from tables you created outside of the Blackbaud CRM SDK.

The data included in this tool is updated daily and the last refresh time is posted on the Summary tab. To refresh the data outside of the automatic refresh process, click Refresh now on the Summary tab. The program indicates an estimated time required for the refresh to let you decide if you want to wait or refresh at another time.

As part of this work, we have also added a new option to the "Business process output delete" global change. You can now choose whether you want to delete all output older than a certain timeframe or all output except a certain number of the most recent runs. Previously, you could only use the first option.

To use the new option, on the Add global change screen for the "Business process output delete" global change, click Delete output tables for all but the most recent and enter the number of runs you want to save.

Note: Deleting business process output does not affect your ability to view business process history. You can still see the full history of business processes even when the output for those processes has been deleted.

To access global changes, from Administration, click Global changes under Data.

To learn more about the new Database Growth Management tool, see the new Database Growth Management Guide.

Pledge Installment Improvements (464595)

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:

The value in the Installment amount field consistently reflects the most recent amount entered.
The values in the Installment amount, No. installments, and No. installments remaining fields are accurately calculated in the pledge installment grid.
The No. installments and No. installments remaining fields represent the number of installments that are not fully paid.
When you edit installment designations and enter different installment values, the value in the Installment amount field consistently represents the earliest installment amount that is not fully paid.

Tip: While the No. installments and No. installments remaining fields are labeled differently, both fields behave the same way throughout the program. For example, the No. installments field displays on the Add a pledge screen and represents the number of installments for a new pledge. The No. installments remaining field displays on the Edit pledge screen and represents the number of remaining installments for an existing pledge.

Recurring Gift Payment Handling (353012)

With this release, on the Revenue page, we replaced the Recurring gift settings configuration option with the new Recurring gift payment handling option.

Previously, the Recurring gift settings configuration option existed and offered two choices: "Update installment amounts to match payments" and "Maintain installment amounts." With this release, the Recurring gift payment handling configuration option replaces the Recurring gift settings configuration option and offers much more flexibility when applying payments.

Click Recurring gift payment handling to access the Recurring gift payment handling screen.

With these new configuration options, 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.

Note: Note that installments with today's date are included as "past installments" for the purposes of payment handling.

Add and Edit a Recurring Gift Payment (353012)

To ensure consistency across the product with the new payment handling options, we made several changes to the Add a payment and Edit a payment screens.

When applying an amount to a recurring gift, on the Amount to apply screen, the Next transaction amount option now displays as Next installment balance. The Past due amount option now displays as Past installment balance.
From the Amount to apply screen, note that Past installment balance is calculated based on the installment date. The calculation includes an installment balance that is due today or in the past. Previously, in version 4.0, this option was based on the installment status.
Based on payment handling configuration options, donations created from overpaying an installment are automatically added in the application grid. A new donation is also created if you increase the amount in the Applied field.

Tip: Donations created from payment handling configuration options also affect recurring gift payments added through Enhanced Revenue Batch and Revenue Update Batch.

When you edit a recurring gift payment, it is important to note the following behavior:

When you edit a recurring gift payment, the payment handling configuration options that existed when you initially added the payment will apply to future edits of the payment. Note that if you added a payment prior to version 4.0, the options in place prior to the upgrade will apply to all future edits of the payment.
Payment handling configuration options consider future and past installments in terms of the recurring gift payment date, not the date the recurring gift is edited.

Consider the following scenario as an example:

On 02/05/2015 -

A recurring gift has two installments due on 01/01/2015 and 02/01/2015 for $5 each.
The payment handling options are set to apply the payment to any past installments with a balance, and create a donation for any excess after that.
A payment of $10 is applied to the recurring gift which pays the installments for 01/01/2015 and 02/01/2015.

On 03/05/2015 -

An installment is now due on 03/01/2015 for $5.
The payment that was added on 02/05/2015 is increased to apply $15 to the recurring gift.
The additional $5 will be split off as a donation. The 03/01/2015 installment is treated as a future installment during this edit because it was considered a future installment at the time the payment was originally added.

Recurring Gift Activity Timeline (353012)

On a recurring gift record, the Details column of the Activity timeline now displays payment handling adjustment details for installments.

For example, when an installment is underpaid, and the payment handling option is set to apply the payment and automatically write-off the remaining installment balance, "Recurring gift payment handling" displays in the Details column.

Warning: When a recurring gift payment is deleted, all associated write-offs and adjustments are deleted as well.

Next Installment Date Calculation (353012)

When you specify recurring gift payment handling configuration options, you can select to either apply a payment to the oldest or most recent installment with a balance.

Based on your selection, the program calculates whether to apply payments to the oldest or most recent installment. Once this is calculated, the "next" installment to be paid is defined and reflected in the following areas of the program:

Recurring gift transaction summary section
Amount and date due on the Add a payment and Edit a payment screens
Amount and date due in Enhanced Revenue Batch and Revenue Update Batch
Installments associated with credit card and direct debit events, such as credit card processing and automatically generating payments
Recurring gift next transaction date in Query
Pledge reminders

Existing Recurring Gift Settings (353012)

When you upgrade to version 4.0 Service Pack 2, you must decide how you want the program to handle payments toward recurring gift installments. The following details explain how the previous option relates to the new payment handling option.

Update Installment Amounts to Match Payments

In the previous version, when you selected "Update installment amounts to match payments," the installment balance that was due increased to match the payment received. No underpaid installment balance or future installment was affected by the overpayment.

To ensure the equivalent behavior is applied to payments using the new Recurring gift payment handling option, select the following options on the Recurring gift payment handling screen:

To handle payments when more than one past installment has a balance, select Apply the payment to the oldest installment with a balance.
To handle payments that overpay the installment balance, select Do not apply the excess amount to other past installments with a balance and then Increase the installment amount to include excess payment amount (other installment amounts are unaffected).
To handle payments that underpay the installment balance, select Decrease the installment amount to match the payment amount (other installment amounts are unaffected).
To handle remaining past installment balances after fulling applying a payment, select Leave any balances.

Maintain Installment Amounts

In the previous version, when you selected "Maintain installment amounts," the payment was applied toward the installment balances that were due and any overpayment amount was applied toward a later installment.

To ensure the equivalent behavior is applied to payments using the new Recurring gift payment handling option, select the following options on the Recurring gift payment handling screen:

To handle payments when more than one past installment has a balance, select Apply the payment to the oldest installment with a balance.
To handle payments that overpay the installment balance, select First, apply the excess amount to any other past installments with a balance (from oldest to most recent) and then Apply any remaining excess to future installments.
To handle payments that underpay the past installment balance, select Apply the payment and leave a balance for the installment.
To handle remaining past installment balances after fulling applying a payment, select Leave any balances.

Opportunities Tile on Constituent Records (474696)

The constituent record now includes the Opportunities tile, which summarizes opportunity information for individual 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.

To add opportunities from the Opportunities tile, click Add. To edit opportunity information, click Edit next to the plan, primary manager, or the amount of the opportunity. If a constituent has more than one opportunity, you can use the arrows on the Opportunity tile to view each opportunity.

The amount that appears in the tile depends on the status of the opportunity. For example, if the opportunity status is qualified, response pending, rejected, or canceled, the tile displays the ask amount. If the opportunity is unqualified, the tile displays the expected ask amount. If the opportunity is accepted, the tile displays the accepted amount.

To open the related record, click the name of the plan, the name of the primary manager, or the opportunity amount.

To open the Opportunities tab of the plan the Opportunities tile is displaying, click the tile name.

Expand and Collapse Query Folders (439874)

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.

On the Query tab of the Information Library, you can now click Expand all and Collapse all to easily view your folders and subfolders.

When you collapse all, only first-level folders are displayed. When you expand all, you see all your query folders and subfolders.

To access your queries, from Analysis, click Information library.

Customize KPI Dashboard (439875)

You can now customize your KPI dashboard. From the dashboard, click Customize dashboard under Tasks.

The new Customize a KPI dashboard screen appears. You can create pages and tabs within pages to organize your KPIs. To add pages or tabs, click the plus sign next to the Page or Tab fields. You can edit existing pages and tab names by clicking the pencil icon, or delete them by clicking the red X icon.

You can also reorganize tabs within a page. To do this, click the engine icon next to the Tab field. On the Reorder KPI Dashboard tabs screen, use the up and down arrows to rearrange tabs and click OK to save the new order.

Once you have created pages and tabs, to assign KPIs to them, select the KPI and click the right arrow to add it, or the left arrow to remove it from a page or a tab.

To access your KPI dashboard, from Analysis, click KPI dashboard.

Performance Improvements for Group WealthPoint Screenings (490167)

To improve the performance when users screen a group of constituents through WealthPoint, Target Analytics is making the following updates.

Going forward, we will focus on returning the key relationships from GuideStar on a group screening:

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

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.

Event Invitation Lists (441286)

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."

Blackbaud Internet Solutions Security Update (464759)

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.

Help Text in Email Messages (438925)

New help text is available for the Send after date field in Messages to explain that after you click Send final, the website does not process the email until the date and time you enter in the field. It also explains that if you delete the email before that date, the program does not process it and does not send it to recipients.

Pages: Additional Copy Part Option (468620)

You can now copy parts from the Page content tab when you highlight a page in the list of pages. This change reduces the number of clicks required to copy parts when you navigate to them from the list of pages. Previously, you had to edit the pages to copy them or copy them from Parts.

Part Search Filters (471249)

To help you quickly find the pages and parts you need, new search filters are available. From the Search tab, you can use the new My content or Filter by template options to narrow the results to pages you created or that use a specific template.

Also, when you search for parts to insert on pages, the My content filter is available so you can limit the list to the parts you created.

Pages and Templates New Sort Options (472909)

You can now use Page name or the new Last modified column to sort the list of pages. These changes help you to quickly find the pages you need.

Note: When you sort the list, the pages appear in ascending order. Pages that begin with the letter A, or include the oldest changes, appear at the top of the list.

Parts Search Filter (471249)

To help you quickly find the parts you need, a new search filter is available. From the Search tab, you can use the new My content option to narrow the results to parts that you created.

Profile Update Form (484998)

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. In the Privacy caption row, you can enter custom text for the checkbox to display on the page.

Note: When users select the new Make my primary email address private 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.

reCAPTCHA Instructional Text (425615)

New instructional text appears on forms that include reCAPTCHA images. Previously, the text instructed users to "type the two words" shown in the reCAPTCHA image. Now, the text instructs them to "enter the text" since the images typically include characters that do not form words.

Site Administrators Filter for Users (468624)

Now when you use filters in Users, you can identify the people who are site administrators. Previously, you could only filter by the roles you added to your website. This change helps you quickly identify people with administrative access when you need to change rights, such as when a person is no longer employed by your organization.

Issues addressed in Service Pack 2

Issues addressed in Service Pack 2
Comment	Work Item	Location	Knowledgebase
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
This change applies to an environment with a blank database and a new CRM 4.0 installation. Previously, some platform files necessary for viewing legacy help topics were not deployed due to the separation of platform code and Infinity code bases. With this fix, we added platform build dependencies to the backend assemblies to ensure necessary files are deployed during installation.	477109	All assemblies	BB755302
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
To improve performance for Blackbaud Internet Solutions, the index IX_TEAMFUNDRAISINGTEAMCAPTAIN_CONSTITUENTID has been added.	467387	All assemblies
Previously, revenue deleted via an adjustment appeared in search results. With this fix, deleted revenue is no longer returned.	467237	All assemblies	BB753465
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
With this change, we modified SQL function to ensure the correct set of tables are used during validation.	466753	All assemblies
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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

Assemblies affected in Service Pack 2

Assemblies affected in Service Pack 2
Assembly	Patch
All assemblies	4.0.141.0

SHA-1 Hash for Service Pack 2

SHA-1 hash for Service Pack 2
Installer filename	SHA-1 Hash
BlackbaudInstaller.exe	B0A8D7E0F0F8E03F0037573ECA9F443B3F41E6E9

Issues addressed in CRM 4.0 prior to Service Pack 2

Issues addressed in CRM 4.0 prior to Service Pack 2
Comment	Work Item	Location	Knowledgebase	Patch
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
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 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
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
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
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
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
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
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
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
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 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
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
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 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
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 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 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
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
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 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
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
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 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
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
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
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
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
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
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
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 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
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 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
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 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
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 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, 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
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
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
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
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

Assembly	Patch
BBISModeler.exe	4.0.131.1
BBNCImport.exe	4.0.131.1
BBNCServiceExtensions.dll	4.0.131.1
BBNCTransactionClient.dll	4.0.131.1
Blackbaud.AppFx.Advocacy.Catalog.dll	4.0.131.1
Blackbaud.AppFx.Advocacy.dll	4.0.131.1
Blackbaud.AppFx.Advocacy.Reports.ClientComponents.dll	4.0.131.1
Blackbaud.AppFx.Advocacy.Test.dll	4.0.131.1
Blackbaud.AppFx.Advocacy.UIModel.dll	4.0.131.1
Blackbaud.AppFx.ApexForm.Catalog.dll	4.0.131.1
Blackbaud.AppFx.ApexForm.Model.dll	4.0.131.1
Blackbaud.AppFx.ApexForm.Web.dll	4.0.131.1
Blackbaud.AppFx.BBNC.Catalog.dll	4.0.131.1
Blackbaud.AppFx.BBNC.ClientComponents.dll	4.0.131.1
Blackbaud.AppFx.BBNC.SPWrapBBNC.dll	4.0.131.1
Blackbaud.AppFx.CMS.FCL.GiftEditor.dll	4.0.131.1
Blackbaud.AppFx.ContentManagement.Catalog.dll	4.0.131.1
Blackbaud.AppFx.ContentManagement.LanguageProvider.dll	4.0.131.1
Blackbaud.AppFx.ContentManagement.MicrositeParts.dll	4.0.131.1
Blackbaud.AppFx.ContentManagement.Parts.EventRegistrationExpress.UI.dll	4.0.131.1
Blackbaud.AppFx.ContentManagement.Parts.MembershipExpress.UI.dll	4.0.131.1
Blackbaud.AppFx.ContentManagement.Parts.PrintAtHome.ETickets.Data.dll	4.0.131.1
Blackbaud.AppFx.ContentManagement.Parts.PrintAtHome.ETickets.UI.dll	4.0.131.1
Blackbaud.AppFx.ContentManagement.Parts.ShoppingCart.UI.dll	4.0.131.1
Blackbaud.AppFx.ContentManagement.Parts.WebFormsUserRegistration.Data.dll	4.0.131.1
Blackbaud.AppFx.ContentManagement.Parts.WebFormsUserRegistration.UI.dll	4.0.131.1
Blackbaud.AppFx.Education.WebEE7.CMS.dll	4.0.131.1
Blackbaud.AppFx.FAFEvent.AdminWeb.dll	4.0.131.1
Blackbaud.AppFx.FAFEvent.Catalog.dll	4.0.131.1
Blackbaud.AppFx.FAFEvent.UIModel.dll	4.0.131.1
Blackbaud.AppFx.FAFEvent.Web.dll	4.0.131.1
Blackbaud.AppFx.Galileo.ServiceRevisions.dll	4.0.138.4
Blackbaud.AppFx.Galileo.ServiceRevisions.Specs1480.dll	4.0.138.4
Blackbaud.AppFx.Marketing.NetCommunityIntegrationCatalog.dll	4.0.131.1
Blackbaud.AppFx.Membership.Catalog.dll	4.0.138.4
Blackbaud.AppFx.Platform.ServiceRevisions.dll	4.0.2.1
Blackbaud.AppFx.Platform.UIModel.dll	4.0.2.1
Blackbaud.AppFx.Programming.ContentManagement.dll	4.0.131.1
Blackbaud.AppFx.Server.dll	4.0.4.7
Blackbaud.AppFx.Sponsorship.ContentManagement.dll	4.0.131.1
Blackbaud.AppFx.WebShell.WebUI.dll	4.0.2.1
Blackbaud.Installer.dll	4.0.131.1
Blackbaud.Installer.Extractor.exe	4.0.131.1
Blackbaud.Installer.SFX.exe	4.0.131.1
Blackbaud.Installer.SFX.FourZero.exe	4.0.131.1
Blackbaud.Installer.UI.Common.dll	4.0.131.1
Blackbaud.NetCommunity.EA7Controls.dll	4.0.131.1
Blackbaud.NetCommunity.EA7Core.dll	4.0.131.1
Blackbaud.NetCommunity.EA7DataSources.dll	4.0.131.1
Blackbaud.NetCommunity.EA7Parts.dll	4.0.131.1
Blackbaud.NetCommunity.EA7Revisions.exe	4.0.131.1
Blackbaud.NetCommunity.EA7Service.dll	4.0.131.1
Blackbaud.NetCommunity.EA7SPWrap.dll	4.0.131.1
Blackbaud.NetCommunity.EEShelbyPlugin.ProfileUpdate.dll	4.0.131.1
Blackbaud.NetCommunity.Web.CacheHandlers.dll	4.0.131.1
Blackbaud.RE7Service.dll	4.0.131.1
Blackbaud.RE7XData.dll	4.0.131.1
Blackbaud.Web.Content.BuildTasks.Common.dll	4.0.131.1
Blackbaud.Web.Content.BuildTasks.dll	4.0.131.1
Blackbaud.Web.Content.Common.dll	4.0.138.7
Blackbaud.Web.Content.Core.dll	4.0.138.7
Blackbaud.Web.Content.PluginService.dll	4.0.131.1
Blackbaud.Web.Content.Portal.dll	4.0.138.7
Blackbaud.Web.Content.Revisions.exe	4.0.131.1
Blackbaud.Web.Content.ScorpioCore.dll	4.0.131.1
Blackbaud.Web.Utils.NetCommunity.UserImport.Library.dll	4.0.131.1
Blackbaud.Web.Utils.NetCommunity.UserImport.Service.dll	4.0.131.1
CustomForm.Common.dll	4.0.131.1
CustomForm.EducationEdgeImporter.dll	4.0.131.1
CustomForm.EducationEdgeImporter.Plugin.dll	4.0.131.1
CustomForm.EducationEdgeImporter.Revisions.dll	4.0.131.1
CustomForm.EE.Admissions.ExporterContext.dll	4.0.131.1
EEShelbyPlugin.dll	4.0.131.1
EEUserImport.dll	4.0.131.1
NCUserImporter.exe	4.0.131.1
OnlineExpressPlugin.dll	4.0.131.1
PostSBMergeSync.exe	4.0.131.1
RE7ShelbyPlugin.dll	4.0.131.1
SettingsEditor.exe	4.0.131.1
Setup.exe	4.0.131.1
Setup.exe	4.0.131.1
Setup.exe	4.0.131.1
Setup.exe	4.0.131.1