|
|
|||||
Synchronizing Luminate CRM with Common GroundThis topic discusses how you use the Convio Connector for Common Ground DataSync to map import and export fields between Luminate CRM and Common Ground, as well as how to map custom donation fields. This operation differs from other Import/Export operations in that it involves mapping fields between Luminate Online and Common Ground. A new field mapping file will be used for the transaction to opportunity sync. Most of your work has been automated. During a Common Groundsync, if the custom donation field is assigned to the donation, it will flow bi-directionally as part of the Common Ground opportunity record. This will only affect the donation portion of the current Common Ground sync. Note: If you are synchronizing data with Common Ground, see the Common Ground Connector Users Guide. Edit OperationThe first step is to define various properties of the operation before you map your Luminate Online and Common Ground fields. To define operation properties:
Map Import FieldsThe only component on the Map Import Fields page is the Data Fields component. This crucial step allows you to match Common Ground fields to the corresponding fields in Constituent360. It matches headers in the import file with corresponding fields in the Constituent360 database. You must map at least one primary identifier in your import file with a File Header (Constituent ID, Primary Email, or Member ID). The component displays four columns, the first labeled Source (Common Ground Field) and the second labeled Target (Luminate Online Field). The final two columns, Reverse Mapping and More Information, provide information about the reverse mapped value of any field and any appropriate additional information that may help you select the correct mapping value. Note: If any of the columns match any Boolean Convio field such as the "Accept Mail" or "Accept Email" Luminate Online fields, a checkbox labeled "Flip Value (Yes means No)" displays in the More Information column. Constituent360 assumes the question asked of a constituent was, "Will you accept email?" The database therefore stores "Y" for "Yes, I will accept email" or "N" for "No, I will not accept email." But other database configurations assume the question asked was "Email declined?" In that case, the answer was "Y" for "Yes, email is not accepted" and "N" for "No, email is accepted." In such a case, "flipping the value" will match the "Y" or "N" in your database's configuration with Luminate Online's. To map import fields:
Map Export FieldsThe process of mapping export fields is identifical to that of mapping import fields except that you are mapping Luminate Online (Constituent360) fields to Common Ground fields. When you are done, click Next. The Map Custom Donation Fields page displays. Map Custom Donation FieldsMapping custom donation fields is identifical to mapping import and export fields, except that you deal exclusively with custom donation elements you created and added. To map custom donation fields:
|
|||||