Toll Free 1-877-506-2744
How can we help?

Data Feeds: Decoding Relationship Merges and Splits

Print Friendly Version of this pagePrint Get a PDF version of this webpagePDF

The "Relationships" subsection of the Data Feeds area contains several reports generated with relationship data. Two of these feeds provide information on the requested and executed merges and splits in your system. This article assumes your institution is performing "householding" with the goal of synchronizing PrecisionLender and your core system.

Let's look at some examples and walk through each scenario that is shown. Some of the information leads to actionable tasks that can be performed in the core system to clean up the relationships.

The data feeds display the most recent data on the top so we read the records from the bottom-up in these examples.

Relationship Merges Example Dataset

Column Descriptions:

  • The first two columns describe the originating relationship family. This relationship may no longer live in the PrecisionLender system if we merged all of its primary relationships with another family.
  • The second pair of columns (Merged Primary Relationship Name/Id) contain information about the primary relationship that moved.
  • The "merged into" pair of columns describe where the primary relationship now lives.
  • Merge source can be either "Core" meaning the merge occurred because of a householding change detected in the relationship awareness upload or "Manual" meaning a lender merged the relationship through the PrecisionLender application.
  • The User column tracks the person that executed the merge for Manual merges. For Core operations, the user listed is the owner of that relationship.
  • Finally, the last column is a full timestamp of when the merge occurred.
Merged From Relationship Family Name Merged From Relationship Household Id Merged Primary Relationship Name Merged Primary Relationship Id Merged Into Relationship Family Name Merged Into Relationship Household Id Merge Source User Merge Timestamp
Joe's Farm   Joe's Farm 8e3f... Joe   Manual somebody@ somebank.com 2016-01-02 T09:10:36Z
Joe's Business   Joe's Business 0f1b... Joe HH_A  Core somebody@ somebank.com 2016-01-01 T08:00:00Z

Looking at the bottom entry - Things we know:

  • This merge was performed by the core system during a relationship awareness upload.
  • "Joe's Business" is a primary relationship with hashed id of 0f1b... (full id truncated for brevity).
  • It was not previously part of a householding because the second column is blank.
  • It was assigned a household id of "HH_A" and merged into a family named "Joe".
  • Since this was a merge, the family "Joe" must contain at least one other primary relationship

Looking at the top entry - Things we know:

  • This was a manual merge. As a side note, all manual merges clear out the household Id (as seen by the empty cell for "merged into relationship household id".
  • "Joe's Farm" was merged into the "Joe" relationship and it happened a day after the previous core merge.
  • It was not previously part of a householding because the second column is blank.

Things to take away from this data sample:

Manual merges are the best indications that something can be updated in the core system. The lender chose to merge "Joe's Farm" into "Joe" so the best course of action would be to update the core system to reflect this change.

 

Relationship Splits Example Dataset

Column Descriptions:

  • The first two columns describe the originating relationship family.
  • The second pair of columns (Split Out Relationship Name/ID) contain information about the primary relationship that moved.
  • The "split out" pair of columns describe where the primary relationship now lives.
  • Split source can be either "Core" meaning the split occurred because of a householding change detected in the relationship awareness upload or "Manual" meaning a lender split the relationship through the PrecisionLender application.
  • The User column tracks the person that executed the split for Manual merges. For Core operations, the user is listed as the owner of that relationship.
  • The second to last column is a full timestamp of when the split occurred.
  • Finally, "Was Ignored" has a very important meaning.
    • FALSE - The split was executed and you should see the results in the PrecisionLender application.
    • TRUE - Can only happen for Core splits where the core system attempted to split a relationship that was created (merged) manually by a lender. This entry was created in this data feed so that the core system could be manually updated to match the expectations of the lender. The split was not performed in PrecisionLender.
Originating Relationship Family Name Originating Relationship Household Id Split Out Relationship Name Split Out Primary Relationship Id Split Out Relationship Family Name Split Out Relationship Household Id Split Source User Split Timestamp Was Ignored
Brian Inc.   Brian's Cogs b905... Cogs of B   Manual somebody@ somebank.com 2016-02-02 T08:15:00Z false
Brian Inc.   Brian's Cogs b905... Brian's Cogs HH_B Core somebody@ somebank.com 2016-02-01 T08:00:03Z true
Brian Inc.   Brian's Widgets 0280... Brian's Widgets HH_B Core somebody@ somebank.com 2016-02-01 T08:00:01Z true 
Chris' Team   Chris 6fe3... Chris' Team HH_C Core somebody@ somebank.com 2016-02-01 T08:00:00Z true 

Looking at the bottom entry - Things we know:

  • This split attempt was NOT executed because the "Was Ignored" is 'true'.
  • The core system attempted to split primary relationship "Chris" out of one family into another family with the same name.
  • Having the same target family name as the originating name tells us that the relationship currently has additional primary relationships that the core system was not expecting. Core attempted to split the househeld primaries out to their own relationship family but was unable to.

Looking at the middle two entries - Things we know:

  • These two split attempts were NOT executed because the "Was Ignored" is 'true'.
  • The core system attempted to split two primary relationships named "Brian's Widgets" and "Brian's Cogs" out of a family called "Brian's Inc.".
  • Since these primary relationships share the same expected household id ("HH_B") we can deduce that the current family ("Brian Inc.") must contain some additional relationships that the lender manually merged with these primary relationships thus preventing the core system from splitting out the relationships.

Looking at the top entry - Things we know:

  • The lender came in a day later and manually split out "Brian's Cogs" into its own relationship family named "Cogs of B".

Things to take away from this data sample:

The main story this data tells us is that a few PrecisionLender relationships have additional primary relationships attached which is preventing the core system from properly householding the relationships. These primary relationships should be added to the core system if possible. Future relationship awareness uploads will continue to report "Ignored" split events for this relationship until either your core system is updated to match the PrecisionLender structure or the PrecisionLender structure is updated to match your core system (relationship family name should also be updated to synchronize the systems).

Was this article helpful?
Have more questions?