Relationship Records

Relationship records allow person records in Slate to store information about associated individuals (e.g., parents, guardians, spouses, siblings).

Each relationship record represents a connection between two individuals and can store its own data, including contact information, biographical details, interactions, and custom relation-scoped fields.

Adding a new relationship to a record

To add a new relationship to a person record:

1. Go to Records.

2. Select a person record.

3. Select the Profile tab.

4. Select Relationships.

5. Select New Relationship.

6. Configure the following settings:

   • Relationship Record: Indicates whether the related individual already exists as a person record in Slate. Select whether the relative entered already has a record in Slate.

   • Lookup Record: If the relative exists as a record in Slate, use Lookup Record to link the record.

   • Type: Select the relationship type, like parent or sibling. You can create custom relationship types.

   • Inverse Relation Type: Select the relationship type from relative’s perspective.

   • Prefix: Select the appropriate prefix prompt, like Mr or Dr. Custom prompt lists can be defined by using a key of prefix.

   • Name Information: Enter first, last, and additional name fields for the related individual.

   • Email: Enter the email address of the relative.

   • Phone: Enter the phone number of the relative.

   • Birthdate: Enter the birthdate of the relative.

   • Age: Enter the age of the relative.

   • Deceased: Select if the relative is deceased.

   • Resides with Record: Select if the relative resides with the record.

7. Select Save.

Querying on relationship records

Relation-scoped queries return one row per relationship. As a result, relation-scoped queries may return a different number of rows than person- or application-scoped queries, even when using similar filters.

To create a relationship-scoped query:

1. Navigate to Queries / Reports.

2. Create a new query with:

   • Type: Configurable Joins

   • Category: Related

   • Base: Relation

3. Add desired exports and filters.

Collecting relationship data with forms

Relationship data can be collected on person- or application-scoped forms. Collecting this data during the applicant stage is recommended.

Field Mapping

Map form fields to the appropriate relationship categories:

• Relationship

• Relationship Job

• Relationship School

Multiple Relationships in One Form

When collecting multiple relationships on a single form:

• Add a Section Break between each relationship

• Assign a unique Form Field Group number to each set of relationship fields

Failure to group fields correctly may result in data being overwritten on submission.

Matching and Duplicate Prevention

Relationship records will only match an existing record when all of the following are present:

• First Name

• Last Name

• Relationship Type

If a relationship type is not included (e.g., on a form), duplicate relationship records may be created.

Safe vs. Unsafe Behavior

By default, most forms are Safe. Safe forms will not update certain data if a record has an active application.

This may prevent relationship data from being updated.

Set Form to Unsafe

1. Open the form and select Edit Properties.

2. Set the form to Unsafe.

3. Select Save.

Override Safe Behavior for a Field

1. Edit the field.

2. Enable Unsafe Override.

3. Select Save.

Why isn’t my form updating relationship data?

If the record has an active application, Safe behavior may prevent updates.

To allow updates:

• Set the form to Unsafe, or

• Enable Unsafe Override on specific fields

Explore our Safe / Unsafe documentation to learn more about how safe and unsafe behavior can affect your records.