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.
I haven’t used the contribution import, but I know that the constituent import requires a postal code, even if you don’t have an address. I just put ours in and it does the trick (and it doesn’t end up on the record). Might be worth trying.
Thanks to everyone who responded with ideas. I did find the issue. When the file was saved it was saved as a text unicode. Although I had opened the file and resaved it as Text tab delimited, Microsoft Excel seemed to keep saving it in the unicode text format. I had several people looking at it, and one copied the contents of the file into a new document and saved it, and it ran. I then tested it with the full file and the import worked. Perhaps this will help someone else with troubleshooting.
That is an easy one to miss. You have to mentally zoom out pretty far to question the file type. That's the hard part. It is an easy oops and at the same time easy to overlook. I don't remember doing the same thing but have done the equivalent on other projects.