This service pack is cumulative. It includes all issues addressed in CRM 4.0 prior to Service Pack 1, as well as any new features and changes outlined below. When you integrate CRM and Blackbaud Internet Solutions, we recommend you make sure both applications are running the same version and service pack.
For information about all of the new features released in 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.
To improve password reset security in email messages from Blackbaud Internet Solutions, 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 the email message.
Tip: The ability to create a special page to link to your user login page (that you define for Page settings in Sites & settings) previously existed. With this feature, any page that contains a User Login part now appears from the drop down and you want to select the user login page that navigates users to your forgotten password page.
This new link remains active in an email for the user to take action to reset the password any time.
When an email 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.
Previously, the Password merge field was available in email messages that use a Registered Users data source. With this update, this merge field no longer includes the password in an email. When a recipient receives the message, the placeholder for the field is blank. As a result, make sure you remove the Password field and create user login password reset page links in email messages to guide your users to reset their password.
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. Please refer to this list to determine whether your organization needs to take any action.
To prevent you from inadvertently removing active content from your Blackbaud Internet Solutions website, you can no longer delete parts when they are associated with web pages. When you attempt to delete a part that is associated with a single site, or shared across multiple sites, a message appears to inform you that you cannot remove it because it exists on a page.
To identify the pages where the part appears, select the part's Usage tab.
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.
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.
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.
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.
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.
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. You can now use the new Update only NCOA changes option, which allows you to only update addresses that have been changed by the process.
You access this screen from the Data Tune-Up page from Administration. For the AddressFinder process you want to edit, under Step 3, click Edit Properties.
In Blackbaud CRM 4.0, we introduced amendments on the Activity tab of a recurring gift record. Under Activity, most amendments associated with a recurring gift appear and are sorted by the most recent event. Amendments represent any manual or global process change to the properties of a recurring gift. For example, when you edit the payment method of a recurring gift or change the recurring gift's status, these actions are recorded as amendments on the activity timeline.
For the United States, with Service Pack 1, for recurring gifts with a payment method of "Direct debit - pay is automatically," the Mandate field is now captured. This field only appears when a European (SEPA) banking system is enabled and the currency is set to Euros. This change is captured when you edit the field on the Edit payment method details screen of a recurring gift, and through an Enhanced Revenue Batch and Revenue Update Batch.
For the United Kingdom, with Service Pack 1, additional fields are now captured as amendments on the activity timeline. These changes are captured when you edit fields on the Edit payment method details screen of a recurring gift, and through an Enhanced Revenue Batch and Revenue Update Batch.
For recurring gifts with a payment method of "Direct debit - pay is automatically," changes to the following fields are now captured as amendments: DDI source, DDI source date, Advance notice sent, Send instruction, New instruction sent, Cancel instruction sent, and Set-up instruction sent.
For recurring gifts with a payment method of "Standing order," changes to the following fields are now captured as amendments: Reference date, Account, Standing order has been setup, Setup on, Use system-generated reference number, and Reference number.
For recurring gifts with a payment method of "Direct debit - pay is automatically," the Mandate field is now captured. This field only appears when a European (SEPA) banking system is enabled and the currency is set to Euros.
In Service Pack 1, we added "Cash" and "Check" as Payment method field options on a recurring gift record. By selecting either option, you can track the number of recurring gifts associated with a cash or check payment method in a given time period. This may be useful in reports or for general reference.
"Cash" and "Check" now appear as Payment method field options and are reflected in the following locations:
Under Payment information on the Add a recurring gift screen.
Edit payment method details screen for a recurring gift.
Transaction summary section for a recurring gift record.
Update recurring gift statuses business process.
Amendment details on the Activity tab of a recurring gift.
Revenue queries.
Revenue Update Batch, Enhanced Revenue Batch, and Sponsor Batch.
Add, transfer, and reassign sponsorship screens as well as the Add a recurring additional gift screen.
In Service Pack 1, we made changes to the behavior of skipped installments. From the Activity tab of a recurring gift record, you can now skip any expected installment in the following scenarios:
The installment date is no more than five days prior to the current date.
No payments or write-offs have been applied to the installment.
No payments have been applied to any installment after the one you want to skip.
There are no skipped installments after the one you want to skip.
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.
For better property valuation estimates, Target Analytics has improved our algorithm for the property value model. This change enables us to consider additional property estimates in the property valuation formula.
CoreLogic property data can be found on the constituent's wealth and ratings record, Assets tab, under the Real estate section.
In January 2015, we updated NOZA, FEC, Dun & Bradstreet, and CoreLogic data used in WealthPoint.
Note: With the CoreLogic data update, we saw a greater population of total market value in Indiana property records.
NOZA: The world's largest database of public charitable donations. This information is stored on the constituent's wealth and ratings record, Giving tab, under Philanthropic gifts. For each donation, a gift range, organization donated to, organization category, gift year, and name on the gift returns. You can use the web address or source material to help you confirm the data belongs to your prospect.
FEC: Federal Elections Commission data, from the Internal Revenue Service, contains information on election and political campaign contributions to identify political affiliations and business giving to PACs and political campaigns. This information includes the amount of the contribution, the recipient, and the date. This information is stored on constituent's wealth and ratings record, Giving tab, under the Political donations section.
Dun & Bradstreet: The world's leading source of commercial information and insight on businesses to identify business ownership, equity, and leadership positions in public and private companies. Provides you with data about the constituent's employment. This information is stored on the constituent's wealth and ratings record, Assets tab, under Businesses section.
CoreLogic: Tracks the constituent's real estate holdings including real estate valuation estimates. Identifies properties owned for a deed, parcel, and mortgage. This information is stored on the constituent's wealth and ratings record, Assets tab, under the Real estate section.
We have added two new query source views from the Blackbaud Data Warehouse: "Revenue (from the Blackbaud Data Warehouse)" and "Revenue Recognition Credits (from the Blackbaud Data Warehouse)."
These queries are similar to their counterpart queries from the transactional database. The 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.
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.
To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh.
Comment | Work Item | Location | Knowledgebase |
---|---|---|---|
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 |
|
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 |
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 |
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 |
|
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 |
|
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 |
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 |
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 |
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 |
|
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 |
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 |
|
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 |
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 |
To improve email performance, this fix significantly reduces the time it takes to process a Blackbaud Direct Marketing email effort. | 451645 | All assemblies |
BB750474 |
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 |
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 |
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 |
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 |
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 |
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 |
|
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 |
|
Previously, when editing a pledge in an Enhanced Revenue Batch, the receipt amount sometimes displayed as zero. With this fix, the receipt amount displays correctly. | 448133 | All assemblies |
|
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
|
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
|
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 |
|
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 |
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 |
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 |
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 |
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 |
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 |
|
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 |
|
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 |
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 |
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 |
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 |
|
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 |
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 |
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 |
|
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 |
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 |
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 |
New Feature: From the Activity tab of a recurring gift record, you can now skip any expected installment in the following scenarios: installment date is no more than five days prior to the current date; no payments or write-offs have been applied to the installment; no payments have been applied to the installment that is scheduled after the next expected installment; and no installments after the next expected installment have been skipped. | 441402 | All assemblies |
|
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 |
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 |
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 |
|
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 |
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 data lists 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 |
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 |
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 |
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 |
|
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 |
|
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 |
|
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 |
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 |
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 |
|
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 |
This fix helps prevent constituents from receiving duplicate emails sent from Blackbaud Internet Solutions. | 436116 | All assemblies |
BB751626 |
New Feature: Now when you export a data list 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 |
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 |
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 |
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 |
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 |
|
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 |
|
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 |
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 |
|
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 |
|
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 |
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 |
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 |
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. To take advantage of this fix, you must redeploy the Blackbaud Data Warehouse and complete an incremental refresh. | 421794 | All assemblies |
|
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 |
|
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 |
|
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 |
|
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
Assembly | Patch |
---|---|
All assemblies | 4.0.138.2 |
Installer filename | SHA-1 Hash |
---|---|
BlackbaudInstaller.exe | 8FE6EA3BE6CD6F104FF3B24C786B0F36E875CE86 |
Comment | Work Item | Location | Knowledgebase | Patch |
---|---|---|---|---|
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 | |
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 | |
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 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 |
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.Marketing.NetCommunityIntegrationCatalog.dll | 4.0.131.1 |
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.2.1 |
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.131.1 |
Blackbaud.Web.Content.Core.dll | 4.0.131.1 |
Blackbaud.Web.Content.PluginService.dll | 4.0.131.1 |
Blackbaud.Web.Content.Portal.dll | 4.0.131.1 |
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 |