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
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.
HiJust to clarify - the non-Windows authentication issue is only fixed in PROD, it still exists in TEST...