BUG: data importing contacts into the same household sometimes does not update hh naming and number of members.

[mrbelvedere]

https://powerofus.force.com/0D58000001SIUN2

I looked at this instance, and did see HH's with the problem, and other HH's without the problem. I don't understand the cause or weird behavior. need to try to reproduce in my own DE org so I can actually debug it.

[davidhabib]

Mehgan Morrison's org with the problem:

Charleston Parks Conservancy 00DF00000007S9S

Here is a report I created that shows all HH accounts with their Contacts: https://na10.salesforce.com/00OF00000067CDd You can see that the third one down in the report, Francis and Anne Cabot, updated correctly. But then the one just below that, Gregory and Suzanne Muth, did not.

[swiftrivermeghan]

Hello! Here's the details of what I was doing leading up to this issue:

• what tool did you use to import contacts with?

I was using DemandTools

• did all the contacts first go in individually (and get their own Household account)?

Yes. Each contact was first imported as its own individual contact record with the auto-generated HH Account created for it.

• how did you move the spouses to their respective partner's household?

Raisers Edge had an indicator (boolean) on the Relationship object to mark that someone is a Spouse, which got imported into a custom field called IsSpouse on the sfdc Relationship object. Then, in DemandTools, I exported the Relationship object records that had the IsSpouse box checked, along with their sfdc Contact IDs and HH Account IDs for both the Contact and the Related Contact in the Relationship object. Then I took that file and did an Update in DemandTools to remap the Related Contact's (HH) Account ID to be updated with the (primary) Contact's (HH) Account ID, which then put them both under the same HH Account.

• any other details you can think of in your process.

The only thing I wondered is that what I realized after the first pass at the update, which was about 1,000 records, was that some of the Contacts had a Relationship record for each person in the HH. So, in some cases for example, Joe Smith was a Contact with Sally Smith as his Related Contact (1st Relationship record), and then Sally Smith was a Contact with Joe Smith as her Related Contact (2nd Relationship record). After I realized this, I then went back and did a send export of the Relationship data to filter on only those records that had another boolean checked for them marking them as Head of Household on the Relationship object. I did the second update with this smaller file (about 350 records) and lowered the batch size to 1, but it didn't change the names at all.

So, I wonder if there was something about the fact that there were 2 Relationship records in my update file for some of the Contacts, essentially canceling one out from the other as the update progressed? Or, maybe the system just didn't know what to do with those and so it did nothing? That's the only thing I can think of.