Salesforce integration release notes (Nonprofit Success Pack) - archive – GoFundMe Pro Help Center

2023 release notes
2022 release notes
2021 release notes
2020 and earlier

Before you start

On May 6, 2025, Classy became GoFundMe Pro. You may still find that name throughout these notes for releases before that date.

Check out our current release notes to stay updated on our latest features and bug fixes in the Salesforce integration.

November 13, 2023

Classy for Salesforce 7.2: Julian

Classy for Salesforce Version 7.2 includes an improved way to change the data processing method from within the Classy Control Panel V2, the ability to fetch Supporter records with the Data Sync Tool, as well as several bug fixes.

Important Changes:

There's a new type of API Request that will now sync for studio campaigns & create a campaign record with the Type = "Studio."
The Data Sync tool will now fetch Supporter records.
Within the Data Processing settings in Classy Control Panel V2, an admin can now change the method of data processing used by the package within the Data Process Mode dropdown:
- Batch: asynchronous method that processes API Requests 1 by 1 as they come into Salesforce. This is the default method for all organizations when the package is installed.
- Queueable: asynchronous method that allows for multiple processing threads of API Requests as resources are available. This method processes more quickly than batch and can be used when expecting higher volumes of data. However, data skew errors are more prevalent with this method and some data may need to be resynced.
- Dynamic Bulkification: asynchronous method that processes API Requests in bulk, up to 20 records at once, reducing the possibility of data skew and data loss. This method is best for high volumes of data processing and data integrity concerns. Because of its efficiency, bulkification processing will likely add time to records being processed during high volume and, as a result, will slow down the "real-time" sync, but will ultimately ensure data parity with improved data quality.

Bug Fixes:

Resolved an issue from Version 7.1021 where organizations were seeing an increase in Classy Log records being created.
Resolved an issue where fundraising_page.updated & fundraising_team.updated API Requests were being skipped resulting in inconsistent records. These messages will now process successfully as the fundraising page or team already exists in Salesforce.
Resolved an issue where the Classy Housekeeping scheduled job was failing with a 10001 DML error.
Resolved an issue where Apex Jobs would sporadically fail with a recompilation error.
Resolved an issue where the ClassyAPISupporterContactMatching job was creating empty Account records if the organization was not using NPSP.
Resolved an issue where the ClassyAPISupporterContactMatching job was attempting to match Classy Supporter records that did not have an email address. The job will now only attempt to match Classy Supporters with a Contact if an email address is present.
Resolved an issue where the ClassyRecurringProfileBatch job was throwing an error if Classy for NPSP was not installed.
Resolved an issue where a number less than 30 could not be set in the Delete Records Days in the Past setting within the Package settings in the Classy Control Panel V2. Now a number of 1 or greater can be saved in the setting.
Resolved an issue where the CreateAttendeeContactBatch job would fail if more than 50 related entities were missing the Contact lookup.
Resolved an issue where if State/Country Picklists were active and the donor's country was Non-US the Country code was not set in the Address.
Resolved an issue where Dynamic Bulkification data processing wasn't handling uncaught exceptions properly. Now, the processing method will move on to the next request in the batch as expected instead of attempting to reprocess the same record.
Resolved an issue where Channel Integration Jobs were not being scheduled via the UI for new installations.

Classy for NPSP 1.5: Jasmine

Classy for NPSP Version 1.5 is a bug fix version that mostly resolves issues with GAU & GAU Allocation creation.

Bug Fixes:

Resolved an issue where NPSP Recurring Donation record failed to be created due to a null pointer exception. This bug only impacts Recurring Donations that exist in Classy but don't exist in Salesforce.
Resolved an issue where GAU records were linked to a Classy Designation if the C4NPSP GAU functionality is active and there is no External Reference ID set.
Resolved an issue where the GAU Allocation was not correctly set on recurring plan installments after the first transaction.
Resolved an issue where the C4NPSP package version was not correctly updated in the Classy Control Panel V2.

September 28, 2023

Classy for Salesforce 7.1021: Julian

Classy for Salesforce Version 7.1021 includes a new setting to prevent the creation of Contacts for Attendees for ticketed events during the real-time sync as well as a way to create those Contacts at a later time.

Important Changes:

A new setting in the Classy Control Panel V2 > Settings > Campaigns tab titled "Prevent Attendee to Contact Creation for Ticketed Events" to stop creating Contacts for Attendees of a ticketed event.
- This setting helps prevent Contacts from being overwritten when Attendee data is updated in Classy or Classy Live.
- It is recommended to turn the setting on before the registration period begins.
New fields on the Classy Related Entity object to track Attendee data updates:
- Classy Attendee First Name (stayclassy__classy_first_name__c)
- Classy Attendee Last Name (stayclassy__classy_attendee_last_name__c)
- Classy Attendee Email (stayclassy__classy_attendee_email__c)
A new report in the Classy Control Panel V2 titled "Classy Related Entities" allows admins to easily review Attendee data at the registration level.
A new button in the Classy Control Panel V2 > Settings > Campaigns titled "Create Attendees as Contacts" to start a batch job that will immediately run and evaluate all Classy Related Entities without a linked Contact in the Classy Member field, then use the Classy Attendee First Name, Classy Attendee Last Name, and Classy Attendee Email fields to match/create Contacts and link to the Related Entity.
New API callouts back to Classy after Supporter and Designation API Requests are processed, which will allow Classy to track success and failure of processing in Salesforce.

Bug Fixes:

Resolved an issue where the Field Mapping Tool UI within the Classy Control Panel V2 was breaking if the destination field was no longer in the org. Now the UI will show the API name of the deprecated field.
Resolved an issue where the user that runs scheduled jobs was not always updated to the authenticated user.
Resolved an issue where if Bidirectional Sync was turned on in an org with NPSP, a "ClassyContactTrigger Batch cannot be called by a future method" error was thrown during Contact updates.

September 12, 2023

Classy for NPSP 1.4903: Iris

Classy for NPSP Version 1.4903 includes a fix to recurring donation processing for organizations that have over 50,000 opportunity records.

Bug Fixes:

Resolved an issue where a change in Recurring Donation logic processing caused over 50,000 Opportunity records to be queried if a null ID was returned during creation of new recurring donation records in Salesforce. This issue only prevented new NPSP recurring donation records from being created.

September 7, 2023

Classy for Salesforce 7.1006: Julian

Classy for Salesforce Version 7.1006 includes a fix to the 'ClassyApiSupporterContactMatchingBatch' APEX job which resolves an issue where new Contacts were being created and linked to a Classy Supporter if no existing Contact was found.

Bug Fixes:

Resolved an issue where the scheduled APEX job called 'ClassyApiSupporterContactMatchingBatch' was unexpectedly creating Contacts if no existing Contact record was found.

August 29, 2023

Classy for Salesforce 7.0: Julian

Classy for Salesforce Version 7.0 includes a new feature: Bidirectional Supporter Sync. Additionally, this version includes updates made to the Classy Control Panel V2, an improvement to NPSP email matching, and several bug fixes.

Important Changes:

Bidirectional Supporter Sync: With Bidirectional Supporter Sync, any changes made to the supported fields on a Contact that has a linked Classy Supporter record will automatically sync back to Classy.
- This feature is not activated upon upgrade. In order to activate this feature, navigate to the Classy Control Panel V2 > Settings > Data Processing > toggle the Bidirectional Sync setting to 'active'.
- Supported fields:
  - First Name
  - Last Name
  - Address (Street, City, State, Postal Code, and Country)
  - Phone
- Introduced a scheduled job called 'ClassyApiSupporterContactMatchingBatch' to help ensure that all Classy Supporter records are linked to a Contact record which will ensure the bidirectional sync works as expected.
Classy Control Panel V2 Updates:
- Within the Settings menu in the Classy Control Panel V2, there is now a Scheduled Jobs tab that will allow admins to schedule and reschedule Classy jobs easily.
- Within the Campaign Settings tab, there is now a setting available to turn off Attendee Campaign Member creation for event campaigns.
Update to NPSP Email Matching: Now, when the NPSP Email Matching setting is active in the Classy Control Panel V2, the integration will use the first name, last name, and email from the supporter or transaction to identify a match based on these three criteria. The email search will be across NPSP email fields only.

