• Replies 13 replies
  • Subscribers 342 subscribers
  • Views 125 views
  • Users 0 members are here
Options
Related

Contribution Import Utility error

T.C. Brown
$organization

Hi,

One of our consortium orgs always uses the contribution import utility for Giving Tuesday donations. Now that they have their data ready, when I try running this report, I keep getting errors.

This is the first since last year that I have tried to run this report. In May we went with Tessitura Merchant Services and the first error I got was related to PSPE. I commented out the Account Number, account Name and exp date in the xml file and deleted those columns since documentation mentioned utility would fail if Account Number and exp date fields were included. I then got the error "Expected row count is less than 1 or is undefined." I tried various things and even commented out all but the 3 minimum required fields as mentioned in the documentation, but I keep getting the 2nd error. I have confirmed that the import file and the xml file have the same three columns in each.

Has anyone had a similar issue with the contribution import utility?  If so, what have you done to make it work?

Appreciate any recommendations.

T.C.

Parents
  • $organization

    When the bulk import tool returns errors I do the following:

    1. Make a copy of the file and alter the copy so that only one row of data and headers is in the file.
    2. Run the import using this pared-down copy.
    3. If it imports successfully, then the issue lies in the data. You can eyeball the data and see if there are any glaring issues, but if you don't see any, try adding half of the data back into the pared-down copy and then try the import again. If it fails, then the data is in that section (at least), so you can keep stripping down the file contents in half until you find the offending row(s).
    4. If Step 2 did not import successfully, then the problem is most likely with your XML file. Using the same idea as Step 3, look over your header and XML contents for glaring issues. If none are found, create a new XML file with only the one half of the columns you want to import and alter your data file correspondingly. Try importing this. If it fails, then the problem is with the columns in this section of the XML, and you can keep repeating the process until you find the offending column(s). If the import is successful, then try with the other half of the columns until you find the culprit.

    I like to use NotePad++ when altering these files.

    Good luck!

  • $organization in reply to Katie Lachance-Duffy

    Hi Katie,

    Thanks for the suggestions.  I already cut the xml file to look at just 3 columns (the minimum it could be) and the data file had 3 rows for testing, but I made it only 1 row.  It continues to fail.  We didn't change anything from a year ago when it worked fine.  Thought maybe something had changed with a version update that affected the import and I missed--we are currently on V 15.2.39--forgot to add that before.

    The data set is basically the same as last year, with a different contribution date, the current campaign, and since i have been playing around with the xml file, i updated that to look at the one I'm testing with.

    Thanks again.

    T.C.

  • $organization in reply to T.C. Brown

    Just trying to think of anything that might be the culprit -- are the dates in the correct format? Do they match what you had last year?

  • $organization in reply to T.C. Brown

    Ugh, sorry, TC! That sounds so odd! I'd be happy to glance over it if you want to send it to me, but I'm sure a TN ticket would get to the bottom of this.

Reply Children