Hi
Is anyone successfully running the Contribution Import Utility in v15? I have a support ticket open but getting frustrated with the process. We have now established there is a known defect with the Import Utilities (all I think) since v15.1.16 which is not fixed until v16. The defect info is a bit vague, but I've managed to confirm the Default Address is not working and so you need at least a postcode (and I've found also an email address!) before it will run. I've tested it with a single row of test data using only Last Name, Postcode, email address, contribution date, contribution amount and received amount. This ran, but when I posted the batch, it has only created a transaction/payment entry, but no contribution entry. I assume it should create a Contribution? It has also not imported the postcode, so the Constituent address is completely blank.
I then ran it using the same data file with 10 rows of actual data including full address details, and now it is saying there is a mismatch between the data file and format file, even though these are effectively the same as I ran with one row. Screenshot below. So I'm thinking it's an address issue, given the known defect is something to do with address data?
If anyone has any insights to share, I'd be very grateful! NB I'm running this in TEST, so am aware of the need to log in without Windows Authentication, so am using my alternative non-WA Tessitura account (this is only fixed in PROD, not TEST).
Many thanksBest wishesDawn
Hi Dawn, we use this daily and are on V15. It's a fickle utility but have worked through the kinks. Happy to help you troubleshoot via a meeting or share our import process if that helps?
Cheers,
jordan
This error is the worst one as it's not clear at all. It's usually that you've exceeded character limit which for us in Aus is as follows:
Thanks for that nugget Jordan, I'll add that to the support ticket, and I may take you up on your kind offer of a call next week if we're still struggling!
Hi Dawn,
We do use this utility in v15 and so far haven't had an address issue. One small thing I've found is that if you even click into a cell or tab outside of your data rows when you are preparing the data file that it can then cause a 'mismatch' to the format file. You might already know this stuff but it sticks in my mind as the most infuriating thing I've had to troubleshoot about import utilities!Good luck, Katie
Hey Dawn,
All the import utilities can be a problematic in this way and like my esteemed collegues suggest the "out of sync" can often relate to one of the cells having unsuitable data or a separator (column or tab) too many that is throwing your rows out.
To get a better eye over mismatching for invisible characters, it's worth giving your file a look in Notepad++ and turning on View > Show Symbol > Show all characters.
As they say in the Contribution Import TroubleShooting doc it can also mean your XML file and data file are mismatched. You are using a txt file and I assume both the earlier one that works also is TXT.
If you've rerun it with the full address, have you changed your format file? You'll need to adjust it to include those fields.
The quirk of the defect is that it requires that something be in the postal code field, but it will not pull in unless you put in the full address. We don't use the contribution import, but I use the ticket order import a fair bit and I think it has the same issues.
Is this defect documented anywhere? We use import periodically, especially heavily following North Texas Giving Day later this month, so I'd like to know exactly how to avoid if possible.
I learned about it through a help ticket, so I'm not sure that it is. Basically, it just requires that something be in the postal code field or it fails. Prior to one of the most recent 15.2 service packs there was also a defect that required you to use a non-Windows authentication login or it would fail. But I'm happy to say that one has been fixed.
It's been a while since I've run this report--we usually do it once a year around Day of Giving. Commas or quotes in the file has been something that I've encountered that makes the utility throw an error. If I missed a comma in an address, or the number was formatted with the thousand separator, the utility errored out. That might be something else to check.
Best,
T.C.
HiJust to clarify - the non-Windows authentication issue is only fixed in PROD, it still exists in TEST...