Bug Fixes:

Resolved an issue where the Contact lookup on Classy Custom Answers was intermittently not being populated for Donors & Attendees.
Resolved an issue where the ClassyRecurringProfileRollupBatch would throw an error related to Classy for NPSP due to an issue with creating new Recurring Donor records.
Resolved an issue where the Classy Campaign Parent ID and Parent Campaign lookup field on Team and Fundraising Page type Campaign records was not populated consistently.
Resolved an issue where the Classy Member ID was not always being set on Contacts created and/or updated by the Classy integration.
Resolved an issue where a '50001 too many query rows' error would be thrown when trying to associate a Team Captain to a fundraising team/page if there were more than 50k contacts without a Classy Member ID in Salesforce.
Resolved an issue where 'Find Missing Data' could be selected on the Data Sync Tool to kick off a job without all required fields entered.
Resolved an issue with the offline donation bidirectional sync where the donation would fail to be created in Classy if a fundraising page was selected as the Primary Campaign Source in Salesforce.
Resolved an issue where the Name fields on the Classy Supporter object in Salesforce did not match the field length in Classy.
Resolved an issue where Fundraising Team update and created API Requests would be skipped causing missing and/or incorrect data in Salesforce.

Classy for NPSP 1.49: Iris

Classy for NPSP version 1.49 includes bug fixes for inconsistent behavior with Opportunity naming and some scheduled job errors related to creating Recurring Donation records.

Bug Fixes:

Resolved an issue where the NPSP Opportunity name was not respected and Classy would overwrite it. This issue was mostly related to Recurring Donation installments.
Resolved an issue where Recurring Donation record creation would fail due to various reasons and throw an exception in Classy Logs.

June 20, 2023

Classy for Salesforce 6.94: Clairemont

Classy for Salesforce Version 6.94 is a bug fix version resolving issues with campaign statuses updating to 'Unpublished', a minor data sync tool issue, and crypto donations failing to be created.

Bug Fixes:

Resolved an issue where Campaigns in Salesforce were not updated with an "Unpublished" status and the active checkbox was not unchecked if unpublished/deactivated in Classy
Resolved an issue where if an org's timezone is set to GMT +X the data sync tool would return an API error
Resolved an issue where the Processor ID field character limit caused crypto donations to fail to be created

Classy for NPSP 1.48: Hydrangea

Classy for NPSP version 1.48 includes a bug fix for recurring donation plan records failing to be created or updated after the first payment.

Bug Fixes:

Resolved an issue where Recurring Donation plans failed to be created or updated when a subsequent payment was processed due to a Day of Month missing error

April 25, 2023

Classy for Salesforce 6.932: Encinitas

Classy for Salesforce Version 6.932 includes an update that resolves an issue where Classy for NPSP was unable to be uninstalled due to a component reference error, as well as a fix for an issue where NPSP email matching was always running.

Bug Fixes:

After the upgrade, the Classy for NPSP package can now be uninstalled successfully without a component reference error preventing uninstalling
Resolved an issue where NPSP Email Matching was always running if C4NPSP was installed regardless of if the setting was toggled on or not

Classy for NPSP 1.471: Gardenia

Classy for NPSP version 1.471 includes an update to the post-install script that removes C4NPSP package references in the Control Panel V2.

Bug Fixes:

Post-install script makes an update to correctly remove the C4NPSP package references in the Control Panel V2
- Removes NPSP from the Settings dropdown
- Removes the C4NPSP version number from the Control Panel V2 home page

If a C4NPSP version earlier than 1.471 is uninstalled and C4SF stays installed in an environment there can be a scenario where the NPSP references stay visible in the Control Panel V2 even though C4NPSP in not installed.

March 28, 2023

Classy for Salesforce 6.93: Encinitas

Classy for Salesforce Version 6.93 includes a new updated Custom Field Mapping UI within the Control Panel V2 for managing and creating custom mapping records in Salesforce.

The Classy Custom Field Mapping Tool has been moved into the Control Panel V2. Now, with an updated UI, there is field-level validation during the creation of field mapping records and a search box to more easily navigate through existing mappings. All previously existing mappings will be visible in the table after upgrading to version 6.93.
Bidirectional offline donation sync now supports syncing offline Company Donations. In order for an offline donation to be created as a Company, the Company Name (stayclassy__company_name__c) field must be filled in on the opportunity instead of the billing first and last name fields.

Bug Fixes:

Resolved an issue where duplicate offline donations were being created in Salesforce when the offline bidirectional sync feature was being used
Resolved an issue where opportunities created in Salesforce and synced back to Classy via bidirectional offline donation sync were being re-parented to Classy Bucket Account if no email was set in the Classy Member Email field.
Resolved an issue where the Classy Campaign field was set with the campaign set in the Primary Campaign Source field regardless of the type.
Resolved an issue with the Data Sync Tool not running as expected if Queueable processing was active (Queueable is not on by default, only organizations with large amounts of data syncing would have this method active)
Resolved an issue where if State/Country picklists are active, the address could be set without a Country
Resolved an issue where Recurring Donation Plans were not receiving the correct status update due to the order in which update events were being sent to Salesforce

Classy for NPSP 1.47: Gardenia

Classy for NPSP version 1.47 includes bug fixes related to Recurring Donations and Company Donations.

Bug Fixes:

Resolved an issue where the Next Payment Date had logic to prevent a date after the 28th to be set
Resolved an issue where offline Company Donations were failing to be created due to a missing query field

January 27, 2023

Deprecation of Support Notice: January 31, 2023

Current Classy for Salesforce customers on packages 6.81 or below are encouraged to update their instance. Starting on January 31, 2023, support will be deprecated for versions 6.81 and below. Customers on versions 6.82 and above will not be affected. Rest assured, versions 6.81 and below will still function as is, but any support related requests will require updating before we can assist.

January 25, 2023

The most recent releases for Classy for Salesforce have been geared towards improving existing functionality and some minor bug fixes.

Classy for Salesforce 6.92

Channel Transactions from Facebook and Double the Donation are now syncing to Salesforce after being created in Classy
The Data Sync tool will no longer find and create transactions with a failed status
Resolved an issue where transaction ID was set in the ‘Dedication ID’ field even if no dedication was created on a transaction

Classy for NPSP 1.46

Recurring Donations are now being updated as expected
‘Next Payment Date’ is now being correctly set on Recurring Donation records

November 14, 2022

Classy for Salesforce 6.90: Leucadia

Classy for Salesforce Version 6.90 introduces a new optional method of processing data in bulk to more efficiently transform Classy data into Salesforce records during peak giving times along with a few minor bug fixes.

Important Changes:

Dynamic Bulkification: New functionality to bulk process Classy API Requests during high volumes in order to create records more efficiently within Salesforce
- Customers that would like to turn on this type of processing need to reach out to our Care team
- Find out more about bulk processing API requests

Bug Fixes:

Resolved an issue where the Transaction Type was not correctly reflected on Opportunities consistently.
Resolved an issue where Source Codes could not be resynced by the Care team.

Classy for NPSP 1.45: Evergreen

Classy for NPSP version 1.45 includes a few minor bug fixes for GAU Allocations not updating and Recurring Donation statuses not updating as expected.

Bug Fixes:

Resolved an issue that occurs when a Classy Program Designation gets updated on a transaction record, the GAU Allocation should now update as well.
Resolved an issue of Recurring Donation statuses not updating as expected.

September 27, 2022

Classy for Salesforce 6.89: University Heights

Classy for Salesforce Version 6.89 includes several bug fixes and a new field to store cancellation reason to the Classy Recurring Donor record.

Important Changes:

Added a new field to Classy Recurring Donor object called "Cancellation Reason" (stayclassy__cancellation_reason__c) to store the reason a recurring plan was canceled.
- Note: Cancellation reason will not sync to NPSP Recurring Donations yet
Updated the functionality of the Opportunity Soft Credit Setting in the Control Panel, now the value set for soft credits will be applied to Fundraisers and Team Captains (before it was only applied to Fundraisers)
Added several new fields to the Campaign, Opportunity, and Classy Recurring Donor objects to support a future release of improved Donor Covered Fee functionality. Additional details on these fields will be published when the functionality is released on the Classy Platform.
- Campaign fields:
  - Donor Covered Fees Active (stayclassy__dcf_enabled__c)
