Data Definitions

Within the Compass-360 application there are several data sources or tables of data. Think of these as Excel documents.

Almost every table has a column that references another table. These are called primary and foreign keys which allow us to join in data.

For example, the Schedule Classes data source has a foreign key of Location ID which links to the Locations table primary key Location ID. These allow us to access data from multiple tables by a relationship.

Browsing Data

From the Reports view, click on the Browse button. This will take you to a page that lists all the available tables. Click on a table to visualize the raw data in the visual editor of a question. From there you can start building a question and save it.

Back at the browse page, hover a table and click on the reference icon to learn about the columns in this table and more.

X-Ray Data

Also from the browse page, there is a feature that intelligently builds a set of questions based of the data and it’s schema. Check out the X-Ray function on the Constituents data source for some useful insights. You can take any of those questions and start building our a question from it’s results.

Table Descriptions

Below is a list of the available tables you can use to build questions of off. To learn about each table, navigate from the browse page and click to learn more about a data source.

Academics

The individual academic or school records for constituents. This table has a unique, calculated column called partition index. This column is a number that represents the most recent academic record for a constituent. 1 is the newest.

Attendance

Individual attendance records for every type of attendance. Center, program / class, in person or virtual.

Constituents

The primary table of every constituent in your database. If you’re looking for just a specific persona, check our the core questions for specific personas, for example, the participants list.

Income

Income that you have accepted as a payment on an invoice. This represents the actual payment details such as the amount, date.

Invoice Line Items

Line items that are on an invoice. These will be individual items a constituent can pay for. For example "Membership Fee - After School".

Invoices

Open and closed invoices that are linked to your constituents. Closed invoices should also have a linked income record.

Locations

All your locations in your database such as Schools and Centers.

Memberships

The individual membership records for every constituent. Memberships have a foreign key that links to the constituent it is for.

Payments

Payments represent the payment method or vehicle that was used on an income. For example, a VISA Credit Card, or Check from Bank ABC.

Programs

Program templates, that you have created to be used in Schedules. These should only be used as a reference to data such as the program name, not to be searched directly. You should instead be searching the Schedule Programs data source.

Relationships

All the relationships that exist between your constituents. Useful to find parent constituents related to a results set of participants.

Schedule Classes

All the classes you have defined in any schedule within your database.

Schedule Enrollments

All the enrollment levels you have created within every schedule.

Schedule Programs

All the programs you have created within every schedule. Note, you’ll most likely want to join in the data from the Programs data source. Also due to the nature of the schedule design, programs do not always have a session parent.

Schedule Rosters

All the rosters, primary and lower for every schedule or level within a schedule. To find a class roster, you would start with the Schedule Class table, filter for a specific list of classes, and then join in the roster on the Linked To ID column. See the Class Roster Constituents core question for an example of this.

Schedule Sessions

All the schedule sessions you have created.

Staff Timecards

The timecards that have been recorded for any staff hours.

Tags

Every tag within the database. Most commonly, a tag is linked to a constituent. It is linked to a constituent by the Linked To ID. For example Constituents.Constituent ID => Tags.Linked To ID

Volunteer Timecards

The timecards that have been recorded for any volunteer hours.