The Raiser's Edge Sphere Connector Guide
8/13/2013 Sphere 9.4.3 The Raiser's Edge Sphere Connector US
©2013 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any
means, electronic, or mechanical, including photocopying, recording, storage in an information retrieval system, or otherwise, without the prior written permission of Blackbaud, Inc.
The information in this manual has been carefully checked and is believed to be accurate. Blackbaud, Inc., assumes no
responsibility for any inaccuracies, errors, or omissions in this manual. In no event will Blackbaud, Inc., be liable for direct,
indirect, special, incidental, or consequential damages resulting from any defect or omission in this manual, even if advised
of the possibility of damages.
In the interest of continuing product development, Blackbaud, Inc., reserves the right to make improvements in this manual
and the products it describes at any time, without notice or obligation.
All Blackbaud product names appearing herein are trademarks or registered trademarks of Blackbaud, Inc.
All other products and company names mentioned herein are trademarks of their respective holder.
RE sync- 2013
Contents
SPHERE AND THE RAISER'S EDGE SYNCHRONIZATION OVERVIEW
Configuring Synchronization between Sphere and The Raiser's Edge Overview
Sending Metadat from The Raiser's Edge to Sphere
Mapping Synchronization Fields for Sphere and The Raiser's Edge
Contact Updates Field Group Mapping for Sphere and The Raiser's Edge
Gifts Field Group Mapping for Sphere and The Raiser's Edge
Events Field Group Mapping for Sphere and The Raiser's Edge
Activating Sphere for Synchronization with The Raiser's Edge Overview
Selecting the Synchronization Mode for Sphere and The Raiser's Edge
Synchronization Field Groups for Sphere and The Raiser's Edge
Importing Records to Sphere from The Raiser's Edge Overview
Importing Contact Updates to Sphere from The Raiser's Edge
Record Identity Field Flowchart for Sphere Imports
Importing Gifts to Sphere from The Raiser's Edge
Gift Allocation Import Flowchart for Sphere and The Raiser's Edge
Importing Contact Lists to Sphere from the Raiser's Edge
Exporting Records from Sphere to The Raiser's Edge Overview
Exporting Contact Updates from Sphere to The Raiser's Edge
Record Identity Field Flowchart for Sphere Exports
Exporting Gifts from Sphere to The Raiser's Edge
Exporting Advocacy Data from Sphere to The Raiser's Edge
Exporting Events from Sphere to The Raiser's Edge
Understanding Synchronization Field Groups
Contact Update Synchronization between Sphere and The Raiser's Edge
Gift Synchronization between Sphere and The Raiser's Edge
Contact List Synchronization between Sphere and The Raiser's Edge
Advocacy Synchronization between Sphere and The Raiser's Edge
Event Synchronization between Sphere and The Raiser's Edge
Standard and Non-Standard Synchronization Fields for Sphere and The Raiser's Edge
Synchronization Field Tables for Sphere and The Raiser's Edge
Custom Fields and Attributes in Sphere and The Raiser's Edge
Auto-create Fields Option in Sphere
Special Character Synchronization for Sphere and The Raiser's Edge
Sphere and The Raiser's Edge Synchronization Batches Overview
Scheduling and Processing Sphere and The Raiser's Edge Synchronization Batches
CONFIGURE SPHERE FOR SYNCHRONIZATION WITH THE RAISER'S EDGE
Install The Raiser's Edge/Sphere synchronization components
Register The Raiser's Edge with Sphere for Synchronization
1
2
3
3
4
4
6
6
6
7
11
12
12
13
14
16
16
17
18
19
20
21
21
21
21
22
22
23
23
24
30
31
31
31
33
35
36
36
Send metadata from The Raiser's Edge to Sphere
Schedule synchronization between Sphere and The Raiser's Edge
36
40
chapter 1
Sphere and The Raiser's
Edge
Synchronization Overvie
w
Configuring Synchronization between Sphere and The Raiser's Edge Overview
2
Importing Records to Sphere from The Raiser's Edge Overview
11
Exporting Records from Sphere to The Raiser's Edge Overview
16
Understanding Synchronization Field Groups
21
Standard and Non-Standard Synchronization Fields for Sphere and The Raiser's Edge
23
Sphere and The Raiser's Edge Synchronization Batches Overview
31
Synchronization between Sphere and The Raiser’s Edge is the process of transferring information between the
Sphere CRM database and The Raiser’s Edge. Synchronization reduces the time your organization spends
administering each database, and eliminates the need to manually prepare data when you want to perform
updates.
You can synchronize a variety of field groups using built-in import and export functionalities. Data you import
into Sphere is added directly into your database, and data you export from Sphere is sent to The Raiser’s Edge so
you can review and commit the data.
Before you begin synchronizing, configure each database with the assistance of a Sphere representative and then
complete an initial synchronization batch for records created on or after a date you specify. Schedule additional
synchronization batches through The Raiser’s Edge to synchronize records you update or create after the last
synchronization using the same configuration as the first batch.
When you want to change how your synchronization is set up, you can change the:
l
Metadata from The Raiser’s Edge to Sphere
l
Mapping for the synchronization fields and attributes you use
2 CHAPTER 1
l
Synchronization mode you use
l
Field groups you use
After you complete synchronizations, Sphere displays the results in the Most Recent and History tabs from the
Connector Sync menu. The Most Recent tab shows details for import results, as well as import and export batch
status. Use the History tab when you want to view historical synchronization results.
Configuring Synchronization between Sphere
and The Raiser's Edge Overview
Before you attempt to synchronize data between Sphere and The Raiser’s Edge, you must prepare each
database to enable communication.
A Sphere representative will help you with the first synchronization:
l
l
l
During the setup, you will be instructed to install applications for The Raiser’s Edge that enable it to search
for and send information (metadata) to Sphere. The upgrade will provide user interfaces so that you can
define, schedule, and commit synchronization batch information. Additionally, you enter your Sphere
login and password through The Raiser’s Edge to register The Raiser’s Edge account with Sphere for the
synchronization service, and also send metadata to Sphere. Registering informs the Sphere database that
you are authorizing an exchange of data, and sending metadata provides Sphere with the list of fields you
use in The Raiser’s Edge. For more information about using the applications you install, see the Blackbaud
Sphere & The Raiser’s Edge Integration Guide from Blackbaud.
After Sphere receives the metadata, map Sphere fields to The Raisers Edge fields, and then activate
Sphere. Activation involves selecting the synchronization mode, field groups, and related categories you
will use.
Setup is complete after you schedule the first synchronization batch and transfer records created on or
after a date you specify.
Note: Configure the initial synchronization with the assistance of a Sphere representative to minimize the risk of
entering incorrect data into Sphere and The Raiser’s Edge.
For subsequent synchronizations:
l
You can change the configuration by installing newer versions of the synchronization components, or
updating the metadata, mapping, synchronization mode, or field groups you use. Keep configuration
alterations to a minimum by using auto-create fields so that new attributes from The Raiser’s Edge are
automatically created and mapped in Sphere.
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
3
Sending Metadat from The Raiser's Edge to Sphere
Sending metadata from The Raiser’s Edge to Sphere is the process of providing Sphere with the list of active fields
you use in The Raiser’s Edge. For information regarding how to send metadata from The Raiser’s Edge, see the
Blackbaud Sphere & The Raiser’s Edge Integration Guide from Blackbaud.
The information you send to Sphere includes standard fields and fields you can map. Sphere populates and
displays the fields that require mapping in the Mapping tab from the Connector Sync menu. You only need to
send metadata the first time you configure synchronization between Sphere and The Raiser’s Edge, and as you
make configuration changes in The Raiser’s Edge (for example, when you create new constituent and gift
attributes or make changes to the funds, appeals, packages, or campaigns you use).
Mapping Synchronization Fields for Sphere and The Raiser's
Edge
When you map synchronization fields you are matching fields that are non-standard in Sphere and The Raiser’s
Edge. Mapping causes data that you send to Sphere to automatically import into the Sphere CRM database, and
data you send to The Raiser’s Edge to be ready for you to commit into The Raiser’s Edge database.
Map and save selected fields through Sphere after you provide a list of The Raiser’s Edge fields to Sphere by
sending metadata, and after you create or identify these same fields in Sphere. For example, if you want to
synchronize the Favorite Color attribute from The Raiser’s Edge, you must have a similar field in Sphere (such as,
Preferred Color) so that you can match the field to the attribute. You do not need to map standard fields since
they automatically correspond in Sphere and The Raiser’s Edge. The synchronization field tables list the standard
fields.
When to Map Fields
Map fields the first time you synchronize Sphere with The Raiser’s Edge, and when you update the fields you use.
If you add custom constituent or gift attributes to The Raiser’s Edge after the initial synchronization, use the
auto-create fields option to create and map the new fields in Sphere instead of manually matching them.
You can complete mapping when the:
l
l
l
l
Phone, E-mail, and address type fields you use in Sphere have more than one logical match in The Raiser’s
Edge (for example, Alternate Phone in Sphere matches with Seasonal Phone in The Raiser’s Edge, but you
might use The Raiser’s Edge Business field to store the same data)
Fields or attributes are custom in either database (for example, favorite color, pet owner, or meal
preference)
Fields are ones you use for gift allocations in either database (for example, funds, appeals, or source
codes)
Sphere event names and registration types do not exactly match event names, units, and unit prices in
The Raiser’s Edge
Mapping is available for three field groups—Contact Updates, Gifts, and Events.
Note: The Contacts Lists field group imports constituent query results from The Raiser’s Edge and does not
require mapping in Sphere. For information regarding query selection, see the Blackbaud Sphere & The Raiser’s
Edge Integration Guide from Blackbaud.
4 CHAPTER 1
Contact Updates Field Group Mapping for Sphere and The Raiser's Edge
The Contact Updates field group includes the following mapping categories: Phone/E-mail, Address, and Custom
Profile Fields. If you do not map fields in these categories, only the standard fields will synchronize.
Note: All the fields for Thon Summary Fields are standard, so you do not need to map them.
l
For Phone/E-mail, match the phone and E-mail fields in Sphere to The Raiser’s Edge fields if the fields you
use in Sphere do not match the Raiser’s Edge fields.
Note: If you use custom fields or attributes for phone numbers, E-mail addresses, or address data you
can map the fields to attributes via Custom Profile Fields.
l
l
For Addresses, match Sphere’s Primary Address fields to The Raiser’s Edge address fields for data you will
export, and other Sphere address fields to The Raiser’s Edge address fields for data you will import. Sphere
imports all of the constituent address types you use in The Raiser’s Edge.
For Custom Profile Fields, match Sphere custom profile fields and segment categories to The Raiser’s Edge
constituent attributes, when the field and the attribute are the same data type. For example, a currency
field in Sphere must map to a currency attribute in The Raiser’s Edge. Sphere segment categories only map
to constituent attributes that use a table data type because the segment category name corresponds to
the attribute table name, and the categories’ segments correspond to the attribute values. You can match
Sphere text fields with The Raiser’s Edge fuzzy date attributes only for data you export. Attributes that use
the constituent name data type are not available for mapping.
Use the table below to understand how custom profile fields and segments match with constituent attributes:
Sphere
The Raiser's Edge
Match if...
Segment category
Constituent attribute category
You map the fields via Sphere’s
Mapping tab
Segment
Constituent attribute value
The Sphere segment and The
Raiser’s Edge constituent attribute value match exactly
Field Name
Constituent attribute category
You map the fields via Sphere’s
Mapping tab
Field Value
Constituent attribute value
The Sphere field and constituent
attribute values match exactly.*
*Values do not need to match
exactly if the field type is text.
Gifts Field Group Mapping for Sphere and The Raiser's Edge
The Gifts field group includes the following mapping categories: Custom Event Fields, Funds, Campaigns,
Appeals, Source Codes, and Memorial/Tribute Fields. If you do not map fields in these categories, only the
standard fields will synchronize.
Note: You must use the Sphere gift allocation rules below when you map the fields for gift imports, otherwise
the gifts will not import. For information regarding gifts you export, see the Blackbaud Sphere & The Raiser’s
Edge Integration Guide from Blackbaud.
S PHE RE
l
l
l
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
5
For Custom Event Fields, match Sphere custom event fields with gift attributes in The Raiser’s Edge (for
example, gift code) when they are the same data type (for example, date, text, and so on). Custom event
fields can relate to gifts or events.
For Funds, match funds and designations in Sphere with the funds you use in The Raiser’s Edge. Sphere
combines donor designations with the designations’ funds so that if you use Sphere designations you can
map them to funds in The Raiser’s Edge. If you do not use donor designations, Sphere funds use
Undesignated as the default. If you do not match Sphere fund and donor designation combinations with
funds in The Raiser’s Edge, Sphere selects your account’s default fund and donor designation combination
when you import donations. You can change the donations’ fund and designation information within
Sphere after you complete imports if you do not want to use the defaults.
For Campaigns, match the campaigns you use in Sphere with campaigns in The Raiser’s Edge. If you map
a campaign, you must also map the campaign’s funds when importing donations into Sphere.
Note: Important: Gift exports from Sphere do not include campaign information. Instead, The Raiser’s Edge
uses the default campaign for the gift’s fund.
l
l
l
For Appeals, match the appeals or source codes you use in Sphere with appeals in The Raiser’s Edge. If
you map an appeal, you must also map the appeal’s campaign when importing donations into Sphere.
For Source Codes, match Sphere source codes to packages in The Raiser’s Edge after you select an appeal
from The Raiser’s Edge. If the appeal mapping you select via the Appeals tab does not match the appeals
that correspond to the source codes and packages you map, Sphere uses the source code’s appeal—not
the mapped appeal—to allocate gifts you import.
For Memorial/Tribute Fields, match the custom fields you use for memorial/tribute information in custom
Friends Asking Friends Web sites, or Single Step Donation forms to memorial/tribute fields in The Raiser’s
Edge if your organization uses the optional RE:Tribute mode in The Raiser’s Edge. The Sphere custom
fields you select must be a drop down data type.
Note: Memorial/ tribute fields in Thon, Gift Entry and Memorial and Tribute forms are standard and do not
require mapping.
Note: Sphere enables you to map one custom field for each memorial/tribute field in The Raiser’s Edge. If you
use more than one Sphere initiative to collect custom memorial/tribute information, use the same custom
profile or custom event fields in each so that you can export all of the information.
Source Codes, Appeals, and Packages
In Sphere, you can use source codes to track gifts you receive via Web site banners and content, or from E-mail,
eNewsletter, and direct mail mailings. You can use source codes as independent tracking methods, or as part of
your Campaign Manager gift allocation structure when you create mailings through appeals.
Since you can use Sphere source codes for multiple purposes, Sphere and The Raiser’s Edge enable you to map
them to appeals or packages in The Raiser’s Edge. Typically, you map source codes to appeals when you do not
use Sphere’s Campaign Manager and you create source codes in Sphere to match appeals in The Raiser’s Edge.
Map source codes to packages if the source codes you use in Sphere match the ways in which you group appeal
solicitations in The Raiser’s Edge. For example, you might use a package in The Raiser’s Edge to group appeal
mailings that use a new logo, and map the package to a Sphere source code you use for E-mail mailings featuring
the new logo. Sphere source codes you map to packages can be independent, or related to Campaign Manager
appeals. Packages in The Raiser's Edge always use appeals.
6 CHAPTER 1
Events Field Group Mapping for Sphere and The Raiser's Edge
The Events field group includes the following mapping categories: Events and Registration Types. If you export
event information without mapping events, Sphere exports the standard and custom event fields so that you
can apply them to a matching event in The Raiser’s Edge. Map custom event fields via the Custom Event Fields
tab.
l
For Events, match a Sphere event with an event from The Raiser’s Edge if the event names you use in each
database do not match exactly.
Note: If you do not map events, an event that uses the same name and registration types (called units
and unit prices in The Raiser’s Edge) must already exist in The Raiser’s Edge.
l
For Registration Types, match Sphere registration types to units when the Sphere registration fee is
greater than or equal to a unit’s price in The Raiser’s Edge. Sphere populates the registration types and
units available for mapping after you select mapped events.
Activating Sphere for Synchronization with The Raiser's Edge
Overview
When you activate Sphere for synchronization with The Raiser’s Edge, you are selecting the synchronization
mode, field groups, and related categories you will use. You must activate Sphere before scheduling
synchronization batches through The Raiser’s Edge.
Selecting the Synchronization Mode for Sphere and The Raiser's Edge
When you select the synchronization mode, you are specifying whether to import or export data between
Sphere and The Raiser’s Edge. Selecting a field group within a synchronization mode column activates Sphere for
synchronization and enables the standard fields to transfer.
The following synchronization modes are available:
l
l
Sphere -> Connector – allows you to export information from Sphere to The Raiser’s Edge. Select field
groups in this column if you want to update The Raiser’s Edge with data you obtain online through
Sphere.
Sphere <- Connector – allows you to import information from The Raiser’s Edge to Sphere. Select field
groups in this column if you want to use The Raiser’s Edge information for Sphere online marketing.
Selecting the same field groups in each synchronization mode column ensures that data in Sphere and The
Raiser’s Edge is current and accurate. If you only synchronize data in one direction, Sphere and The Raiser’s Edge
will not use record identity fields to link the records. Instead, Sphere and The Raiser’s Edge will create new
records when you update and synchronize existing records. The new records will require you to use the
duplication removal tools available in the destination database.
The figure below shows the synchronization mode options that display on the Connector Sync Admin page:
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
7
Note: Synchronization is available in both directions for Contact Updates and Gifts. Events and Advocacy only
export from Sphere to The Raiser’s Edge, and Contact Lists only import to Sphere from The Raiser’s Edge.
Synchronization Field Groups for Sphere and The Raiser's Edge
Sphere and The Raiser’s Edge can synchronize data for contact update, gift, event, advocacy, and contact list
field groups. When you select a field group within a synchronization mode column, you activate Sphere for
synchronization and enable the standard fields to transfer.
After you select the field groups, choose categories related to Contact Updates, Gifts, and Events if you have
already mapped non-standard fields. For example, standard gift synchronizations include information about the
amount of money you receive and the date you receive it, and can also include appeal information if you select it
as a field category.
Note: If you map custom gift fields via the Custom Event Fields mapping tab, you do not need to select them as
a related category. The fields automatically synchronize when you select Gifts as a synchronization mode field
group.
Sphere shows the field groups and related categories you import on the Import Batch Detail page after you
complete a synchronization batch. In The Raiser’s Edge, field groups correspond to the following links on the
Sphere page:
l
Constituent Updates activate Profile Updates
l
Gifts activate Donations
l
Events activate Event Registrations
l
Advocacy activates Advocacy Actions
l
Contact Lists activate Queried Contact Lists
Data you export from Sphere pertaining to a supporter who does not have a constituent record in The Raiser’s
Edge automatically activates the Sign-up Requests link on The Raiser’s Edge Sphere page. We recommend that
you commit Sign-up Requests before you commit other records to create records for new constituents.
8 CHAPTER 1
Note: Registrations and donations you synchronize from Sphere to The Raiser’s Edge do not activate the Signup Requests link. Instead, you create constituent records when you process transactions. If you synchronize
other registrant and donor related activities, such as profile updates, before you create the constituent records,
the Connector activates the link.
The figures below shows the field groups and related categories that display on the Connector Sync Admin page:
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
9
Contact Updates
When you enter or update a supporter (or constituent in The Raiser’s Edge) in either database, you can import or
export the following types of contact information:
l
Standard profile fields (for example, first name, last name, gender, birth date, and so on)
l
Phone and E-mail fields (for example, home phone number, E-mail address, and so on)
l
Address fields (for example, city, state, zip code, and so on)
l
Custom contact information (for example, favorite hobbies, pet name, or other custom field or attribute
you create)
For Sphere supporters who participate in Thon events, you can export Thon summary fields (for example, team
Name, team Goal, last login, and so on).
10 CHAPTER 1
If you use the Contact Updates field group, you automatically synchronize standard profile fields. The other
profile field categories are optional.
Gifts
When you enter or update a donation in either database, you can import or export the following types of
donation information:
l
Standard gift fields (for example, gift amount, received date, and so on)
l
Custom gift fields (for example, gift code, gift summary, and so on)
l
Fund name (for example, disaster fund, street clean-up fund, and so on)
l
Appeal name (for example, year-end appeal, hurricane appeal, and so on)
l
Source code or package name (for example, spring direct mailing, promotional brochure, and so on)
You can import campaign information from the Raiser’s Edge to Sphere (for example, annual campaign, disaster
relief campaign, and so on); however gift exports from Sphere do not include campaign details. Instead, The
Raiser’s Edge uses the default campaign for the gift’s fund.
For memorial or tribute donations you enter or update in Sphere, you can export the following if your
organization uses the optional RE:Tribute mode in The Raiser’s Edge:
l
l
Standard memorial/tribute fields from Thon, Gift Entry, and Memorial and Tribute forms (for example,
tribute type, name of honoree, and so on)
Custom profile or event fields from custom Friends Asking Friends Web sites or Single Step Donation
forms (for example, cancer survivor name, in loving memory of, and so on)
If you use the Gifts field group, you automatically synchronize standard and custom donation fields. The other
gift field categories are optional, but you should consider the gift allocation rules you use in each database before
enabling fund, campaign, appeal, and source code synchronizations. If you enable Campaigns/Appeals without
also selecting Fund, Sphere will use the campaign's default fund when you import gifts.
When you use Gifts, you also synchronize Contact Updates—even if you do not select it as a field group—
because the information enables you to match donations with supporters and constituents.
Events
When you enter or update a registration in Sphere, you can export the following types of information to The
Raiser’s Edge:
l
Standard event fields (event name, registration type, registration quantity, and registration fee)
l
Custom event fields (for example, meal preference, start time, and so on)
If you use the Events field group, you automatically export standard and custom event fields which you can
apply to an existing event in The Raiser’s Edge.
When the events you use in each database do not match exactly, you can map events and registration types
from Sphere to events and units in The Raiser’s Edge. Selecting the Events field group automatically synchronizes
the event mapping selections you make, and the Event Registration Types category synchronizes registration
type and unit selections.
When you use Events, you also synchronize Contact Updates—even if you do not select it as a field group—
because the information enables you to match registrations with constituents.
Advocacy
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
11
When a supporter takes action online by sending an action message or signing a petition, you can export the
following types of information to The Raiser’s Edge:
l
l
Action item data (delivery method, recipient name, action item name, action topic classification)
Supporter advocacy data (date and time the action was taken, message identification number, last action
taken, lifetime number of actions taken, number of actions forwarded, and supporter district data )
Note: Sphere calculates the number of action items the supporter forwarded when the action item appears as a
trackable link in a bulk e-mail message.
Contact Lists
You can import constituent query results from The Raiser’s Edge and save them as contact lists in Sphere. Sphere
contact lists are accessible via Contacts > Database Management > Contact Lists, and do not require mapping.
For information regarding query selection, see the Blackbaud Sphere & The Raiser’s Edge Integration Guide
from Blackbaud.
Importing Records to Sphere from The Raiser's
Edge Overview
Import data to Sphere from The Raiser’s Edge by initiating a synchronization batch through The Raiser’s Edge.
Depending on the field groups you select, records you update or create in The Raiser’s Edge after the last
synchronization are sent in an encrypted format to Sphere. You can import Contact Updates, Gifts, and Contact
Lists.
Note: Events do not import into Sphere. Use Sphere’s online tools to obtain registration information and then
export the information to The Raiser’s Edge.
During the import process, Sphere matches fields according to your account’s unique mapping structure and
compares constituent and gift attributes from The Raiser’s Edge with existing Sphere custom fields. Sphere
processes imports using the following criteria:
l
l
l
l
If the file includes new attributes, Sphere creates new custom fields for the attributes when you select the
auto-create fields option in the mapping configuration. Otherwise, Sphere flags the attributes that were
not part of the mapping with an error code and displays them in the batch results.
If the file contains donations, Sphere verifies they use funds, appeals, source codes, and campaigns in the
same manner as your account’s gift allocation structure. Otherwise, Sphere flags the donation records
with an error code and displays them in the batch results. The gift allocation import flowchart shows how
Sphere handles donations you import.
If the file contains Contact Updates records, Sphere determines whether The Raiser’s Edge or Sphere
record is more current, imports the latest from The Raiser’s Edge, and displays an error message for the
records which are more current in Sphere.
If the file contains constituent query results, Sphere processes the batch’s contact data and then flags
query result records that are not part of the CRM database with an error code. Sphere displays The
Raiser’s Edge identification numbers for each failed record in the batch results.
After the import is complete, Sphere stores the data and makes the following available from the Most Recent and
History tabs in the Connector Sync menu:
12 CHAPTER 1
l
Total number of successful imports
l
Total number of failed imports
l
Total number of rejected imports because the Sphere record is more current
Importing Contact Updates to Sphere from The Raiser's Edge
Contact Updates import profile data for individuals and organizations, and always synchronize standard profile
fields (for example, First Name, Last Name, and so on). The standard profile fields include record identity fields
that match existing records and identify new ones. The record identity field flowchart for Sphere imports shows
how Sphere handles new and existing constituents you import from The Raiser’s Edge.
You can also import phone/E-mail, address, and constituent attribute fields. If you choose to import address
information, Sphere imports all of the constituent record address types you use in The Raiser’s Edge.
Note: When a constituent record in The Raiser's Edge contains more than one address with the same address
type, Sphere creates supporter records for each address during the import. You can merge the records after the
synchronization.
Record Identity Field Flowchart for Sphere Imports
Use the chart below to learn how Sphere handles new and existing constituents you import from The Raiser’s
Edge.
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
13
Importing Gifts to Sphere from The Raiser's Edge
Gifts import donation information and always synchronize standard gift fields (for example, Amount Received,
and Payment Type). When you import Gifts, you also synchronize Contact Updates—even if you do not select it
as a field group—because the information enables you to match donations with supporters.
14 CHAPTER 1
Note: During the synchronization, payment methods entered for The Raiser’s Edge Pay method field always
appear as cash gifts in Sphere’s Payment Type field.
Donation information includes record identity fields from The Raiser’s Edge which help Sphere match existing
records and identify new ones. Sphere uses the record identity fields to match donors from The Raiser’s Edge
with existing supporter records when the Sphere Alternate ID is the same as The Raiser’s Edge Constituent
Import ID. Sphere uses profile details from Contact Updates to determine if the contact information you define
for your account’s automatic duplication removal logic is the same. If there are differences, Sphere creates a new
supporter record.
Sphere processes new donations using fund and donor designation combinations. Sphere combines donor
designations with the designations’ funds so that if you use Sphere designations you can match them with funds
in The Raiser’s Edge before importing gifts. For example, if you have a Street Clean-up Fund in Sphere with a
donor designation available for Main Street and a Main Street Clean-up Fund in The Raiser’s Edge, you can map
Sphere’s Street Clean-up Fund/Main Street combination to The Raiser’s Edge Main Street Clean-up Fund. If you
do not use donor designations, Sphere funds use Undesignated as the default.
If you do not match Sphere fund and donor designation combinations with funds in The Raiser’s Edge, Sphere
selects your account’s default fund and donor designation combination when you import donations. You can
change the donations’ fund and designation information within Sphere after you complete imports if you do not
want to use the defaults.
When you use gift allocation rules in Sphere for funds, appeals, and campaigns, the donations you import must
use the same allocations. For example, if you import a gift and map it to the Street Clean-up Fund, and you
associate the Street Clean-up Fund with the Disaster Relief Campaign in Sphere, then you must map the
campaign information before you import the gift and the fund. The gift allocation import flowchart shows how
Sphere handles donations you import.
If you import gifts and map them to source codes, and use source codes as part of your gift allocation hierarchy,
Sphere allocates the gifts to the source codes and their related appeals. Source codes you create via Control >
Code Library > Source Codes do not use appeals, so if you use them in your mapping Sphere only allocates gift
imports to the source code.
Gift Allocation Import Flowchart for Sphere and The Raiser's
Edge
Use the chart below to learn how Sphere allocates gifts you import from The Raiser’s Edge.
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
15
16 CHAPTER 1
Importing Contact Lists to Sphere from the Raiser's Edge
Contact Lists import results from constituent queries that you select via The Raiser’s Edge Sphere page before
scheduling synchronization batches. Sphere imports up to the first 100,000 records for each selected query when
result records also exist in Sphere, and saves them as contact lists that use the same names as The Raiser’s Edge
constituent queries. If you use a dynamic query for multiple synchronizations, Sphere imports all of the results—
not only the records that contain updates—to the same contact list for each batch.
Note: If a contact list exists in Sphere with the same name as a constituent query from The Raiser’s Edge before
you import results, Sphere appends The Raiser’s Edge records to the existing list.
After the import is complete, the contact list is available via Contacts > Database Management > Contacts Lists.
The total number of failed records becomes available from the Most Recent and History tabs, accessible via the
Connector Sync menu.
Exporting Records from Sphere to The Raiser's
Edge Overview
Export data from Sphere to The Raiser’s Edge by initiating a synchronization batch through The Raiser’s Edge.
Depending on the field groups you select, records you update or create in Sphere after the last synchronization
are sent in an encrypted format to The Raiser’s Edge. You can export Contact Update, Gift, Event or Advocacy
records.
Note: If you merge or delete records in Sphere and subsequently remove a record that also exists in The
Raiser’s Edge, you must manually make the same changes to the corresponding records in The Raiser’s Edge.
When you remove attributes or addresses in The Raiser’s Edge that also exist in Sphere, subsequent changes
you make to the information in Sphere will not export to The Raiser’s Edge because Sphere ignores attributes if
they are no longer in The Raiser's Edge.
Sphere records the date you send each batch and makes the date available from the Most Recent tab in the
Connector Sync menu.
The Raiser’s Edge receives the synchronization records and creates links (see figure below) in The Raiser’s Edge
Sphere page for each Sphere export field group. Sphere fields are already mapped to fields in The Raiser’s Edge so
you can quickly commit records.
Data you export from Sphere pertaining to a supporter who does not have a constituent record in The Raiser’s
Edge automatically activates the Sign-up Requests link on The Raiser’s Edge Sphere page. We recommend that
you commit Sign-up Requests before you commit other records to create records for new constituents.
Note: Registrations and donations you synchronize from Sphere to The Raiser’s Edge do not activate the Signup Requests link. Instead, you create constituent records when you process transactions. If you synchronize
other registrant and donor related activities, such as profile updates, before you create the constituent records,
the Connector activates the link.
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
17
Exporting Contact Updates from Sphere to The Raiser's Edge
Contact Updates export individual and organization supporter profile data and always synchronize standard
profile fields (for example, First Name, Last Name, and so on). The standard profile fields include record identity
fields that match existing records and identify new ones. The record identity field flowchart for Sphere exports
shows how The Raiser’s Edge handles new and existing supporters you export from Sphere.
Note: Sphere does not export information about primary contacts in organization records.
Note: Updates to constituent profile data are not available for batch processing in The Raiser’s Edge.
You can also export phone/E-mail, address, custom profile, and Thon summary fields. If you export address
information, Sphere only exports addresses that have the Primary Address flag. In The Raiser’s Edge Sphere
page, you can use the Address Saving option to commit addresses to new constituent records as preferred, or
update existing records using the address type from Sphere (see figure below). When you update existing
records, the default selection is to create a new address—not overwrite the preferred address.
For Thon summary field exports, The Raiser’s Edge adds the information from Sphere to corresponding fields in
the constituent record Attributes tab and displays the Thon name and creation date for each in the Comments
column. Sphere exports Thon summary data when the field has a value, and The Raiser’s Edge only displays the
fields Sphere exports. For example, Sphere does not export team fields that do not apply to individual
registrants. When supporters participate in multiple events, Sphere exports summary fields for each Thon. When
a team member’s summary information changes, Sphere updates the corresponding summary data for each
person in the team and exports all the summary data fields—including fields that have a zero value—during the
next synchronization.
Note: Sphere does not export Last Login when a team or registrant is entered via Thon’s Bookkeeping section.
Note: Sphere does not update or export the Thon summary fields Number of Facebook Updates and Number
of Tweets until values exist for the fields.
When you select Contact Updates, any change that creates an activity in a supporter record will cause the record
to synchronize. For example, when a supporter logs into their Thon participant headquarters Sphere creates a
login activity, saves the change as an update, and exports the supporter record during the next synchronization.
18 CHAPTER 1
Record Identity Field Flowchart for Sphere Exports
Use the chart below to learn how The Raiser’s Edge handles new and existing supporters you export from Sphere.
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
19
Exporting Gifts from Sphere to The Raiser's Edge
Gifts export donation information, and always synchronize standard gift fields (for example, Amount Received,
and Payment Type). When you export Gifts, you also synchronize Contact Updates—even if you do not select it
as a field group—because the information enables you to match donations with constituents.
Note: Sphere only exports initiative gifts when the initiative is active.
Donation information can include custom event, fund, campaign, appeal, source code, and memorial/tribute
fields if you map them. The following explain how some gifts appear in The Raiser’s Edge Sphere page:
20 CHAPTER 1
l
l
l
l
If you export donations that use donor designations, Sphere exports the donor designation and the
corresponding fund. For example, if you have a Street Clean-up Fund in Sphere, and you allow donors to
designate Main Street or Cherry Street when they make a donation, Sphere exports the donation for Main
Street as Street Clean-Up Fund/Main Street which you can then match to a fund you use in The Raiser’s
Edge.
If you export donations that use source codes and appeals, and you map the source codes to packages
that do not use the same appeals as the ones you select via the Appeals tab, The Raiser’s Edge uses the
package’s appeal—not the mapped appeal—to allocate the gift.
If you export memorial/tribute fields, The Raiser’s Edge automatically creates a link between the person
who made the donation (the acknowledgee) and the person to whom the tribute was made (the honoree
or tributee) when there is one unique corresponding constituent record or no existing record. When there
is more than one constituent record that matches the acknowledgee information, The Raiser’s Edge
provides the option to manually identify the correct constituent record, or to create another record if
necessary.
If you export donations made in support of event participants and you select the Participant Supporter
option under the Admin tab on the Connector Sync page, the synchronization marks the event participant
as a solicitor in The Raiser's Edge. To synchronize recurring participant gifts, you must use The Raiser's
Edge version 7.92 or higher.
Note: Gift exports from Sphere do not include campaign information. Instead, The Raiser's Edge uses the
default campaign for the gift's fund.
Note: Memorial/tribute fields you export from Sphere are only available in The Raiser’s Edge Sphere page if
your organization uses the optional RE:Tribute mode in The Raiser’s Edge.
Exporting Advocacy Data from Sphere to The Raiser's Edge
dvocacy exports advocacy activity data from Sphere to The Raiser’s Edge, and always uses standard action fields.
Standard advocacy data includes information from supporter activity records (such as the date the action is
taken and the total number of actions taken by the supporter), and information from action items (such as the
message recipients and the action item names).
Note: Sphere only exports advocacy message data after all delivery attempts are complete.
When you select Advocacy Actions from The Raiser’s Edge Sphere page, all of the details about an action item
appear in a row with the constituent’s name – including each of the message recipients. In the constituent’s
record, the action item details appear for each message recipient under the Actions tab. For example, if a
constituent takes action using a Sphere Action Center and three people receive the message, the Actions tab in
The Raiser’s Edge constituent record displays three actions.
In The Raiser’s Edge Action screen, most fields from Sphere appear under the General tab. However, the
supporter’s district information appears under the Attributes tab. Summary action information including the last
action taken, the total number of actions taken by the supporter, and the number of action items the supporter
forwarded, appear under the Attributes tab in the constituent record.
Note: Sphere calculates the number of action items the supporter forwarded when the action item appears as a
trackable link in a bulk e-mail message.
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
21
Exporting Events from Sphere to The Raiser's Edge
Events export registration and sponsorship data, and always include the event’s standard (event name,
registration type, registration quantity, and registration fee) and custom event (for example, start time) fields.
When you export Events, you also synchronize Contact Updates—even if you do not select it as a field group—
because the information enables you to match registrations with constituents in The Raiser’s Edge. If you want
to synchronize donations made during registrations, you must select Gifts.
Tip: In The Raiser's Edge, we recommend you process registrations before donations so you can link donations
made in support of registrants to the registrant constituent records.
For transactions that contain multiple registrations, donations, tee shirt, or other additional fees, Sphere exports
one gift record and includes the number of registrations or other selections made during the purchase. If you use
a plugin version higher than 4.1.1.5, Sphere also updates the receipt amount value in The Raiser's Edge to include
the additional fees.
Exporting event information without mapping events or registration types requires you to have an existing event
with the same name and matching units in The Raiser’s Edge.
For information regarding how to match registrations with constituents, see Event Registrations in the
Blackbaud Sphere & The Raiser’s Edge Integration Guide from Blackbaud.
Understanding Synchronization Field Groups
When you synchronize data between Sphere and The Raiser's Edge, you can transfer contact, gift, contact list,
advocacy, and event data.
Contact Update Synchronization between Sphere and The
Raiser's Edge
Sphere and The Raiser’s Edge synchronize profile information which enables you to import and export data
about supporters (or constituents in The Raiser’s Edge) when you receive new information about these
supporters.
You can synchronize profiles so that Sphere and The Raiser’s Edge have the latest information for use in
marketing. For example, you can synchronize address updates you receive from Sphere online event
registrations and use the updates for direct mail marketing through The Raiser’s Edge. Conversely, you can
synchronize E-mail address updates you receive from The Raiser’s Edge offline marketing efforts and use the
updates for Sphere’s E-mail campaigns.
Gift Synchronization between Sphere and The Raiser's Edge
Sphere and The Raiser’s Edge synchronize donation information which enables you to import and export data
about payments you receive.
Use Sphere to process large numbers of donations online, and The Raiser’s Edge to enter offline donations and
donations you solicit periodically, and then synchronize the payments so that each database has the latest
information for use in marketing. For example, you can synchronize payments you receive from Sphere online
22 CHAPTER 1
donation forms and use the information when you solicit major gifts through The Raiser’s Edge. Conversely, you
can synchronize payments you receive from The Raiser’s Edge offline fundraising efforts and use the information
when you target donors for marketing through Sphere
If you want to associate donors with recurring donations or pledges, structure custom information in each
database to help you easily identify the donors when you synchronize their profiles.
Tip:
l
l
In The Raiser’s Edge, you can create constituent attributes and map them to custom profile fields in
Sphere. For example, if you are using Sphere to solicit donations and you want to exclude donors who
have already made major pledges, create a pledge attribute in The Raiser’s Edge and map it to a custom
profile field for pledges in Sphere. This way when you import constituent information to Sphere from The
Raiser’s Edge you can identify and suppress the donors with major pledges from your marketing efforts.
In Sphere, you can separate online forms for recurring gifts and pledges from forms for single one time
donations, and then use Sphere’s auto-segment option to place donors into payments groups. For
example, if you are using The Raiser’s Edge to thank donors for ongoing contributions, create a form and a
segment for recurring gifts in Sphere and map it to a constituent attribute in The Raiser’s Edge. This way
when you export supporter information from Sphere to The Raiser’s Edge you can identify and thank the
donors with recurring gifts.
Note: Sphere and The Raiser’s Edge do not synchronize pledge and recurring gift information unless you use
custom fields and attributes.
Contact List Synchronization between Sphere and The Raiser's
Edge
Sphere and The Raiser’s Edge synchronize constituent query results from The Raiser’s Edge as contact lists in
Sphere, enabling you to create complex searches in The Raiser’s Edge and target specific segments of your
database for online marketing through Sphere. For example, you can use a constituent query from The Raiser’s
Edge to identify previous donors who are currently inactive, export the results to Sphere, and then use the
contact list for an E-mail campaign receiver base.
Advocacy Synchronization between Sphere and The Raiser's
Edge
Sphere and The Raiser’s Edge synchronize advocacy data which enables you to export advocacy information
after supporters take action.
Note: Sphere only exports advocacy message data after all delivery attempts are complete.
Use Sphere for online advocacy efforts and then synchronize the information so that The Raiser’s Edge has the
latest constituent information. For example, you can synchronize supporter advocacy activities from Sphere
Action Centers and use the information when you target constituents for gifts through The Raiser’s Edge.
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
23
Event Synchronization between Sphere and The Raiser's Edge
Sphere and The Raiser’s Edge synchronize event information which enables you to export registration details
when you receive the data.
Use Sphere to process online event registrations and then synchronize the information so that the Raiser’s Edge
has the latest constituent information. For example, you can synchronize registrations you receive from Sphere
online Thon events and use the information when you target constituents for gifts through The Raiser’s Edge.
Standard and Non-Standard Synchronization
Fields for Sphere and The Raiser's Edge
Sphere and The Raiser’s Edge synchronize standard and non-standard fields.
Standard Fields
Fields that automatically match in Sphere and The Raiser’s Edge are standard. For example, the First Name field
in The Raiser’s Edge corresponds to the First Name field in Sphere. When you send metadata from The Raiser’s
Edge, you do not need to create or map the standard fields in Sphere. The synchronization field tables list all the
standard fields.
Standard fields include the following types of data:
l
l
Record identifiers – Match existing records and identify new records. The record identity field flowcharts
for Sphere imports and exports show how Sphere and The Raiser’s Edge handle new and existing
supporters you synchronize. The Record Identity Fields table displays the standard mapping. Changing
the values for any of the record identifiers will result in duplicate records.
Profile fields – Match profile information that has the same meaning in each database. For example, First
Name contains first name values in each database.
Note: Although phone, E-mail, and address type fields have direct matches in each database, the fields are nonstandard when the fields you use in Sphere do not match The Raiser’s Edge fields. For example, Alternate
Phone in Sphere matches with Seasonal Phone in The Raiser’s Edge, but you might use The Raiser’s Edge
Business field to store the same data.
l
l
l
Constituencies and constituent codes – Match characteristics you identify about a group of supporters.
When you configure a default constituent code via Options in The Raiser’s Edge Sphere page, Sphere
imports the code for each batch record, and auto-creates a corresponding constituency if one does not
already exist in Sphere. Sphere exports a supporter's primary constituency the first time you synchronize
the contact record with The Raiser's Edge. For information about how to create constituent codes in The
Raiser’s Edge for Sphere constituencies you export, see The Raiser’s Edge Configuration and Security
Guide from Blackbaud.
Gift fields – Match donation information that has the same meaning in each database. For example, Gift
Received Date in Sphere and Gift Date in The Raiser’s Edge contain the same values in each database
Event fields – Match Sphere event names, registration types, and registration fees with events and units in
The Raiser’s Edge when event information is exactly the same in each database.
Note: When event information does not match exactly in Sphere and The Raiser’s Edge, the event fields are
non-standard and require mapping.
24 CHAPTER 1
Non-standard Fields and Attributes
Fields and attributes that do not automatically match in Sphere and The Raiser’s Edge are non-standard. For
example, if you create a Pet Name attribute in The Raiser’s Edge, you must create or identify a corresponding
custom field in Sphere and then indicate you want to match it with the Pet Name attribute. After you send
metadata from The Raiser’s Edge, you need to map non-standard fields unless you use the auto-create fields
option.
Non-standard fields include the following:
l
l
Phone, E-mail and address type fields you use in Sphere that do not match The Raiser’s Edge fields (for
example, Alternate Phone in Sphere matches with Seasonal Phone in The Raiser’s Edge, but you might
use The Raiser’s Edge Business field to store the same data).
Custom fields you use for supporters, gifts, and events in either database (for example, favorite color, or
pet owner)
l
Fields you use for gift allocations in either database (for example, funds, appeals, or campaigns)
l
Custom fields you use in Sphere custom Friends Asking Friends Web sites or Single Step Donation forms
l
Event fields when event information does not match exactly in each database (for example, event name,
or registration types)
Synchronization Field Tables for Sphere and The Raiser's Edge
Use the tables below to learn how Sphere and The Raiser’s Edge synchronize fields that are available in each
database.
Although the Phone/E-mail tables indicate the fields have direct matches in each database, you can map them if
the fields you use in Sphere do not match The Raiser’s Edge fields. For example, Alternate Phone in Sphere
matches with Seasonal Phone in The Raiser’s Edge, but you might use The Raiser’s Edge Business field to store
the same data.
Contact Update Fields
Individual and Organization Record Identity Fields
Sphere Field
The Raiser’s Edge Field
The Raiser’s Edge to
Sphere
Sphere to The Raiser’s
Edge
Supporter ID
Sphere Constituent Identifier
No
Yes
Alternate ID
Constituent Import ID
Yes
No
RE System Identifier
Internal System Record ID
and Constituent ID
Yes
Yes
The Raiser's Edge to
Sphere
Sphere to the Raiser's
Edge
Individual Phone/E-mail Fields
Sphere Field
The Raiser's Edge Field
Home Phone
Home
Yes
Yes
Business Phone
Business
Yes
Yes
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
Fax
Fax
Yes
Yes
Cell Phone
Cell Phone
Yes
Yes
Pager
Beeper
Yes
Yes
Alternate Phone
Seasonal Phone
Yes
Yes
Email
Email
Yes
Yes
Email 2
Email
Yes
Yes
The Raiser's Edge to
Sphere
Sphere to the Raiser's
Edge
Organization Phone Fields
Sphere Field
The Raiser's Edge Field
Business Phone
Business
Yes
Yes
Fax
Fax
Yes
Yes
The Raiser's Edge to
Sphere
Sphere to the Raiser's
Edge
Individual and Organization Address Fields
Sphere Field
The Raiser's Edge Field
Address Line 1 and
Line 2
Address Lines
Yes
Yes
City
City (US, UK, Can)/Suburb
(Aus)
Yes
Yes
Country
Country
Yes
Yes
County
County
Yes
Yes
Primary Address
Set this address to the
preferred address checkbox
Yes
Yes
Mail to this Address
Send mail to this address
checkbox
Yes
No
State
State
Yes
Yes
ZIP Code
ZIP (US); Post code (NZ);
Postcode (UK, Aus);
Postal Code (Can)
Yes
Yes
Sphere Field
The Raiser's Edge Field
The Raiser's Edge to
Sphere
Sphere to the Raiser's
Edge
Last Name
Last Name
Yes
Yes
Individual Profile Fields
25
26 CHAPTER 1
First Name
First Name
Yes
Yes
Middle Initial
Middle Name
Yes
Yes
Title
Titles
Yes
Yes
Suffix
Suffixes
Yes
Yes
Suffix 1
Suffixes
Yes
Yes
Nickname
Nickname
Yes
Yes
Maiden Name
Maiden Name
Yes
No
Gender
Gender
Yes
Yes
Birth Date
Birth date
Yes
Yes
Deceased
Deceased
Yes
Yes
Marital Status
Marital status
Yes
Yes
Active Flag
Is inactive
Yes
Yes
Do not email
Requests no email
Yes
Yes
Ethnicity
Ethnicity
Yes
Yes
Religion
Religion
Yes
Yes
Greeting 1
Primary salutation
Yes
No
Greeting 2
Primary addressee
Yes
No
The Raiser's Edge to
Sphere
Sphere to the Raiser's
Edge
Organization Profile Fields
Sphere Field
The Raiser's Edge Field
Company Name
Org Name
Yes
Yes
Active Flag
Is inactive
Yes
Yes
Do not email
Requests no email
Yes
Yes
Thon Summary Fields
Sphere Field
The Raiser's Edge Field
The Raiser's Edge to
Sphere
Sphere to The Raiser's
Edge
Amount Raised to
Date
Sphere Thon Raised
No
Yes
Personal Fundraising
Goal
Sphere Thon Goal
No
Yes
Team Name*
Sphere Thon Team Name
No
Yes
Team Fundraising
Goal*
Sphere Thon Team Goal
No
Yes
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
Amount Raised by
Team*
Sphere Thon Team
Raised
No
Yes
Team Member Goal*
Sphere Thon Member
Goal
No
Yes
Number of Team Members*
Sphere Thon Number of
Members
No
Yes
Team Captain
Sphere Thon is Team Captain
No
Yes
# of Emails
Sphere Thon Number of
Emails
No
Yes
Last Login^
Sphere Thon Last Login
No
Yes
Number of Tweets
Sphere Thon Number of
Tweets
No
Yes
Number of Facebook
Updates
Sphere Thon Number of
Facebook Updates
No
Yes
27
*Sphere updates the field for every team member when there is a change to one person’s summary information.
^Sphere does not export Last Login when the registration is entered via Thon's Bookkeeping section.
Gifts
Gift Fields
Sphere Field
The Raiser's Edge Field
The Raiser's Edge to
Sphere
Sphere to The Raiser's
Edge
Fund/Designation
Fund*
Yes
Yes
Amount Received
Amount
Yes
Yes
Received Date
Gift date
Yes
Yes
Payment Type**
Pay method
Yes
Yes
Payment Type: Cash
Pay method: Cash
No
Yes
Payment Type: Check
(Individual Supporter)
Pay method: Personal
Check
No
Yes
Payment Type: Check
(Organizational Supporter)
Pay method: Business
Check
No
Yes
Check Date
Check date
No
Yes
Check Number
Check no
No
Yes
Payment Type: Direct
Debit
Pay method: Other***
No
Yes
Payment Type: ACH
Pay method: Other***
No
Yes
28 CHAPTER 1
Payment Type: Charge
(Offline)
Pay method: Credit
No
Yes
Payment Type: Credit
Pay method: Credit
No
Yes
Credit Card Type
Card type
No
Yes
Payment Type: Paypal
Pay method: Other***
No
Yes
Receipt #^
SphereReceiptNumber
No
Yes
*The Connector links gifts from Sphere to the fund’s default campaign in The Raiser’s Edge.
**Payment methods entered for The Raiser’s Edge Pay method field always appear as cash gifts in Sphere’s
Payment Type field.
***The Sphere payment method displays in The Raiser’s Edge Ref no./date field when the value if Pay method is
Other.
^Sphere exports Receipt # if PDF receipts are enabled for the account.
Thon Dedication Memorial Tribute Fields
Sphere Field
The Raiser's Edge Field
The Raiser's Edge to
Sphere
Sphere to The Raiser's
Edge
Recognition From
Last name, First name
No
Yes
Recognition Type
Tribute Type
No
Yes
Recognition To
Honor/Memorial
No
Yes
Gift Entry Memorial Tribute Fields
Sphere Field
The Raiser's Edge Field
The Raiser's Edge to
Sphere
Sphere to The Raiser's
Edge
Honoree
Honor/Memorial
No
Yes
Honoree Type
Tribute Type
No
Yes
Supporter First Name,
Last Name*
Constituent
No
Yes
Supporter Phone*
Phone/Email/Links
No
Yes
Supporter Email*
Phone/Email/Links
No
Yes
Supporter Address
Line 1*
Address lines
No
Yes
Supporter City*
City
No
Yes
Supporter State*
State
No
Yes
Supporter ZIP*
ZIP
No
Yes
*The Raiser’s Edge uses supporter and acknowledgee fields to match donors with existing constituent records—
not to create new constituents.
Memorial and Tribute Form Fields
S PHE RE
Sphere Field
The Raiser's Edge Field
Honoree First Name,
Last Name
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
The Raiser's Edge to
Sphere
Sphere to The Raiser's
Edge
Honor/Memorial
No
Yes
Tribute Type
Tribute Type
No
Yes
Acknowledgee First
Name, Last Name*
Name
No
Yes
Acknowledgee Phone*
Phone/Email/Links
No
Yes
Acknowledgee Email*
Phone/Email/Links
No
Yes
Acknowledgee Address
Line 1*
Street Address
No
Yes
Acknowledgee City*
City
No
Yes
Acknowledgee State*
State
No
Yes
Acknowledgee ZIP*
ZIP
No
Yes
29
*The Raiser’s Edge uses supporter and acknowledgee fields to match donors with existing constituent records—
not to create new constituents.
Events
Event Fields
Sphere Field
The Raiser's Edge Field
The Raiser's Edge to
Sphere
Sphere to the
Raiser's Edge
Event Name
Name
No
Yes
Registration Type
Unit
No
Yes
Registration Fee
Gift Amount
No
Yes
Registration Quantity
No. Units
No
Yes
Advocacy
Advocacy Action Item Fields
Sphere Field
The Raiser's Edge Field
The Raiser's Edge to
Sphere
Sphere to the Raiser's
Edge
Delivery Method
Delivery Method
No
Yes
Target
Recipient Name
No
Yes
Action Item Name
Alert Title
No
Yes
Action Topic Classification
Issue
No
Yes
Action Type
Action type
No
Yes
Advocacy Supporter Record Fields
30 CHAPTER 1
Sphere Field
The Raiser's Edge Field
The Raiser's Edge to
Sphere
Sphere to the
Raiser's Edge
Action/Message ID*
Message ID
No
Yes
Date Created
Action date, Start time,
and End time
No
Yes
District
District
No
Yes
Most Recent
Last Action Taken**
No
Yes
Total
# of total actions taken (lifetime)**
No
Yes
Number of action items
forwarded***
# of action items forwarded
No
Yes
* The field does not display in Sphere.
**The field appears in The Raiser’s Edge under the constituent record’s Attributes tab.
***Sphere calculates the number of action items the supporter forwarded when the action item appears as a
trackable link in a bulk e-mail message.
Custom Fields and Attributes in Sphere and The Raiser's Edge
In Sphere, you can store custom data about a supporter or a gift in the following ways:
l
l
l
l
Custom profile field – information about a supporter (for example, favorite color, pet name, and so on)
Custom event field – information about a gift or an initiative not relevant to the supporter’s profile (for
example, gift code, meal preference, start time, and so on)
Segment category or segment – a group of supporters who identify themselves as having certain
characteristics. Examples of segment categories are dog enthusiast or environmentalist, and examples of
segments are individual dog breeds or environmental concerns.
Constituency – a group of supporters you identify as having certain characteristics (for example, past
event registrant, volunteer, and so on)
Supporters in The Raiser’s Edge are called constituents; the custom fields you use to store information about
constituents are called constituent attributes and constituent codes. Fields you use to store custom information
about gifts in The Raiser’s Edge are called gift attributes. When you synchronize data, you can map constituent
and gift attributes to the custom fields and segment categories Sphere uses for each field group (see table).
Constituent codes automatically match with Sphere’s primary constituencies, so you do not need to map them.
Sphere automatically creates constituencies when you import constituent codes from The Raiser’s Edge that do
not exist in Sphere.
Field Group
Sphere Custom Field
Data Relates to the...
Contact Updates
Custom profile fields and segment categories
Supporter
Gifts
Custom event fields
Gift and not the supporter
Registrations
Custom event fields
Event and not the supporter
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
31
Auto-create Fields Option in Sphere
The auto-create fields option allows you to synchronize constituent and gift attribute information from The
Raiser’s Edge without manually creating and mapping the same custom field in Sphere. This functionality is
available for constituent and gift attributes when use the Constituent Update and Gifts field groups.
l
l
When you auto-create custom fields for Constituent Updates, Sphere creates custom profile fields using
the same attribute labels you use in The Raiser’s Edge and lists them in your account’s default custom
profile field folder.
When you auto-create custom fields for Gifts, Sphere creates custom event fields using the same attribute
labels you use in The Raiser’s Edge and lists them in your account’s default custom event field folder.
Sphere also auto-creates segments when you add new values to attribute tables you map to Sphere segment
categories, and auto-creates constituencies when you import constituent codes from the Raiser’s Edge that do
not exist in Sphere.
Special Character Synchronization for Sphere and The Raiser's
Edge
Use the table below to learn the special characters you should not include in custom field and attribute names
you will use for synchronizations between Sphere and The Raiser’s Edge. For example, you should not attempt to
synchronize a custom field with the name Pet’s Breed. Instead, change the field name to Pet Breed or Breed of
Pet.
Special characters that appear in field values will synchronize. For example, if the value of Address Line 1 is 456
Miller’s Lane, the apostrophe will appear when you synchronize the field.
Special
Character
Special Character
Name
&
Ampersand
<
Left angled bracket
>
Right angled bracket
“
Quotation mark
‘
Apostrophe
Sphere and The Raiser's Edge Synchronization
Batches Overview
A synchronization batch is a group of records you send between Sphere and The Raiser’s Edge. Synchronization
batches use records you create or update since the last synchronization, and include standard and non-standard
fields and attributes from categories related to the field groups you select.
Imports
32 CHAPTER 1
When you import contacts, Sphere uses your account’s name and the synchronization time to name batches.
For query results, the Sphere batch and contact list names use The Raiser’s Edge constituent query name.
Sphere displays the details for contact and query result imports in the Most Recent and History tabs from the
Connector Sync menu.
Contact Update and Gift Imports
The contact import details include the number of successful imports, the number of records Sphere did not
import because the Sphere record is more recent, and the number of records Sphere did not import because the
records fail to meet the synchronization criteria. Contact import failures can occur for the following reasons:
l
l
l
The Raiser’s Edge field value exceeds the character limit in Sphere. For example, if you attempt to
synchronize a text field from The Raiser’s Edge that contains 200 characters and the field limit for the
corresponding field in Sphere is only 150 characters, Sphere will reject the record and then display the
failure in the batch results.
The Raiser’s Edge field data type does not match the Sphere field data type. For example, if you attempt to
synchronize a money field from The Raiser’s Edge with a date field in Sphere, Sphere will reject the record
and then display the failure in the batch results.
The Raiser’s Edge donation contains values for gift categories such as fund, appeal and campaign and the
mapping does not match your account’s gift allocation structure. For example, if you attempt to
synchronize an appeal from The Raiser’s Edge with an appeal in Sphere that has a campaign, Sphere will
reject the donation if you do not also map and synchronize the campaign information. The gift allocation
import flowchart shows how Sphere handles donations you import.
Note: If an Out-of-Sync condition warning displays at the top of the Most Recent page or in the History page’s
Description column, it indicates that the synchronization job numbers are out of order. Verify the list of
expected records by viewing the # Success details. If the records did not import, contact your Sphere
representative.
You can attempt to re-import records that fail by updating the records in The Raiser’s Edge and processing
another synchronization batch, or by using the Reprocess option for donation records Sphere did not import
because the gift allocation from The Raiser’s Edge did not match the gift allocation in Sphere.
When you use the Reprocess option, Sphere includes the gifts in the next synchronization batch you schedule
and removes the failure details from the import record.
Contact List Imports
Contact list results include the number of successful imports, and The Raiser’s Edge identification number for
query records that did not import because the records do not exist in the Sphere CRM database. You can reimport the complete set of query results after you import the missing records into Sphere.
Exports
Sphere uses the name of your account and the synchronization time to name batches you export, and records
their dates in the Most Recent tab from the Connector Sync menu. For information regarding how The Raiser’s
Edge displays synchronization batches, see the Blackbaud Sphere & The Raiser’s Edge Integration Guide from
Blackbaud.
Note: If you do not commit records in The Raiser’s Edge after you export them from Sphere, the next
synchronization batch will not re-send the records unless they contain updates.
S PHE RE
AND
T HE R A ISE R ' S E DGE S Y N CHRO N IZA T IO N O V E RV IE W
33
Scheduling and Processing Sphere and The Raiser's Edge
Synchronization Batches
When you schedule synchronization batches for Sphere and The Raiser’s Edge, you are specifying when to send
records to Sphere or The Raiser’s Edge database. Processing is the set of actions each database takes to
complete the synchronization. Depending on the synchronization mode and field groups you select, records you
update or create since the last synchronization are sent between Sphere and The Raiser’s Edge. When Sphere
processes a synchronization batch, the records are immediately added to the database. After a synchronization
batch processes in The Raiser’s Edge, the data is available through The Raiser’s Edge Sphere page.
Schedule batches through The Raiser’s Edge by selecting the time and date to begin synchronizations, and how
often to process them. When you schedule batches, the first batch immediately processes and then the other
batches process according to the times you specify. You can also manually initiate a batch if you want an
immediate one time synchronization. For information regarding how to schedule a batch and then commit the
records to The Raiser’s Edge, see the Blackbaud Sphere & The Raiser’s Edge Integration Guide from Blackbaud.
Note: Synchronization relies on strict time matching criteria to update records, otherwise batches will not
process. Therefore, you must ensure the computers you use for The Raiser’s Edge have the correct time.
34 CHAPTER 1
chapter 2
Configure Sphere for
synchronization with The
Raiser's Edge
Install The Raiser's Edge/Sphere synchronization components
36
Register The Raiser's Edge with Sphere for Synchronization
36
Send metadata from The Raiser's Edge to Sphere
36
Schedule synchronization between Sphere and The Raiser's Edge
40
Configure Sphere for synchronization with The Raiser’s Edge by performing the following steps:
1. Activate Sphere Connect API
2. Install The Raiser’s Edge/Sphere synchronization components
3. Register The Raiser’s Edge with Sphere for the synchronization service
4. Send metadata from The Raiser’s Edge to Sphere
5. Map synchronization fields
6. Activate Sphere for synchronization with The Raiser’s Edge
Note: New features are now available if you upgrade to the latest version of the Sphere Connector Service. Visit
www.blackbaud.com/support/downloads/downloads.aspx to download the new installation files.
} Activate Sphere Connect API
Use this procedure to activate the Sphere Connect API, which is necessary before you can configure The Raiser’s
Edge for synchronization with Sphere. You only need to perform this procedure the first time you configure
synchronization between Sphere and The Raiser’s Edge.
Prerequisites
l
The Sphere Connect API has not been previously activated for your account
l
The Sphere Connect API is enabled for your Sphere account
Starting point:
You are logged into Sphere.
36 CHAPTER 2
1. Select Control > Administration > Kintera Connect API.The Sphere Connect API WSDL page appears.
2. Accept the Sphere Connect terms and conditions.
Note: You do not need to download the Sphere Connect API WSDL. Instead, install the Sphere/Raiser’s Edge
Integration Plugin and the Sphere Connector Service. For more information regarding how to install them, see
the Blackbaud Sphere & The Raiser’s Edge Integration Guide from Blackbaud.
Install The Raiser's Edge/Sphere
synchronization components
For information regarding how to install the Sphere/Raiser’s Edge Integration Plugin and the Sphere Connector
Service, see the Blackbaud Sphere & The Raiser’s Edge Integration Guide from Blackbaud. You only need to
perform this procedure the first time you configure synchronization between Sphere and The Raiser’s Edge, or if
you are upgrading to a more recent version of the Sphere Connector Service.
Register The Raiser's Edge with Sphere for
Synchronization
For information regarding how to register The Raiser’s Edge with Sphere so you can enable the synchronization
service, see the Blackbaud Sphere & The Raiser’s Edge Integration Guide from Blackbaud. You only need to
perform this procedure the first time you configure synchronization between Sphere and The Raiser’s Edge, or if
you are upgrading to a more recent version of the Sphere Connector Service.
Send metadata from The Raiser's Edge to
Sphere
For information regarding how to send metadata from The Raiser’s Edge to Sphere so that you can use the
synchronization service, see the Blackbaud Sphere & The Raiser’s Edge Integration Guide from Blackbaud. You
only need to perform this procedure the first time you configure synchronization between Sphere and The
Raiser’s Edge, and when you create new attributes, funds, campaigns, appeals, packages, and events in The
Raiser’s Edge.
} Map synchronization fields for Sphere and The Raiser's Edge
Use this procedure to map synchronization fields in Sphere with fields in The Raiser’s Edge. You only need to
perform this procedure the first time you configure synchronization between Sphere and The Raiser’s Edge, or
when you make changes to the fields and attributes you use.
Review the synchronization field tables for Sphere and The Raiser’s Edge, and then map fields that are nonstandard. When you map fields in Sphere, The Raiser’s Edge uses the same mapping. After you complete the
mapping, activate Sphere for synchronization.
C O N FIGU RE S PHE RE
FO R SY N CHRO N IZA T IO N WIT H
T HE R A ISE R ' S E DGE
37
Note: Event mapping matches Sphere events and registration types with The Raiser's Edge events and units —
not fields.
Prerequisites
l
You have administrator access to the account you will synchronize with The Raiser’s Edge
l
You have already accepted the Connect terms and conditions
l
The synchronization components are already installed
l
The Raiser’s Edge is already registered with Sphere for the synchronization service
l
The Raiser’s Edge metadata is already sent to Sphere
Starting
point:
You are logged into Sphere.
The Phone/Email page of the Connector Sync Mapping tab is displayed. If
not, select Control > Administration > Connector Sync > Mapping.
Step 1: Review synchronization fields for Sphere and The Raiser’s Edge
1. Review the synchronization field tables.
2. Create the custom profile, segment, custom event, fund, campaign, and appeal and source code fields
you will map if the fields or attributes do not already exist in both databases.
Step 2: Map Sphere’s fields to The Raiser’s Edge fields
1. For Sphere Fields, click a field name in your Sphere database.
2. For The Raiser's Edge [Fields], click an attribute name in The Raiser’s Edge database to which the Sphere
field will be mapped.
3. Click Add Mapping to add the field and attribute to the Synchronization Mapping list box.
4. If you need to remove a field from Synchronization Mapping, select it and then click Remove Mapping.
To remove all mapping fields on a tab, click Remove All.
5. If you are mapping fields on the Custom Profile Fields or Custom Event Fields tabs, the Auto-create Sphere
custom profile or custom event fields check box is selected by default. Deselect the check box if you do not
want Sphere to automatically create new custom profile and custom event fields when you import
unmapped constituent and gift attributes from The Raiser’s Edge.
Note: When you select the Auto-create Sphere custom profile or custom event fields check box, Sphere lists the
new custom fields in your account’s default custom profile and custom event folders.
6. If you are mapping fields on the Source Codes, or Registration Types tabs, select an appeal or event for
Select an appeal from The Raiser's Edge or Select events from the Events tab. Sphere will populate the
related packages or registration types and units so that you can map them.
7. Repeat these steps as needed. Each time you click Add Mapping, Sphere automatically saves your
changes.
38 CHAPTER 2
} Activate Sphere for synchronization with The Raiser's Edge
Use this procedure to activate Sphere for synchronization with The Raiser’s Edge. You only need to perform this
procedure the first time you configure synchronization between Sphere and The Raiser’s Edge, and when you
want to change the synchronization mode or the field groups you are using.
After you review the synchronization field tables and map any non-standard fields you use, activate Sphere by
indicating the types of records you will synchronize. You must activate Sphere before scheduling synchronization
batches through The Raiser’s Edge.
Prerequisites
l
You have administrator access to the account you will synchronize with The Raiser’s Edge
l
You have already accepted the Sphere Connect terms and conditions
l
The synchronization components are already installed
l
The Raiser’s Edge is already registered with Sphere for the synchronization service
l
The Raiser’s Edge metadata is already sent to Sphere
l
The Raiser’s Edge fields are already mapped to Sphere fields if you are synchronizing fields that are not
standard
Starting
point:
You are logged into Sphere.
The Admin page of the Connector Sync is displayed. If not, select Control >
Administration > Connector Sync > Admin.
1. For Connector Sync Mode, select one or more option below. Make selections for each direction in which
you want to synchronize records.
Select
If you are…
Corresponding link in the
The Raiser’s Edge Sphere
page…
Contact
Updates
Synchronizing profile information
Sign-up Requests
Gifts
Synchronizing donation information
Donations
Events
Exporting registration information from Sphere
to The Raiser’s Edge
Event Registrations
Advocacy
Exporting advocacy data from Sphere to The
Raiser’s Edge
Advocacy Actions
Contact Lists
Importing constituent query results from The
Raiser’s Edge to Sphere
Queried Contact Lists
Profile Updates
Note: You must select and save at least one Connector Sync Mode option before you schedule a batch through
The Raiser’s Edge.
C O N FIGU RE S PHE RE
FO R SY N CHRO N IZA T IO N WIT H
T HE R A ISE R ' S E DGE
39
Note: Selecting the first check box in a column automatically selects all the other check boxes in the Connector
Sync Mode table.
2. For Connector Sync Activations, make your selections as follows:
a. If you selected Contact Updates, choose one or more of the following options as necessary.
The standard contact fields and attributes will automatically synchronize.
Select
If you are…
Field mapping
required?
Phone/Email
Synchronizing phone or E-mail profile
data
Yes
Addresses
Synchronizing address profile data
Yes
Custom Profile Fields
Synchronizing constituent attributes with
Sphere custom profile fields and segments
Yes
Thon Summary Fields
Exporting participant Thon summary
fields from Sphere to The Raiser’s Edge
No
b. If you selected Gifts, choose one or more of the following options as necessary. The standard gift fields, and custom selections made via the Custom Event Fields mapping tab, will
automatically synchronize.
Select
If you are…
Field mapping
required?
Funds
Synchronizing funds and designations
Yes
Campaigns/Appeals
Synchronizing campaigns and appeals
Yes
Source codes
Synchronizing Sphere source codes
with packages in The Raiser’s Edge
Yes
Memorial/Tribute
Fields
Exporting memorial/tribute fields from
Sphere to The Raiser’s Edge
Only the custom
memorial/tribute
fields you use in
custom Friends Asking Friends Web
sites, or Single Step
Donation forms
Participant Sponsors
Exporting participant gifts from Sphere
to The Raiser's Edge and want to mark
the event participant as the solicitor
for the donor
No
40 CHAPTER 2
c. If you selected Events, use the following options as necessary. The standard and custom
event fields, and event selections made via the Events mapping tab, will automatically
export from Sphere to The Raiser’s Edge.
i. Select the Registration Types check box if you are exporting registration types and you have
already mapped them to units because the names to not exactly match in Sphere and The
Raiser's Edge.
ii. Select the Event Sponsors check box to export sponsorship information from Sphere to The
Raiser's Edge.
3. Click Save.
Schedule synchronization between Sphere and
The Raiser's Edge
For information regarding how to schedule synchronization between Sphere and The Raiser’s Edge, see the
Blackbaud Sphere & The Raiser’s Edge Integration Guide from Blackbaud. You only complete this step after you
configure each database for the synchronization.
Note: Synchronization relies on strict time matching criteria to update records, otherwise batches will not
process. Therefore, make sure the computers you use for The Raiser’s Edge have the correct time.
} View historical synchronization result from The Raiser's Edge to Sphere
Use this procedure to view detailed results of historical synchronizations from The Raiser’s Edge to Sphere.
Detailed results of historical synchronizations for Sphere exports are available through The Raiser’s Edge.
The History page contains a batch list from which you can select a specific synchronization. The import results
display on a page containing two tables—one for contact updates and gifts, the other for contact lists.
Prerequisites
l
l
You have administrator access to the account you synchronized with The Raiser’s Edge
A synchronization batch from The Raiser’s Edge to Sphere is already processed if you are viewing the
results
Starting
point:
You are logged into Sphere.
The History page of the Connector Sync is displayed. If not, select Control>
Administration>Connector Sync > History.
To view historical contact update and gift synchronization results
1. From the batch list, highlight the batch name for the date and time you want to view and select
View Detail. The RE Batch Details page appears.
C O N FIGU RE S PHE RE
FO R SY N CHRO N IZA T IO N WIT H
T HE R A ISE R ' S E DGE
41
2. For Import Batch Detail, click View for any category in the # Success, # Sphere is More Recent, or
# Failed columns to view a detailed list of records.
Note: If the Description column for the batch you are viewing displays w/Out-of-Sync Condition, it indicates
that the synchronization job numbers are out of order. Verify the list of expected records by viewing the #
Success details. If the records did not import, contact your Sphere representative.
Note: If you want to view a supporter record from an import, navigate and search for the record via Contacts >
Individuals (or Organizations). Sphere displays the synchronization date in the Date Modified field on the
Record Management tab. For a view of an entire gift record, navigate and search for it via Contacts > Gifts.
Sphere displays synchronization dates for gifts when you use the Date Modified column in the Gift View of the
Find Transactions page.
To view historical contact list synchronization results
1. From the batch list, highlight the batch name for the date and time you want to view and select
View Detail. The RE Batch Details page appears.
2. For Import Contact List:
3. Click View in the # Success column to view a detailed list of records
4. Click Download in the # Failed column to view The Raiser’s Edge identification numbers for the
records that did not import because the corresponding records are not available in Sphere.
Note: Constituent query import records are also available via Contacts > Database Management >
Contacts Lists. The Sphere contact list name uses The Raiser’s Edge constituent query name.
} View most recent synchronization results for Sphere and The Raiser's Edge
Use this procedure to view detailed results of the most recent import synchronizations from The Raiser’s Edge to
Sphere, and to view export status and date information for synchronizations from Sphere to The Raiser’s Edge.
Detailed results of synchronizations for Sphere exports are available through The Raiser’s Edge.
The Most Recent page contains two columns. Import results in the left column display in two tables—one for
contact updates and gifts, the other for contact lists. The right column contains export information.
Prerequisites
l
l
l
You have administrator access to the account you synchronized with The Raiser’s Edge
A synchronization batch from The Raiser’s Edge to Sphere is already processed if you are viewing the
results
A synchronization batch from Sphere to The Raiser’s Edge is already processed if you are viewing the
status and date information
Starting
point:
You are logged into Sphere.
The Most Recent page of the Connector Sync is displayed. If not, select
Control > Administration > Connector Sync > Most Recent.
To view the most recent contact update and gift synchronization import results
42 CHAPTER 2
1. For Import Batch Detail:
a. Click View for any category in the # Success column to view a detailed list of records that
Sphere imported.
b. Click View for any category in the # Sphere is More Recent column to view a detailed list
of records that Sphere did not import because the record in Sphere is more current than
the one in The Raiser’s Edge.
c. Click View for any category in the # Failed column to view a detailed list of records that
Sphere did not import because the records fail to meet the synchronization criteria.
Note: If an Out-of-Sync condition warning displays at the top of the page, it indicates that the
synchronization job numbers are out of order. Verify the list of expected records by viewing the #
Success details. Contact your Sphere representative if the correct records did not import. If the
message An older version of the Connector is currently in use appears, click the link to update
your version of the Connector.
Note: If you want to view a supporter record from an import, navigate and search for the record
via Contacts > Individuals (or Organizations). Sphere displays the synchronization date in the
Date Modified field on the Record Management tab. For a view of an entire gift record, navigate
and search for it via Contacts > Gifts. Sphere displays synchronization dates for gifts when you use
the Date Modified column in the Gift View of the Find Transactions page.
To view the most recent contact list synchronization import results
1. For Import Contact List:
a. Click View in the # Success column to view a detailed list of records.
b. Click Download in the # Failed column to view The Raiser’s Edge identification numbers
for the records that did not import because the corresponding records are not available in
Sphere.
To view the most recent synchronization export information
1. For Export (from Sphere), review the synchronization batch status and date information.
} Reprocess gift records Sphere did not import from The Raiser's Edge
Use this procedure to reprocess gift records that Sphere did not import from The Raiser’s Edge because the gift
allocation from The Raiser’s Edge did not match the gift allocation in Sphere. When you use this option Sphere
includes the gifts in the next synchronization batch you schedule.
Prerequisites
l
You have administrator access to the account you synchronized with The Raiser’s Edge
l
A synchronization batch from The Raiser’s Edge to Sphere is already processed
C O N FIGU RE S PHE RE
Starting
point:
FO R SY N CHRO N IZA T IO N WIT H
T HE R A ISE R ' S E DGE
43
You are logged into Sphere.
The Most Recent page of the Connector Sync is displayed. If not, select
Control > Administration > Connector Sync > Most Recent.
1. Click Reprocess for the Gift category in the # Failed column to reprocess only the gift records that Sphere
did not import from The Raiser’s Edge.
Sphere includes the gifts in the next synchronization batch you schedule and removes the failure details
from the import record.
Note: You must manually fix fund, appeal, source code and campaign gift allocation errors before you
reprocess the gifts. Otherwise, Sphere will not import them. For example, if you attempt to import a gift
with mapping to the Street Clean-up Fund and the Disaster Relief Campaign, then you must associate the
Street Clean-up Fund with the Disaster Relief Campaign in your Sphere gift allocation.
} Review synchronization records Sphere did not import from The Raiser's Edge
Use this procedure to review detailed results of records that Sphere did not import from The Raiser’s Edge.
The Most Recent page contains two columns. Import results in the left column display in two tables—one for
contact updates and gifts, the other for contact lists. The right column contains export information.
Prerequisites
l
You have administrator access to the account you synchronized with The Raiser’s Edge
l
A synchronization batch from The Raiser’s Edge to Sphere is already processed
Starting
point:
You are logged into Sphere.
The Most Recent page of the Connector Sync is displayed. If not, select
Control > Administration > Connector Sync > Most Recent.
To review contact update and gift records Sphere did not import from The Raiser’s Edge
1. For Import Batch Detail:
a. Click View for any category in the # Sphere is More Recent column to view a detailed list
of records Sphere did not import because the record in Sphere is more current than the
one in The Raiser’s Edge.
b. Click View for any category in the # Failed column to view a detailed list of records that
Sphere did not import because the records failed to meet the synchronization criteria.
To review contact list records Sphere did not import from The Raiser’s Edge
1. For Import Contact List, click Download in the # Failed column to view The Raiser’s Edge identification numbers for the records that did not import because the corresponding records are not
available in Sphere.
44 CHAPTER 2