- Opportunity fields:
  - Donor Covered Fees (stayclassy__is_donor_covered_fee__c)
  - Intended Donation Amount (stayclassy__raw_initial_gross_amount__c)
  - Adjustment Amount (stayclassy__raw_adjustment_amount__c)
  - Flex Rate % (stayclassy__flex_rate_percent__c)
- Classy Recurring Donor fields:
  - Donor Covered Fees (stayclassy__is_donor_covered_fee__c)
  - Intended Donation Amount (stayclassy__raw_initial_gross_amount__c)
  - Adjustment Amount (stayclassy__raw_adjustment_amount__c)
  - Flex Rate % (stayclassy__flex_rate_percent__c)

Bug Fixes:

Resolved an issue where the Recurring Start Date is no longer overwritten on subsequent updates.
Removed the dependency of Enhanced Contact Matching being active for the NPSP Email Matching setting to work as expected. NPSP Email Matching can now be used without having Enhanced Contact Matching configured.
Resolved an issue where the Opportunity Record Type setting was storing a text value instead of the record id after install.
Resolved an issue where the Control Panel V2 would sometimes throw a component error after installing 6.88.
Resolved an issue where dedication information for offline donations required a double save in Classy to populate in Salesforce.

Classy for NPSP 1.44: Evergreen

Classy for NPSP version 1.44 includes a new Control Panel setting to set a custom stage name for pledge functionality, and a fix for Next Donation Date being set incorrectly on Recurring Donation records.

Important Changes:

Added a new setting in the Control Panel V2 Settings > NPSP > Custom Opportunity Pledged Stage Name, to set the stage name of the records that should be removed when a successful recurring donation iteration syncs.
- If your organization uses a status for future opportunities outside of the default “pledged” status, action will need to be taken after upgrade.

Bug Fixes:

Resolved an issue where the Next Donation Date was set incorrectly, after upgrade new recurring donation plans will have the next donation date set correctly.
Resolved an issue where the NPSP naming convention was unexpectedly being overwritten with the Classy opportunity naming convention.

August 1, 2022

Classy for Salesforce 6.88: Point Loma

Classy for Salesforce Version 6.88 includes support for Classy Live transaction types - a new field for identifying reprocessed transactions (Opportunities), and UI notifications for the Data Sync Tool jobs.

Important Changes:

Classy Live Transaction Types will now sync to the Transaction Type (stayclassy__transaction_type__c) field on the Opportunity object:
- Good
- Auction
Is Reprocessed (stayclassy__is_reprocessed__c) checkbox on opportunities
Data Sync Tool UI notifications to alert users of Data Sync Job statuses
Preventing "Pending" ACH transactions from syncing to Salesforce to reduce discrepancies
Added support for EFT, Crypto, Stock Donations, and Corporate Matches to the payment method field for offline donations from Classy
Added in Opportunity Data Fetch Retry logic to reduce the occurrence of hard failures when fetching Data from Classy

Bug Fixes:

Added a fix to prevent permissions errors with scheduled jobs by having these jobs scheduled by the admin that authenticates the integration
- This fix will be for new installs moving forward, however, if your organization receives errors noting insufficient privileges related to a Classy job, please reach out to our Care team for resolution.

July 7, 2022

Classy for NPSP Version 1.4301: Dahlia

Summary

Classy for NPSP version 1.4301 is a bug fix version to resolve an issue from version 1.43 where recurring opportunities were being incorrectly deleted when using a custom StageName.

Bug fixes

Resolved an issue where recurring opportunities were deleted and updates failing with an error of “ENTITY_IS_DELETED” in environments where a custom Opportunity StageName is configured.

June 15, 2022

Classy for Salesforce Version 6.87: Point Loma

Summary

Classy for Salesforce Version 6.87 includes back-end improvements to the data sync tool, a change with how supporter name is split into first and last name, and resolves an issue with record type settings being respected.

Bug fixes

Resolved an issue where the data sync tool was running longer than needed because of excess callouts being executed. The job is now streamlined and should operate more efficiently.
Resolved an issue where not all and/or duplicate custom questions and/or ticket types were being returned in by the data sync tool
Resolved an issue where if an admin attempts to sync over 500 campaigns from one Classy account using the data sync tool, an error would occur
Resolved an issue where the Supporter name was incorrectly being split and stored in first and last name fields. Now, the values entered in the first name text box and last name text boxes on the checkout form are correctly mapped into corresponding Salesforce fields.
Resolves an issue where the Opportunity Record Type selected in Classy settings wasn’t being respected

Classy for NPSP Version 1.43: Dahlia

Summary

Classy for NPSP version 1.43 contains fixes related to open installments not being correctly updated (Recurring Donations) and now updating the status field on Recurring Donations.

Important Changes

The Classy for NPSP extension will now write to the status field on Enhanced Recurring Donation records. If there is a status change to a recurring plan in Classy, the change is now reflected on the NPSP Recurring Donation record.

Bug fixes

Resolved an issue where if an open installment associated with an NPSP Recurring Donation record was in a status other than “Pledged” the record was not updated as expected. Now, if an opportunity is related to a recurring plan and in any status other than Closed Won, it will be updated by the integration as expected.
Resolved an issue where two opportunity records were created & associated with a Recurring Donation during record creation. Now, only one Closed Won opportunity is created & associated with the Recurring Donation record.
Resolved an issue where the Daily frequency wasn’t created after installing the package, and therefore resulted in missing Recurring Donation records specific to the Daily frequency.

May 19, 2022

Classy for Salesforce Version 6.86: Point Loma

Summary

Classy for Salesforce Version 6.86 includes fixes for issues where events data weren't being created as expected and opportunities were incorrectly associated with the Classy Bucket Account.

Note: If you need any data cleanup related to a bug we fixed in this version, please reach out to our Care team.

Bug fixes

Resolved an issue where opportunities were incorrectly being associated to a Classy Bucket account
When ticket names in Classy include double quotes ("Example"), ticket creation no longer fails
Products, Related Entities, and Opportunity Contact Roles are now created as expected for registrations
Resolved an issue where the Team campaign record was not updated to Deleted status
Resolved an issue where a scheduled job wasn't respecting the Delete Logs & API Request settings. Records now delete as expected.

March 7, 2022

Classy for Salesforce Version 6.85: Cardiff

Summary

Classy for Salesforce Version 6.85 is mostly a bug-fix version, with a new start date field on Classy Recurring Donors to improve reporting and date accuracy.

Important changes

A new field has been created to store the Start Date for Recurring Donation Plans without a time value. This field is on the Classy Recurring Donors object, is labeled Classy Recurring Start Date (stayclassy__classy_recurring_start_date__c), and will be populated moving forward. *Note: We have not deprecated the Recurring Start Date field yet.
The Classy Designation lookup will now be set on Classy Recurring Donors.
The 'Description' field on offline donations will now sync over to Salesforce to a field on opportunities called "Classy Offline Description" (stayclassy__classy_offline_description__c).

Bug fixes

Resolved an issue where the Recurring Start Date on Classy Recurring Donors was converted from UTC incorrectly
Resolved an issue where 'Ended' status was not correctly reflected in Salesforce
Resolved an issue where the transaction type was not being updated correctly for Registration opportunities
Resolved an issue where opportunities created by the channel transaction sync job, specifically for Facebook and Instagram, were created with the incorrect opportunity naming convention
Added a WHERE clause/LIMIT the SOQL query running for NPSP Email Matching to reduce errors
Resolved an issue where the Custom Field Mapping Tool was failing when mapping boolean values
Resolved an issue where registrants who created/joined a Team were being added as Campaign Members with a 'Donor' status.
- A registrant who joins a team will receive a 'Team Member' status, and a registrant that creates a team will receive a 'Team Captain' Campaign Member status.
While not dependent on installing 6.85, we also resolved an issue on 3/4 where some recurring donations were not syncing during the real time sync.

November 15, 2021

Version 6.84: Kensington

This release includes the ability to sync offline donations from Double the Donation to Salesforce, along with a few additional bug fixes.

Important Changes

From the Control Panel V2 > Settings > Channel Integrations, it’s now possible to configure settings for matching gifts from Double the Donation to sync over to Salesforce if the additional configuration is turned on for the Double the Donation integration.

