Maintain Data Sync Cross-References

One of the challenges of exchanging data between two unrelated databases is dealing with codes and IDs that have no meaning outside the originating system. For instance, the unique ID of a campaign in Luminate Online is a number that has no meaning to an offline donor database. Conversely, the code of a group in an offline donor database has no meaning to the Luminate Online database.

To address this problem, Data Sync provides cross-reference tables to translate codes and IDs from one database to another. The cross-reference table associates a code or ID in Luminate Online to a code or ID in an offline donor database, and vice versa, as illustrated below:

Y ou will know you need to add or update cross-reference entries when you see messages like the following in the Data Sync reports or error files:

In this case, the remedy would be to add a campaign cross-reference entry for the campaign referenced in this report summary. In other cases, you may need to modify a cross-reference to keep it current.

Configuring cross-references is integrated into the process for creating objects. The feature works with popular third party off-line databases. Client administrators can enforce requirements regarding cross-reference creation before using newly created objects.