Import Added Birthdates to BOTH Constituent and Spouse

Kirstin Ringel

A couple months ago, I imported birthdates to our constituent records. It appears, that for some, not all, the spouse record (both constituent and non-constituent) received the birthdate added to their record, as well. I've certainly got a cleanup project ahead of me. But the big things: I'm not sure where I went wrong or how to prevent this in the future. Can you help?

For example:

My import:

Joe Moretti

There is not a lot of information here to give any advice. If you can add more relevant information that might be helpful.

Alex Wong

your import file has 2 columns of birthday: "Birth Date" and "Spouse Birth Date", which appears to be the same exact date for the 3 rows you shown, which would be oddly coincidental if that is true. Unless I'm looking at this wrong, that the first screenshot is actually an export of the data after you did the import.

Your import mapping tab is showing only 4 columns, and you only mapped 2 columns: User20: Constituent ID and Date of Birth. If that was exactly your import, then ONLY the main constituent that is denoted by the User20: Constituent ID column would get the Birth Date field "set" to the value in the Date of Birth column.

non-constituent spouse is a relationship record, so it will be interesting to check the retionship record's "last date modified" to see if it was indeed the import that caused this issue OR was the date added before or after.

Madeleine Holdsworth

I think the file is showing the results after the import. I think you may want to examine the import file itself (and the query that produced it). That would be the first step to troubleshoot this.

Kirstin Ringel

https://community.blackbaud.com/discussion/comment/312162#Comment_312162

I will absolutely go look at the relationship record's "last date modified". Appreciate that insight! You are correct that the first screenshot is of my exported data, not the file that I imported.

Kirstin Ringel

None of the spouses share a "Date Last Changed" with my import file. So back to the drawing board. Thank you again for that suggestion. It helped me rule out that as the cause.

Alex Wong

I would suggest you "test" out a test import on a test constituent record with spouse.

Madeleine Holdsworth

@Kirstin Ringel

I've tried importing using the same fields you did, for both constituent and non-constit spouses. I could not replicate your results. The birthdates were imported only to the HOH spouse.

Dariel Dixon

Can you create a screenshot of the import file with some dummy data? It is almost impossible to troubleshoot without looking at the file that caused the issue.

Kirstin Ringel

Thanks, everyone. I did some test importing and could not replicate either. I believe since the "Date Last Changed" does not match my import, that perhaps the mistake was not mine. I appreciate the help! Now to start my cleanup.

Dariel Dixon

@Kirstin Ringel Is there someone else or another process that could have possibly created this data? I would hope there is not a lot of other people or processes that could have created this duplicated data. I would make sure that I have confidence that this issue won't be repeated the next time I import any data. In this situation, is there another script or something else that does match the date last changed that can give you some more insight as to how this data was created?

This is a quite silly problem, but a problem nonetheless.