These opportunity records will be created and linked to a corresponding Account matched or created based on Company Name and will have the parent transaction ID set to indicate which online gift the match was started from.

Bug Fixes

Fixed an issue where the start date was not populated on team campaign records created
Fixed a SOQL query that resulted in fundraising pages failing to sync if more than 200 team campaigns were associated with the same Member Id

October 14, 2021

Version 6.83: Kensington

Summary

Classy for Salesforce Version 6.83 addresses bugs related to close date being set one day in the future and NPSP recurring donation records not being updated as expected.

Fixes

Resolved an issue for Versions 6.82+ where opportunities are being set with a close date of one day in the future. This fix will not be retroactive for existing records but new records created moving forward will have the correct close date
Resolved an issue where the team lookup field on a fundraising page campaign in Salesforce isn’t updated if a team moves to a different campaign

Classy for NPSP 1.41: Carnation

Summary

Classy for NPSP Version 1.41 includes support for syncing updates to recurring plans to NPSP Recurring Donation records, and additional recurring frequencies, Daily, Weekly, and Bi-weekly.

Important changes

If the Create NPSP Recurring Donations setting is toggled on, now records will be created with the installment frequency of Daily, Weekly and Bi-weekly.

Note: If your organization is using Enhanced Recurring Donations, the Daily frequency will need to be manually activated after upgrade. Steps: Navigate to Setup > Object Manager > Recurring Donation > Installment Period > Activate the Daily picklist value.

Fixes

Resolved an issue where NPSP Recurring Donation records aren’t being updated as expected when updates are made to recurring plans in Classy.

September 1, 2021

Version 6.8204: Mission Hills

Summary

Classy for Salesforce version 6.8204 includes several bug fixes related to Supporter matching functionality, offline donations, and the custom field mapping tool. This version also introduces a new feature: the ability to sync Instagram donations from Classy into Salesforce.

Fixes

Resolved an issue where contacts were still being updated regardless of the Contact update setting configuration, intermittently. Now, updates to contact fields records will align with setting configuration
Resolved an issue where Supporter to contact matching wasn't occurring even though the setting was active. After this bug fix, if the ‘Use Supporter Matching for Contact matching/creation’ setting is active, the integration will use Supporter ID to find an existing supporter and use the related contact to associate incoming records and update the contact record data
Resolved an issue when the ‘Use Supporter Matching for Contact matching/creation’ setting was active, the Billing name and address were used to update the Supporter record. Now when this setting is enabled, Supporter name will be populated on the Supporter record and updated on the Contact record
Resolved an issue where offline donations without an email address were failing to sync due to a missing Supporter ID. Now, offline donations without email addresses will be associated with a Classy bucket account without a contact so that offline donations can flow through to Salesforce
Resolved an issue where when a Supporter’s name was longer than 40 characters, the opportunity creation would fail. Now, no opportunities should fail due to supporter field limitations
Resolved an issue where the Classy Field Mapping Tool wasn’t handling mapping boolean values to custom fields of the same type successfully. Now, all boolean type field mapping will occur when a record is created or updated

June 10, 2021

Version 6.8101: Hillcrest

Summary

Classy for Salesforce Version 6.8101 includes functionality to sync online Company donations to Salesforce and resolves a few bugs, most notably a fix for offline company donations failing to sync and contacts intermittently updated/created with missing first name, missing last name.

Important changes

New Functionality: Online Company donations will now sync to Salesforce and perform an exact match using the name entered on the checkout form to find an existing Account or create a new Account record. These opportunities will also have a contact associated based on the billing/supporter names used during checkout, but the matched or created contact will not be reparented to the matched account.

Fixes

Resolved an issue where Company offline donations were failing to sync to Salesforce after the previous update. After updating to 6.8101, the data sync tool can be used to resync any historical records that failed to sync
Resolved an issue where Contacts were being updated with Missing First Name, Missing Last name when the Create/Match contacts with Supporter data setting is active
Updated a query specific to NPSP email matching where a limit was hit if an org had a large number of contacts without NPSP email fields populated

April 19, 2021

Version 6.8: Hillcrest

Summary

Classy for Salesforce Version 6.8 includes improved contact management features that allow matching across NPSP email fields, and the ability to select the type of Classy data used for contact matching and creation.

Important changes

New NPSP matching setting in the Account & Contact tab of the Control Panel V2 (Setting Name: NPSP Custom Email Contact Matching)
- Activate this setting after upgrade to match across all NPSP email fields (personal, alternate, and work + standard email address)
- Enhanced Contact Matching must be enabled
- NPSP must be installed in your org (Note: Classy for NPSP is not required)

New Control Panel setting to determine the type of Classy data used to create and match Contacts. (Setting Name: Use Classy Supporter information for Contact matching and creation)
- Consider your current data sets when enabling this setting, and how existing contact data can be overwritten with the change in data used to populate contact fields
- Enabling the setting will only impact data going forward; it will not retroactively update any existing data

Fixes

We've added a Classy Admin permission set that auto-applies to the authenticated user to avoid any disruptions due to a Winter '21 change to authenticated user permissions for Aura enabled Apex methods
Resolved an issue where if Enhanced Contact Matching is enabled and the update contact name and contact address settings are inactive, the fields were still being updated.
Resolved an issue where if State/Country picklists are enabled, the state is not populated on the Contact address fields

April 15, 2021

Classy for NPSP 1.40: Bougainvillea

Summary

Classy for NPSP version 1.4 includes an improvement related to GAU Allocation creation and support for the Classy product release of Recurring Frequencies.

Important changes

New NPSP matching setting in the Account & Contact tab of the Control Panel V2 (Setting Name: NPSP Custom Email Contact Matching)

GAU Allocations will now be created based on the Program Designation on the transaction record, resolving discrepancies with campaign default designations and supporter selected designations
Support for Recurring Frequencies on the NPSP Recurring Donor object. Monthly, Yearly, Quarterly, and Semi-annually are now all possible Installment Periods on a corresponding NPSP plan. The only installment period that requires a picklist value activation is Semi-annual

Fixes

NPSP recurring donation records will now be set to closed when a recurring donation plan is canceled in Classy

January 15, 2021

Version 6.7002: South Park

Summary

Classy for Salesforce Version 6.7002 resolves an issue found in version 6.7 where duplicate accounts are created if Enhanced Contact Matching is enabled and a matched contact is identified.

December 16, 2020

Version 6.7 - South Park

Summary

Classy for Salesforce Version 6.7 includes a redesign of the Control Panel homepage and the ability to upgrade our managed packages directly within Salesforce along with a few bug fixes.

Important changes

Upgrade Version prompts now live directly on the Control Panel homepage, and allow for upgrading both Classy for Salesforce and Classy for NPSP directly in Salesforce.

Note: The ability to upgrade packages is still available in Classy Manager as well

Squashed bugs

Resolved an issue where the Data Sync Tool wasn’t returning online donations for syncing
Made an improvement to Contact update logic to prevent overwriting Contact data with null values based on update field settings

October 23, 2020

Version 6.61 - Normal Heights

Summary

Classy for Salesforce version 6.61 is comprised of a few bug fixes and support for an upcoming release of Digital Wallets on the Classy platform.

Important changes

Added a field to the opportunity object called Payment Source (stayclassy__payment_source__c) to support the upcoming release of digital wallets. Potential field values are:

manual
plaid
paypal
wallet
apple_pay
google_pay

Squashed bugs

Fixed an issue with the Data Sync tool where offline donations that were set to not sync with Salesforce will no longer create Opportunities
Fixed an issue where if Salesforce Shield is enabled, installing our managed package would fail
Fixed a few issues related to Classy Recurring Donation records:
- The status field will now correctly update
- The Campaign lookup field will now correctly update
- The Recur Until date (stayclassy__recur_until__c) was incorrectly populated with the cancel date, both fields will correctly reflect separate dates

September 21, 2020

Version 6.602 - Normal Heights

Summary

Classy for Salesforce version 6.602 fixes an issue related to Contact and Opportunity creation that was introduced in version 6.6.

Squashed bugs

Fixed an issue with contact creation where a "REQUIRED: last name missing" error resulted on api requests for new donations when no existing contact was returned on insert

