Import Exceptions due to "Record to update is for another constituent"

James Rhodes · May 2023

Howdy folks! I was doing to preferred address data clean up within all FL constituents via import. Among 54K+ records, 20 came back as exceptions with the reason being “Record to update is for another constituent”. I have confirmed that the constituent ID's, Preferred Address Import ID's, and other imported data is complete and correct. These records are also queryable/able to be used in a query and viewable in RE Classic but not viewable in RE NXT. Has anyone seen this before?

JoAnn Strommen · May 2023

@James Rhodes Welcome to BB community!

Haven't seen but am wondering if the address is shared with another constituent. That might be a reason for the exception/error.

James Rhodes · May 2023

@JoAnn Strommen Thank you for the warm welcome!

I see what you mean. That's potentially an issue because some are constituents at the same location, but slightly differing address such as “ 1234 example way, Office of the President” vs “1234 example way, Office of the Provost”. I've also found that some of the records are also one-offs. Thank you for the guidance!

JoAnn Strommen · May 2023

@James Rhodes
Yes, there can be duplicate addresses. I am referring to ‘shared’ address. Say Bill Smith is a constituent. At some point a record is needed for his wife Sue. While a user can key in the same address on her record, a better practice is to ‘share’/link the address from Bill's record. This way when one changes, it will be changed on both records. Just a thought that it could affect your cleanup.

a82c1fc11b429c92a428944d0edaff8d-huge-im

Import Exceptions due to "Record to update is for another constituent"

Comments

Categories