How can I troubleshooting a Custom Data Sync?

Options

While each Custom Data Sync has aspects that make it unique, there are some basic troubleshooting tips we can offer to get issues corrected quickly.

1. If you get a failure message, please be sure to take a look at the information provided. Often, the failure will say a message such as:

errorMsg=Unable to execute prepare statement java.sql.SQLException: ORA-01401: inserted value too large for column java.sql.SQLException

The important thing to not here is the part that reads:

inserted value too large for column

This means that there is a field with too many characters. Immediately preceding the error message you should see some sort of field that should direct you where to look. Basically, though, there is an issue with the data you are uploading.

2. If you are noticing that someone is in your Constituent 360 database but not in the offline database, or vice versa, you will want to check the Resolve New Constituents section of Constituent 360->Import/Export. If the contact is in this area, the issues of duplication of their record need to be cleared up before they will show up in Constituent 360.

3. If you notice that a constituent is in the offline and online databases but the donations associated with his/her record have not been downloaded, please be aware of the following. A constituent must be officially synched with both databases before the donations can be transferred. So, the new constituent in Cons360 must be downloaded from Convio, uploaded into your offline database, then reuploaded into Convio with the Member ID before the transactions associated with his/her record can come into the offline database.

These are basic issues that will crop up with custom data syncs. If you have any additional questions after reviewing the above information, please feel free to contact support.

Tagged:

Categories