Importing Relationships for Advancement
  • 09 Nov 2023
  • 1 minute read
  • Dark
  • PDF

Importing Relationships for Advancement

  • Dark
  • PDF

Article Summary

Relationships between records of the same type (Person - Person, Company - Company, etc.) can be imported using standard destination mappings in Upload Dataset.

Relationships can be either created through this import process or linked to existing records. To link existing records, Slate needs at least the following information:

Record 1 ID | Record 1 Relationship Type | Record 2 ID | Record 2 Inverse Relationship Type

The record IDs can be either a Slate ID (such as the Slate GUID or Reference ID) or a custom unique for merging field (such as an Advance ID or Colleague ID). When utilizing a custom field that is unique for merging, be sure to also include the ID of the custom unique field in your source file:


The field mapping destinations for these values are:

  • Fields -- Other - Legacy ID (the unique for merging field associated with the record)

  • Relationship -- Relationship: Type

  • Relationship -- Relationship: Linked Record Unique Field

  • Relationship -- Relationship: Linked Record Unique Field Value

  • Relationship -- Relationship: Linked Record Inverse Type

An example of this type of import exists in the Advancement Showcase Clean Slate database environment, titled Relationship Import Example, in the Sources / Upload Dataset section of the database.

Additionally, relationship imports will match on First Name, Last Name, and Relationship Type. If a matching relationship object is not found, then a new relationship will be created.


It is strongly recommended that each relationship_type have a Category established at the prompt level. This will assist with the future head of household and salutation calculations.

Was this article helpful?