Released December 13, 2017
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!
- 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.
- 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 where the “Campaign URL” field for donation page campaigns pointed to the campaign landing page, which doesn’t exist for donation page-only campaigns.
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.
- 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.