Entities Overview
  • 22 Apr 2024
  • 1 minute read
  • Dark
  • PDF

Entities Overview

  • Dark
  • PDF

Article Summary

Slate delivers many standard tables that collect commonly grouped data points such as biographical data, school data, job data, and much more. Of course, your processes can require collecting additional grouped data points beyond these standard tables. Entities provide the flexibility to create these custom tables for any scenario of grouped data points.

Entity Widgets (a form with a special scope) live on person record custom tabs.

Entities are custom-built data tables that are exclusive to your database and process.

  • Scope & Display - Entities can be created for and displayed on person records, application records, or dataset records. These data are displayed as a table on the record using custom tabs and an entity widget.

  • Multiple entries of similar data - Entities store multiple entries of similar data. Each entry is a “row,” and the collected data points are the “columns.”

  • One-to-many data - Entities are used to store one-to-many data on records. For example, a list of the scholarships received by a student, or a list of their past schools attended.

  • Merge Fields & Queries - Entity data can be used as merge fields and query exports to display dynamically in other ways.

Examples of custom entities

A few examples for using an Entity include:

  • Scholarships

  • Class schedules

  • Courses

  • Programs of interest

  • Committees


A person or application can have multiple scholarships. In this case, a "Scholarships" Entity can be created with corresponding scholarship-scoped fields:


Class Schedule

A person takes multiple courses in a given semester. In this case, a "Class Schedule" Entity can be created with corresponding class-scoped fields.


Why use an entity?

Entities are highly customizable but aren’t appropriate for every situation. They also have limitations that may prevent them from being appropriate for your needs. If there is a need to collect and display information representing a one-to-many relationship on a record, then using an Entity may be ideal for your process. Questions you can ask to help determine this:

  • Does the information represent a one-to-many relationship, where one record has many possible entries? This might look like one application record with many different scholarships.

  • Does it make sense for the data to be displayed on a person, application, or dataset record?

  • Are there common data points that need to be collected for each row within the entity (such as entry name, effective date, or amount)?

📖 Further reading

Creating and displaying entities

Was this article helpful?