Likely related to T228241

Here are some more details regarding the new fields. We mapped the fields and then ran the data import job as usual and you can see between these two summaries that the "Total Bad Data" row (last item) increased significantly:

screenshot in email "Re: IBM Import details"

I initially thought it may have been mapped incorrectly, however I had our email consultant (and IBM guru) take a look and he did the same thing I did. After we ran a few search queries in IBM for "null" data, we deduced that the bad data could be from IBM not recognizing the data due to either an incorrect date format for the following queries: [endowment_last_donation_date] & [endowment_first_donation_date], and/or incorrect number format (the file contains commas for 4-digit+ numbers) for all the others [total_2018], [total_2019], [total_2020], and [endowment_number_donations].

Our default date format is: mm/DD/YYY and numeric format does not contain commas.

Please let me know if you have any questions. I'll be on IRC :)

Thank you for your help!