Please, stop creating Company Person records for every Relationship Person

We don’t use relationships at the moment, but this is just logical. ​@revathimenon, ​@Kenneth R, can we get some eyes on this?

Hi ​@angela_domenichelli 

The People data model works in a hierarchy and tight dependency with the Person object at the top followed by Company Person and Relationship person. In a way relationship person is a child of company person. In other words, a relationship person record cannot exist without a company person.
So all the data loads either through rules, connectors or even single record entry via the UI will need/create a company person to create a relationship person record. But there are no duplicate records being created.

Secondly, there’s one to many association amongst these entities. That is one person can be associated with multiple companies therefore multiple Company person records.
 One company can have multiple relationships and a person in that company can be eventually associated with multiple relationships and eventually lead to multiple relationship person records. So, if we pull data for a combination of PersonId and relationshipID, there are chances of multiple records for such a combination.

The right unique identifier for a relationship person is a combination of PersonID, CompanyID, CompanyPersonID, RelationshipID.

With the above in context, here’s responses to your queries : 

Query 1

• Duplicate Relationship Person records where the Person and Relationship are the same, but there are multiple Company Person records, Ticket 353751

We analysed the support ticket and evaluated the data with the above combination(PersonID, CompanyID, CompanyPersonID, RelationshipID) and do not see duplicate records. The ticket will be updated with the relevant findings. Please have a look and let us know if you have any more queries.

Query 2

Company Person records are created without an identifier or any detail

If you’re referring to Rules Engine, Load to People action, when a load is defined for Relationship Person, we mandate the relationship ID and derive the relevant companyID from that and thus CompanyID is not required to be configured for Load to relationship person. It is not a bug.

Query 3

Account Contact Relationship and Company Person have completely different datasets

From your overall description, I’m assuming you mean, Company Person has more records than that of Account contact relationship, this is possible because every relationship person records are created as company persons. So, in your case, records from Associated contacts will be created as company person records while they’re syncing to relationship person object. 

For e.g. if Account contact relationship has 5 records and that is synced with company person

Associated contact has 5 records and that is synced with relationship person.

Company Person will have a minimum of 10 records.

Let us know if my assumption is incorrect or you don’t see the relevant records from Account Contact relationship in company person. 

Thanks,

Shilpa

Hi ​@Shilpa Gumnur your summary is correct and exactly what I am asking Gainsight to change.  Company Person and Relationship Person should not be in a hierarchy.  I would still consider the Relationship Person records in ticket 353751 duplicates because everything we have defined as an identifier for Relationship Person is listed on 2 different GSIDs.  This is problematic for all aspects of Relationship Person in Gainsight because now users have no visibility into which of these Relationship Person records has all of the dependencies and our clients would certainly see emails sent from Programs using Relationship Person as an identifier as a duplicate.  I am not necessarily reporting a bug, but am requesting a change to the design.  The Company Person and Relationship Person objects should be separate entities.  The hierarchal nature is disruptive across Salesforce & Gainsight.

​@angela_domenichelli Company person(CP) and Relationship person(RP) are hierarchal in nature because the underlying core objects; Company and Relationships are. Since the former help in modelling the business they need to be tied together which eventually ties the entities associated with them. 

Would you like to get on a call for Programs? We would like to understand more about it to offer any remedy. 

We can connect over an email to find convenient slots. 

Thanks,

Shilpa

I have shared my availability in the 2 tickets that remain open for this.  

I have just heard from CSMs it is also problematic when logged emails to Timeline because there are so many unnecessary options to map to Company Person when the email address has not Account Contact Relationship. 

Gainsight ticket 384828 is another example of an issue with this process.  If the Company Person is deleted, the Relationship Person cannot be updated and must be deleted and re-created (causing loss of data integrity across Programs and other features.)