August 27, 2020

Version 6.6 - Normal Heights

Summary

The primary feature of Classy for Salesforce 6.6 is the ability to sync fundraising, donation, and donor data related to the Classy for Facebook integration.

Technical changes

Data related to Facebook is fetched through a scheduled job on a predetermined interval (every 15 minutes) from the Classy API and processed via a batch job. When the batch runs, all Facebook related transactions will be fetched from the API and inserted into the Salesforce instance in bulk. Additionally, any new or modified Facebook transactions will be upserted by this job process.

Scheduled Job Name: ClassyScheduleApiFetchChannelTransaction
Batch Job Name: ClassyApiFetchChannelTransactionBatch

Contact settings

The following new settings are provided for Facebook donors. These settings can be configured in the Classy Control Panel within Salesforce.

Sync Classy for Facebook Transactions (boolean)
- Determines if the scheduled job will run and retrieve transactions & supporter information for Facebook donations.
Classy For Facebook Contact Settings
- Stores one of the following three options for syncing donor data from Facebook to Salesforce:
  - Never create Contact records for Facebook donors
  - Only create Contact records for Facebook donors if the donor has opted-in to share their email address
  - Always create Contact records for Facebook donors

Added fields

Channel Transaction ID (Opportunity)
Channel Fundraising Page ID (Opportunity)
Channel Supporter ID (Opportunity)
Channel Name (Opportunity)

Squashed bugs

Fixed issue where the “Update Existing Contact Name” Setting is not respected
Classy Start Date & Classy End Date fields not syncing over correctly for Campaigns

October 9, 2019

Version 6.53 - City Heights

Summary

Classy for Salesforce version 6.5300 includes fixes for issues related to the Classy Control Panel, Contact address fields being overwritten, Campaign Member/Contact creation and inconsistent format for Campaign Types. We’ve also included a minor improvement to the way new API Requests are handled.

Important changes

This list indicates alterations or changes to values for specific fields. These changes may impact workflows or other business processes, so pay careful attention if there are customizations in your org that expect specific values in these fields.

API Requests for Transactions will now be prioritized based on the event type. Transaction completed API Requests will take priority over transaction updated messages, and transaction updated API Requests will take priority over transaction created API Requests

Squashed bugs

Fixed an issue with the Classy Control Panel being unable to schedule new Apex jobs in the “Tools” section
Fixed an issue with the integration overwriting addresses in certain situations even though the “Update Existing Contact Address” Setting is turned off
Fixed some inconsistency with the “Type” field on Classy Campaigns where they would come in uncapitalized for Donation and Peer-to-Peer Campaigns
Fixed an issue in which an incorrect State and/or Country value on the supporter would cause failure on Contact creation

June 26, 2019

Version 6.522 - City Heights

Summary

Classy for Salesforce version 6.522 contains a fix to an issue where a Scheduled job could not be scheduled in the Developer Console.

Squashed bugs

Internal Campaign Name Setting [future functionality] will allow organizations to choose whether or not the Classy Internal Campaign Name or Classy External Campaign Name is used in the standard “Name” field on Campaigns

June 14, 2019

Version 6.52 - City Heights

Summary

Classy for Salesforce version 6.52 includes a number of under the hood enhancements that make way for some future Classy functionality like internal Campaign names. We’ve also included a bug fix for the Processor ID field not filling in on recurring Opportunities that some Authorize.net clients were experiencing.

What’s New

Internal Campaign Name Setting [future functionality] will allow organizations to choose whether or not the Classy Internal Campaign Name or Classy External Campaign Name is used in the standard “Name” field on Campaigns

Important changes

New field on Campaign object with API Name “stayclassy__Classy_Campaign_External_Name__c” and label “Classy Campaign External Name” which always populates with the public Campaign name [future functionality]
New field on Campaign object with API Name “stayclassy__Classy_Campaign_Internal_Name__c” and label “Classy Campaign Internal Name” which always populates with the internal Campaign name [future functionality]

Squashed bugs

Fixed an issue where Processor ID field was not populating on Opportunities for some Authorize.net recurring transactions

May 29, 2019

Version 6.51 - City Heights

Summary

Classy for Salesforce version 6.51 includes a number of fixes for issues with Event Contact Creation, Offline Donation Creation, and Source Codes.

Important changes

New field on Classy Recurring History object with API Name “stayclassy__Classy_Transaction_ID__c” and label “Classy Transaction ID” which allows for Transaction ID associated with a Recurring History record to be captured if applicable
New field on Classy Source Code object with API Name "stayclassy__Referrer_long__c” and label “Referrer” which allows for full-length referrer text to be captured
Renamed the label on the field with API Name “stayclassy__Referrer__c” to “Referrer Short” in order to distinguish it from the full-length referrer text field

Squashed bugs

Fixed an issue where Event data was not created in some situations when Salesforce State/Country Picklists feature is enabled. Now, Event data will be created as expected
Fixed an issue blocking the creation of Opportunities for Offline Donations when no email address was provided. Now, Offline Donations without email addresses are created and related to a “Classy Bucket” Account without a Contact in order to prevent unreliable matching/duplicates
Fixed an issue where Source Codes were not created if the Referrer was too long

January 31, 2019

Version 6.501 - Ramona

Summary

Classy for Salesforce version 6.501 includes a revamped version of the Data Sync Tool with more flexibility in finding and creating data. From support for timezones to filtering results and searching by ID, give your organization the ability to identify which missing records you'd like to sync before you create standard and custom objects. As always, we've included bug fixes and other improvements.

What's new

Data Sync Tool V2

The Classy Data Sync tool has been redesigned from the ground up to give you more control over missing Classy data. With this facelift, we thought it deserved its own section in the Control Panel sidebar named “Data Sync”.

Find by Type and Date Range
- Now you can choose what kind of data you want to find. Look for just transaction data, campaign data, or both over a given date range. Created date for campaigns and purchased date for transactions are used to identify records within the given date range
Timezone Aware
- In order to be more precise, your Salesforce organization timezone is now displayed and used when looking for missing data
- Note: Classy timezone is viewable on reports and may differ
View Results
- The new “Results” section allows you to see missing data before it is created. View data by its type and unique Classy ID. For power users, you can even click on records to view their raw data
Filter and Search by ID
- The results view has several filtering options including filtering by type or Classy ID. This helps in identifying the correct records you’d like to create
Create All or Individual Data
- Select individual records that you’d like to create or click “Select All” which selects all records on all pages
Nightly Data Correction
- Improvements to the tool mean our nightly data sync job gets this same great functionality. It is now even more precise when finding missing records and automatically syncing them
Email Results
- We’ve improved the completion by adding a summary of results. Summary totals include a count of records found and a count of records missing
New Logs
- For those who like to debug on their own, we’ve added additional logs which display sync results. This is especially helpful if you’d like to see what the nightly data sync job attempted to sync the previous day

Important changes

New object named “Classy Temporary Data” which contains Data Sync Tool results
Removed “ClassyHealthCheck” scheduled job since results are now viewable in Classy Logs
Simplified configuration section of Control Panel by removing deprecated settings
Standardized naming convention for API Requests created by the Data Sync Tool
Various changes to keep in line with Salesforce security best practices

Squashed bugs

Fixed an issue where the Data Sync Tool was syncing transactions with status “Canceled”
Fixed an issue where the Data Sync Tool could be manually started multiple times before completion which produced inaccurate results
Fixed an issue where “Donor Selected Classy Mode” field on Opportunities was intermittently incorrect for recurring donations
Fixed an issue where Data Sync Tool completion email was sent even if an API credential was inactive
Fixed an issue where transaction data was not syncing for Honoree name fields that exceeded max length
Fixed a typo on the Enhanced Contact Matching setting help text

November 16, 2018

Version 6.47 - Sherman Heights

Summary

Classy for Salesforce version 6.47 contains a number of minor bug fixes for transaction and recurring profile linking as well as other improvements.

What's new

Changed the "Campaign" field label on Opportunity to "Classy Campaign" to help distinguish it from other Campaign lookup fields
Created a "Classy Member Name" field on Opportunity which contains the full name captured by the "Your Information" fields on donation pages

What's fixed

