Configurable Joins

Configurable Joins offer greatly extended capabilities for data extraction by providing access to more tables in the database, as well as a “smart” join menu that includes only query populations or tables that are related to the starting population, which then includes more possible related populations as more joins are added to the query.

What are Configurable Joins?

A “join” combines data from multiple tables for querying based on relationships between them. Configurable joins allow users to specify how a related table should be joined to a query base.

Configurable Joins significantly expand access to the database by exposing more of the underlying tables that were previously available only through custom SQL or direct SQL access. It also offers greater flexibility in query building. For example, a table that utilizes ranks could be joined multiple times to the same base. Each join pertains to a single record out of multiple possible records (for example, one join on Address Rank #1, and then an additional join for Address Rank #2).

Databases

Slate data are stored in tables, and a collection of tables together comprise a Slate database. Slate databases can be described as relational databases, which means that the database tables are interrelated.

For example, when viewing a person record in Slate, an additional tab appears when the person also has an application.

This application record is represented as a row in the Application table. It is possible for a person to have multiple applications, which then take up multiple rows in the Application table.

How does Slate know that these two rows in the Application table also belong to the same individual (i.e. the same row in the Person table)? In a Slate database, there is a one-to-many relationship between the Person table and the Application table; that is, one instance on the Person table could be related to more than one instance on the Application table, but one instance on the Application table can be related back to only one instance on the Person table.

The Slate Query Builder enables access for viewing data in the underlying tables, as well as functionality for extracting and manipulating data. Currently, the Query Builder provides access to table data through a standard list of Query populations or bases. Many of these query populations present table data in a predetermined way: for example, the Prospects query population automatically excludes person records with an Opt-Out tag.

Was this article helpful?
19 out of 47 found this helpful