← Communications
Lesson 02 of 06Beginner 10–15 minutes

Fields

Learning objective

Explain what a field is, distinguish between a field and its value, locate field values on a record, and understand why knowing where information is stored matters throughout Slate.

Core takeaway

Fields define the individual pieces of information Slate stores. Understanding where information lives is foundational to finding it, collecting it, reporting on it, and using it in processes.

Understand

Fields: Where the Details Live

In the last lesson you learned that a record is something Slate stores information about. This lesson is about the information itself.

A field is a defined place where one specific piece of information is stored. Email address is a field. Birthdate is a field. Application status is a field.

The field is the container. The value is what's inside it for a particular record. Two people share the same fields, but almost never the same values.

Fields concept card
Concept Card

Fields

A field is where a single piece of information is stored about a record — the foundation of your data.

The big idea

A field is the label. A value is the answer.

Record

Jordan Ellis

Field

Email Address

Value

jellis@example.edu

Same field, different value, on every record in your database.

When someone asks you to “pull everyone with an incomplete application,” they're really asking you to look at a field and filter on its value. Knowing which field holds the information is usually the hardest part of the request.

Remember these

Field

A defined place where one specific piece of information is stored.

Value

The actual information stored in a field on one particular record.

Where it comes from

Values arrive from forms, imports, staff entry, and automated processes. The field stays the same no matter how the value got there.

Check your understanding

One question at a time. Wrong answers are just practice.

Question 1 of 3

Which of these best describes a field?

Practice

Read the Fields on a Record

Goal

Open a Person record and separate what you see into fields and values.

Open your Slate database in another tab and pull up a Person record you're permitted to view. Slowly read the record and notice the labels around the information — those labels are fields.

  • A name field and its value
  • A contact field (email or phone) and its value
  • A date field and its value
  • A field that is currently empty
  • A field whose value came from a form or import

For anything you found, you should be able to say it out loud in this shape:

Field

Birthdate

Value

March 14, 2007

Your Slate may look different

Slate is highly customizable. Your institution's tabs, fields, views, permissions, and processes may differ from examples used throughout Insider's Aid. Focus on understanding the concept rather than finding an identical screen.

Reflection

You looked at two different Person records. What was the same and what was different?

Apply

A Colleague Asks for a List

A colleague emails you: “Can you send me everyone who listed Nursing as their intended major?” You have access to build the list. What has to be true before you can build it?

What is the necessary first step?

Think Like a Slate User

Step 1

Record

Who or what

Step 2

Field

Where it's stored

Step 3

Value

What it says

Step 4

Use it

Find, report, automate

Once you know the field, you can
Filter a queryExport a columnPersonalize a mailingTrigger a ruleBuild a report

New users tend to ask: “Where do I click to see this?”

A stronger question is: “Which field stores this, and what value am I expecting to find there?”

Insider's Aid Tip

When a request feels vague, translate it into a field and a value. “Everyone who's incomplete” becomes “this field equals this value” — and suddenly it's buildable.

Put it together

Records and Fields Together

Lesson 01 gave you the container. Lesson 02 gives you what's inside it.

Record

The person

Field

The question

Value

Their answer

A record without fields would hold nothing. A field without records would apply to no one. Every tool you learn next — forms, queries, datasets, rules — is a different way of reading or writing values into fields on records.

Next up: Forms, the most common way values get into fields in the first place.

Reference

Keep Learning

Fields concept card
Concept Card

Fields

A field is where a single piece of information is stored about a record — the foundation of your data.

Records

Revisit what a record represents and why the Person record matters.

Forms

See how values get collected into fields in the first place.

Queries

Filter and export records based on field values.

Finished the lesson?

Mark it complete to track your progress. Progress is saved in this browser.

Slate Foundations progress0 of 7 lessons complete
Up next

Queries

Use criteria to identify the records that should—or should not—receive a communication.

Available