Fixed an issue where some registration data failed to sync if similar names were used for Ticketed Event registrations
Fixed a rare issue where Classy Recurring Donors were not related to Opportunities during times of high transaction volume
Fixed a rare issue where Opportunities would associate with the wrong Classy Recurring Donor record if a "0" was stored for its Classy Recurring ID
Fixed an issue where transaction Classy API Requests with recurring donors contained an "Invalid decimal" error (NGO Connect organizations only)

November 5, 2018

Version 6.461 - Sherman Heights

What's fixed

Fixed an issue where data related to Opportunities for ticketed events was not created

August 10, 2018

Version 6.46 - Sherman Heights

Summary

Classy for Salesforce version 6.46 contains a number of minor bug fixes and improvements. "Attendee" Opportunity Contact Roles will now be created for all attendees besides the donor which still receive a "Donor" Opportunity Contact Role. Additionally, in order to improve support for NPSP rollup fields based on Opportunity Contact Roles, we've added logic to ensure a "Donor" Opportunity Contact Role is created even if a donor donates to their own Fundraising Page and/or Team Page.

What's new

Added an "Attendee" Opportunity Contact Role to ticket purchase transaction
"Donor" Opportunity Contact Role will now always populate for the donor if they donate to a Team they are captain of or Fundraising page they are the fundraiser for
Improved Classy Recurring Donor rollup to accommodate for Opportunities with a null "Amount" field
Removed requirement for "Recurring ID" field on Classy Recurring Donor records

What's fixed

Fixed an issue where "Host Total" field was not filling in on Opportunity records
Fixed an Issue where "Default Opportunity Contact Role" setting was also on Account & Contact section of Classy Control Panel
Removed deprecated "TEST Email" field from Contact

July 27, 2018

Version 6.45 - Sherman Heights

Summary

Classy for Salesforce version 6.45 contains support for the Opt-In checkbox on Classy transactions. This selection will be captured and stored in the field "Classy Opt-In" on Contacts and will update for any Contacts with Classy Member IDs that share the same email address. Additionally, this update includes several bug fixes for the Classy Recurring Donor object.

What's new

Added support for the "Classy Opt-In" checkbox on Classy transactions
"Classy Opt-In" field will be updated whenever a new transaction is created
"Classy Opt-In" field will be updated whenever a Supporter is updated in Classy

What's fixed

Fixed an issue where Classy Recurring Donors that were missing a Contact were not updated if a new successful transactions was created
Fixed an issue where Classy Recurring Donor records with no successful transactions were being created
Fixed an issue where updates to non-ID and non-lookup fields could not be made to Classy Recurring Donor records
Fixed the spelling of "Event Type" field label from "Entity Type" on Classy Source Codes

July 11, 2018

Version 6.44 - Sherman Heights

Summary

Classy for Salesforce version 6.44 contains several bug fixes and the groundwork for Source Codes. Expect to see more details on this new functionality in future releases of Classy for Salesforce and the Classy Fundraising Suite.

What's new

Added an object called “Classy Source Codes” in order to support future functionality
Prevented an email about Classy Recurring Donor rollups when run by scheduled job

What's fixed

Fixed an issue where the State field on Contacts is sometimes not filling in when State/Country picklists are enabled
Fixed an issue where the NPSP Extension menu was showing even if the NPSP Extension is not installed

June 21, 2018

Version 6.431 - Sherman Heights

What's fixed

Fixed an issue where "Attendee" Campaign Member setting was not enabled by default

June 13, 2018

Version 6.43 - Sherman Heights

Summary

Classy for Salesforce version 6.43 provides a number of bug fixes related to registrations as well as a new nightly job to recalculate Classy Recurring Donor rollups. Additionally, we’ve added a Campaign Member status called “Attendee” so that it’s easier to determine who’s attending an event in Salesforce.

What's new

Added fields on Campaign, Opportunity, and Classy Recurring Donor to support New Classy Mode/li>
Added “Attendee” Campaign Member status on Campaign object
Added a nightly rollup job to improve reliability of rollups on Classy Recurring Donor object
Added a button in Classy Control Panel tools section to refresh Classy Recurring Donor rollups

What's fixed

Fixed an issue where the “Contact” and “Classy Registration” fields on Classy Custom Answer records were not always filled in
Fixed an issue where some registration data was not created for Campaigns with a custom Campaign Member status
Fixed an issue where the Data Sync tool would fail on a newly refreshed Sandbox

May 1, 2018

Version 6.421 - Sherman Heights

What's fixed

Fixed an issue where the Parent Campaign field was overwritten on Campaigns

April 9, 2018

Version 6.43 - Sherman Heights

Summary

Classy for Salesforce version 6.42 provides a number of bug fixes related to Registration with Fundraising, Events, and the Data Sync tool.

What's fixed

Fixed an issue where the Data Sync tool would stall if a recurring profile had text in its name
Fixed an issue where Campaign Members were not created and the Contact field was not filled on fundraising page and team Campaign records for Registration with Fundraising campaigns
Fixed an issue where Campaign Members were not created for a Registration with Fundraising campaign when same registrant info is used for multiple attendees
Fixed an issues where Contact Address fields would overwrite after registering for an event
Reduced the number of duplicate Contacts when registering as a Team Captain
Added logs to provide more registration details

March 8, 2018

Version 6.41 - Sherman Heights

Summary

Classy for Salesforce version 6.41 provides a number of bug fixes related to Registration with Fundraising campaign types as well as improvements to the Data Sync tool.

What's fixed

Fixed an issue where the Data Sync tool was not including the full "Days to compare" of the Data Health tool
Fixed an issue where offline donations were syncing even if "Salesforce Sync" option was disabled
Fixed an issue where Campaign Members were not created for fundraising page contacts coming from a Registration with Fundraising campaign
Fixed an issue where the "Transaction Type" field on Opportunity filled in with "Donation" instead of "Registration" intermittently
Fixed an issue where the "Classy Opt-in" field on Contacts was being cleared on update

February 19, 2018

Version 6.4 - Sherman Heights

Summary

Classy for Salesforce 6.4 is a deeper integration than ever before, with a number of significant improvements based on providing valuable insight into how the integration is performing, tools to reconcile data, and a brand new interface for managing integration settings and configuration. This new version also fully supports the upcoming revamp of Classy Events. In addition, substantial improvements have been made to our data processing in order to drastically reduce the amount of duplicate contacts.

What's new

Classy Control Panel

The Classy Control Panel is an entirely new aspect of our integration. Our intention is to make the Control Panel your home page for everything about the Classy for Salesforce integration. We’ll be making a lot of updates to the Control Panel going forward, so stay tuned! For this initial launch, we’ve added some links to useful articles about the integration. In the future, look forward to release notes, known issues updates, and more!

Data Reconciliation Tool
- This was first released generally in August, but we’ve updated to a brand new UI to make this tool easier to use than ever!
Health Metrics
- Looking for insight into the health of your integration? This is the place for you! Find details on how successfully your donations are syncing to Salesforce as well as additional information on other areas of the integration, including:
  - The status of the last five sync events
  - Scheduled jobs status, with a simple button to schedule any non-running jobs
  - Classy API credentials
  - Type of contact matching used by the integration
Custom Settings & Configuration UI
- Previously settings were managed partly in Classy and partly through custom settings in Salesforce, which are buried in menus and have a difficult UI as well. We’ve built an entirely new UI to help you navigate and manage your settings from a single place within your integration

Support for New Classy Events

Get ready for the new Classy Events suite, coming soon! This release of Classy for Salesforce fully supports Classy Events, so update now to ensure you’ll have full support for Events once it’s released. With this update, all event data, including transactions, tickets, and attendees will sync in real-time to Salesforce, just like our other new event types.

Additionally, the integration now supports creating Contacts for event attendees, a long time feature request! (Please note attendees must fill in first/last name & email in order for a Contact to be created).

What's fixed

Reduced the number of duplicates created for new donors
Reduced the number of duplicates created during registration & ticketed events
Resolved an issue where recurring plans with a status of “Failing” weren’t updating correctly in Salesforce
Designations created or updated through the API are now processing correctly in Salesforce
For NPSP users, event & registration attendees that are new Contacts are now correctly associated to a Household Account
Corrected an issue where the Designation lookup field was overwritten and set as blank for Campaigns when a Recurring Donor was updated

Important changes

New tab for “Classy Control Panel” to let you experience the new suite of tools around data validation, reconciliation, health metrics, and configuration

December 13, 2017

Version 6.33 - Shelter Island

Summary

Classy for Salesforce version 6.33 contains a number of improvements, but the key update involves some new functionality around matched donations and company offline donations. It's been a highly requested feature to prevent matched donations from syncing to Salesforce, so our team has added a new custom setting to stop matched donations from creating Opportunities. However, if you still want to see those matched donations in Salesforce, we've updated our integration to add Account fields for both matched donations and offline donations made to companies. To ensure we don't create duplicate Accounts, we recommend that the organizations you specify in Classy already have Accounts we can match to in Salesforce. See below for more details on these and more exciting features!

What's new

Improvements to matched gifts and company offline donations
- A new custom setting called "Prevent creation of matched gifts". While disabled by default, when this setting is enabled matched gifts will NOT be created as Opportunities
- When Opportunities are created from either matched gifts or company offline donations, the integration will attempt to exactly match to an existing Account. The integration will not create Accounts, and will only look for exact matches, so we recommend ensuring that Accounts exist in Salesforce prior to applying those organizations to company offline donations matched donations
In conjunction with the release of Classy Passport, added new currency specific fields on the Classy Recurring Donor object:
- Raw Donation Amount: The amount selected by the donor on the donation form
- Raw Currency Code: The currency selected by the donor on the donation form
- Charged Currency Code: The type of currency sent by Classy to the payment processor
- Charged Donation Amount: The amount of the donation sent by Classy to the payment processor
Added new fields to separate first/last names for dedications, including the dedication contact and honoree. This should make email template creation utilizing separate names substantially easier
- Dedication First Name: The value of Recipient's First Name on the dedication form in Classy
- Dedication Last Name: The value of Recipient's Last Name on the dedication form in Classy
- Honoree First Name: The value of Honoree's First Name on the dedication form in Classy
- Honoree Last Name: The value of Honoree's First Name on the dedication form in Classy
Added a new field called "Campaign Path" on Campaign. This field is used to populate the Campaign URL field with the updated URL structure used by Classy's new fundraising suite

What's fixed

Fixed several inconsistent fields affecting offline donations to new campaigns. This includes ensuring that the "Offline Donation" field is checked, the "Payment Gateway" field is set to "Offline", and the "Payment Method" is set correctly based on the value selected when creating the offline donation
Resolved an issue where Custom Field Mapping was not working properly when mapping between fields on the same object (for instance, from one Opportunity field to another). NOTE: this bug did not affect mapping from a Custom Answer to a different object, such as a Contact"
Corrected an issue in the Data Sync tool which was not resetting the retrieval dates for the nightly job properly. Now if the Data Sync tool is manually set to verify data for an arbitrary date in the past, when the daily reconciliation job runs it will ensure that the data is being retrieved for the previous day

Important changes

The "Campaign URL" field now has a new URL structure for new fundraising page campaigns, including the parent campaign, fundraising pages, and fundraising teams. Previously this field always used the legacy URL structure for all campaigns; for new campaigns, legacy URLs would automatically redirect to new URLs

November 1, 2017

Version 6.32 - Shelter Island

Summary

Classy for Salesforce version 6.32 focuses on improved capabilities for organizations with multiple Classy accounts connected to a single Salesforce instance and adding detailed history for recurring donation plans.

What's new

Improved the system for automatically fetching missing data for organizations that have multiple Classy accounts connected to a single Salesforce instance
Added a new field to indicate if a donor marked their donation as Gift Aid Eligible on the Classy donation form (see Important Changes below for additional details)
Recurring Donation History object is now populating for all recurring donations created in new fundraising suite campaigns and for all recurring donations processed by Classy Pay

What's fixed

Fixed an issue affecting clients using NPSP where an update to a Classy transaction would overwrite the NPSP formatted Opportunity name with the default Classy formatted Opportunity name. All Opportunities for NPSP users should always adhere to NPSP Opportunity naming conventions. Requires NPSP Extension package
Resolved an issue where registrations purchases with Classy mode/fee on top selected by the donor were not including the additional fee in the Amount field on Opportunities
Corrected an issue in the Data Sync tool which was not resetting the retrieval dates for the nightly job properly. Now if the Data Sync tool is manually set to verify data for an arbitrary date in the past, when the daily reconciliation job runs it will ensure that the data is being retrieved for the previous day

Important changes

New custom field Is Gift Aid Eligible on Opportunity. This checkbox field will be set to true if a donor indicated that their donation is eligible for Gift Aid in the United Kingdom
NOTE: This features requires an organization to enable the Gift Aid setting in their Classy account

October 4, 2017

Version 6.31 - Shelter Island

Summary

Classy for Salesforce version 6.31 introduces a couple of new features as well as a number of critical bug fixes intended to keep your integration operating smooth as silk.

What's new

Added a new custom field named Donor Selected Classy Mode on Opportunity to indicate if "Classy Mode" (the option on a donation form where the user elects to cover Classy's fees) was selected when donating
New "Classy Passport Transactions" report listing all international donations as part of Classy Passport. This is located in the Classy Reports folder in the Reports tab

What's fixed

Fixed an issue where updating attendee information via Classy Reports did not update the attendee in Salesforce
Resolved an issue with the data reconciliation tool where campaign names using special characters could cause an error during processing which prevented the record from being created
Corrected an issue where multiple attendees on a single registration have an incorrect Amount attributed to the purchase
Fixed an issue with invalid state names preventing Contact records from being created in organizations with the state/country picklist feature enabled

Important changes

New custom field Donor Selected Classy Mode on Opportunity

August 31, 2017

Version 6.3 - Shelter Island

Summary

Classy for Salesforce version 6.3 introduces a highly requested feature, a tool that compares and resyncs missing records. This tool can support data verification for different object types, and is configured to run nightly to try and reprocess any missing data.

This release also supports data related to promo codes for new Classy Events (including Registration with Fundraising).

What's new

New custom UI to manage the data reconciliation tool
Set start and end dates to import data for specific time periods
The tool is configured to run nightly after upgrading to 6.3. After installation the tool will verify and attempt to reprocess any missing data each night
By default the tool will sync data related to the following resources/objects
- Transactions (non-offline)
- Campaigns
- Custom Questions
- Fundraising Pages
- Fundraising Teams
- Custom Answers
- Recurring Donations
- Tickets/Registrations
- Contacts (Supporters)
Supports the new promo code system for Classy Events, including Registration with Fundraising
- Populates the promo code used and the adjustment amount representing the discount applied via the promo code on Opportunities
New SDK method to allow updating recurring donation attributes such as amount, the day of the month the charge occurs, and setting an end date. Note that this does not allow updating credit card or billing information

What's fixed

Fixed an issue for orgs using NPSP where the Account on an Opportunity would not be populated
Fixed an issue where the following fields were not being populated on recurring donations: Contact, Designation, Installment Period, Billing Address Line 2, Payment Gateway Name, and Gateway Subscription ID
Fixed an issue where the "Payment Gateway Transaction ID" was not populated on Opportunities (this field has been re-labeled as "Processor ID"; see Important Changes below for more details)
Fixed an issue where the Account Name field was not always populated for classic Classy campaigns for organizations using NPSP
Fixed an issue where the billing address 2 field was not getting added to the address data for Contacts
Fixed an issue where custom questions did not sync when a Campaign was duplicated in Classy
Fixed an issue where the honoree and recipient fields were switched for dedications made through new fundraising suite campaigns
Fixed an issue where Team Captains were not being created as Campaign Members on the parent Campaign
Fixed an issue where field mapping was not always correctly applied for donation custom answers for recurring donations made to legacy campaigns

Important changes

The "Payment Gateway Transaction ID" custom field on Opportunity has been re-labeled as "Processor ID" to reflect the name of this field in Classy Reporting
On Opportunities, the "Discount Code" and "Discount Total" have been renamed as "Promo Code" and "Adjustment Amount", respectively, in order to match the field names in Classy reporting. This will not impact existing or new data

July 12, 2017

Version 6.23 - Shelter Island

Summary

This release had a heavy focus on resolving some lingering issues, in particular populating dedication fields for new campaign types and respecting certain custom settings, such as object Record Type defaults.

What's new

New fields on Opportunity to support future payment options
- Payment Account Type
- Payment Account Number
- Payment Institution

What's fixed

Dedication fields now populating on Opportunities
Fixed an issue with custom field mapping settings not working properly for new campaign type data, including transactions
Fixed an issue where default Record Type settings for Contact, Campaigns, and Opportunities were not being respected for transactions through new campaign types
Billing Address 2 field now populating on Opportunities
Payment Gateway Name now populating on Opportunities
Fixed an issue where the "Always use Classy parent Campaign as the Primary Campaign on an Opportunity" custom setting was not being respected

Important changes

Field Name: Opportunity > Payment Gateway Name
- Old Value: "Classy Pay"
- New Value: Actual payment processor used (e.g., "Braintree", "WePay", "Authorize.net")

May 17, 2017

Version 6.204 - Shelter Island

Summary

Version 6.2 includes support for the new Registration with Fundraising campaign type. All data related to a registration will be sent to Salesforce in real time, including all registrations, donations made along with the registration purchase, contacts, fundraising pages, fundraising teams, and custom answers. In addition, this version supports multi-currency Salesforce orgs.

What's new

Support for FRS Registration with Fundraising campaign data, including transactions, registrations, and custom questions
Support for multi-currency Salesforce orgs
Matching Sponsor gifts for FRS Campaigns now sync without creating or matching to a Contact or Account
New Related Entity object, to allow for easy reporting on attendees
New fields on Opportunity:
- Classy Business ID
- Parent Transaction ID
- Is a Matched Gift?

What's fixed

Custom Answers for Classy Pay transactions will now sync
Transaction Type field on Transactions is now populated properly
Custom answers will now populate for transactions & fundraising pages
Deleted campaigns, fundraising pages, and teams will now properly update the Campaign Status & Active fields
Saving addresses with orgs that have state/country picklists enabled
Matching Sponsor gifts no longer relate to incorrect Contact and Account

Important changes

Names are no longer automatically re-formatted to only uppercase the first letter of the first/last name for FRS campaign types. Names will now mirror the casing/formatting in Classy
Transaction Type field on Opportunity will now be set to "Registration" for registrations and "Donation" for donations on donation pages or additional donations for registrations
For registrations where a single email is used to create multiple registrations, individual Contacts will be created based on the First/Last/Email when Enhanced Contact Matching is enabled
Deleted campaigns, fundraising pages, and teams will now properly update the Campaign Status & Active fields
Classy Lookup fields are no longer editable in order to reduce issues related to these fields containing differing values from Classy

April 13, 2017

Version 6.125 - East Village

Completely revamped UI for Classy Custom Field Mapping
Better support for mapping to Date/DateTime and Currency fields
Bug fixes related to incorrect Amounts for ticket purchases that incorporate a portion of the event fee
New custom field: Classy Order Total on Opportunity

February 23, 2017

Version 6.0 - East Village

Fixed issue with incorrect Date of Last Donation on the Contact record
Updated enhanced contact matching to allow matching for non-string fields
Bug fixes related to matching on multiple email fields
Improved query to search for existing Classy jobs in Post Install script

2016

Version name: Mission Bay

5.201

Completely revamped UI for Classy Custom Field Mapping
Better support for mapping to Date/DateTime and Currency fields
Bug fixes related to incorrect Amounts for ticket purchases that incorporate a portion of the event fee
New custom field: Classy Order Total on Opportunity

Version name: Bird Rock

5.111

Fixed issue with incorrect Date of Last Donation on the Contact record
Updated enhanced contact matching to allow matching for non-string fields
Bug fixes related to matching on multiple email fields
Improved query to search for existing Classy jobs in Post Install script

5.1

Contacts were not being created in orgs with Enhanced Contact Matching enabled but no saved criteria
Moves Contact field updates from a third party integration (i.e., our NGOC integration) are now being applied AFTER Accounts are created; this was causing issues in NGOC, which expects an AccountId value on Contacts

5.0

Improved Account/Contact creation process
Improved Campaign Member Roles (if a fundraiser joins a team, their role will update to Team Member, and if they leave, will return to Fundraiser role)

2015

Version name: Logan Heights

4.312

Adds a new custom field called Organization ID to Opportunity; this helps organizations that have multiple Classy accounts connected to a single Salesforce instance.

4.3

Added additional fields to roll up reporting on the Contact record, including new fields for number & total amount of recurring donations, number of fundraising pages created, and new fields for number & amount of donations for the past X days, where X can be set within Classy custom settings.

Version name: Bay Park

4.24

Adds the option to set custom Record Types for all Account, Contact, and Campaign records created by Classy

4.23

Updates Team and Fundraising Campaigns so that donors to a page are added as Campaign Members; previously donors were only add to the parent Campaign
Added a setting to force the Primary Campaign on an Opportunity to always be the parent Campaign, instead of a team or fundraising Campaign

4.22

Added new custom fields on Opportunity: Discount Code, Discount Total, and Browser Info

Version name: Del Mar

4.2

Added custom fields for Billing First/Last Name on Opportunity
Removal of deprecated objects/fields

Version name: Talmadge

4.193

Added support for Fundraiser Alias field on the Campaign object. This field is used for fundraising pages that want to display a name other than their contact name.

4.192

Contact Mailing Field Update

We enountered an issue where the Mailing Address field on Contact records was not getting added properly. This new packages provides a resolution for this issue.

4.19

New Transaction Type Field

In this version we've added a new field for Transaction Type which indicates whether a purchase is a donation, ticket, or registration. The API name of this field "Stayclassy__Transaction_Type__c".

4.16

NGO Connect Release

Our newest version of the NGO Connect package is now avialable.

Custom Layouts

Instead of changing your organization's record layouts when you install our package, you now have the option to use our record types at your leisure, when it makes sense for your organization. They will no longer appear as the default.

Custom Field Mapping

With our custom field mapping tool you can push your Classy data to a custom or standard field of your choice on the same object. Field mapping is available for Custom Answers, Opportunities, Campaigns and Contacts.

Custom PriceBook Attribution

If your organization uses a unique PriceBook, you can contact us and we can add that setting to our database.

Version name: Presidio

3.5

Fixed bugs caused by field level security from previous version number

3.33

Integration now allows a Classy top-level Campaign to be a child of an existing Campaign

3.3

Update the logo and app labeling to reflect our new name, Classy!
Added a new custom object, Recurring History, to capture detailed events related to a recurring donor profile, including payments, failures, and cancellations.

2014

Version name: Tourmaline

3.26

Added Team Captain & Team Members (Fundraisers) as Campaign Members under the Team Campaign Record
New Attendees Report for Event & Registration Campaign Types
Added support for Birthdate field

3.2

Added Custom Objects for Classy Questions and Classy Answers. These objects are hold response to data from custom fields asked via StayClassy fundraiser, ticket, registration, and donation forms. Please add related lists for these objects to your Campaign, Contact, and Opportunity page layouts to show the data for your StayClassy custom fields.

Version name: Pacific Beach

3.23

Added support for State/Country picklists for Contacts
Bug fixes for matching existing Contact records
Security fixes for App Exchange submission
Added Custom Objects for Classy Questions and Classy Answers. These objects are hold response to data from custom fields asked via StayClassy fundraiser, ticket, registration, and donation forms. Please add related lists for these objects to your Campaign, Contact, and Opportunity page layouts to show the data for your StayClassy custom fields.

Version name: Golden Hill

3.14

Added Tickets/Registrations as Products
Tickets/Registrations displayed as Opportunity Line Items
Added Fundraiser as an Opportunity Contact Role
Added settings to prevent overwriting existing Contact fields

Version name: North Park

3.0

Fundraisers/Teams are now Campaigns; moved all code logic to Apex; better support for bulk uploads.

2013

Version name: Imperial Beach

2.1

We released a new Classy Dashboard with pre-defined reports for a high-level overview of StayClassy Activity.

Version name: Coronoado

2.0

The StayClassy app now utilizes the standard Campaign and Opportunity objects in place of the Classy Campaign and Classy Transactions custom objects. This allows for deeper integration with SalesForce processes as well as third-party apps that utilize the standard objects.

Version name: Spring 2013

1.0

The initial release of the StayClassy package.