Status

Set the status to 'Active' for currently used Fields.

Inactivate fields that are no longer used without fear of losing data associated with them.

Scope Category

The available scopes will dynamically show based on the category selected.

Records: The Records category includes primary records in the database, like constituent and dataset records.

Related: The Related category includes objects that have to be associated with a primary record, such as gifts, addresses, jobs, etc.

Scope

Scope describes the object to which the field is related.

Do not change the scope of a field once data exists for the field. Changing the scope of a field will not update existing values, resulting in orphaned data. Also, existing filters and exports will continue referencing data with the original scope. If data should be scoped differently, create a new field with the desired scope. Then, export the existing data and import it to the new field using Upload Dataset.

ID 

This is the unique ID that Slate will use to identify specific fields in the database. Each field must have a different ID.

It is best practice to have this ID be all lowercase with no spaces or special characters other than an underscore.  

Once this ID is set and in use, you should never change the ID. 

Name

Give the field a name. This name will be visible administratively only. It is acceptable to change the name, even if data already exists for the field.

Folder

Adding fields to folders provides for better organization and filtering options. Select a folder or select Other and enter the name of a new folder. It is highly recommended to organize your content with folders.

Category

Select an existing category or select Other and enter a new category for the field. Fields can be queried by using category.

Field Type

Select one of the listed field types.

• Free Text: Select Free Text when storing a response that does not require a predetermined list of values. For example, if you ask someone about their favorite book, there are too many to list in a drop-down. Instead, ask the person to provide their answer using free text.

• Single Value: If a record should only have one associated value, set this to Single Value. This means that if the field is gift scoped and configured to store a single value, each gift on a record can have one value for this field.  

• Multiple Values: If a field can have more than one associated value, set this to Multiple Values. 

• Bit: When looking to store a yes/no response. Note: Do not create prompts for Yes/No values; use the Bit (Yes/No) field setting instead. 

• Related Dataset Row: A related dataset row field allows a record (a constituent record or a dataset record) to be linked to a record in a different dataset. Select a related dataset from the Related Dataset setting; leaving the related dataset blank will relate the field to the constituent records.

• Dataset Row key: When selected along with the scope of a dataset, a field configured with a type of Dataset Row Key enables renaming the selected datasets default key field in Slate. 

• Dataset Row Query: A dataset row query enables related data to appear on a dataset record. For example, a Company dataset record could also show a list of constituent records currently employed at the company.

• Dataset Row Address (Retired)

• Dataset Row Location (Retired)

• Dataset Row Interactions (Retired)

• Custom Configuration (Advanced User Only): Enables some field settings to be overwritten. For example, setting up a field that uses a prompt list and is also unique for matching.

Depending on the type selected, additional configuration fields may appear.

Prompt

Select from any prompt lists that are available within your database. Prompt lists are agnostic to scope.  

Ordered

This setting is available for fields that store multiple values. This setting is used for field values that are grouped together.

• Unordered Values: This field value should typically be set to Unordered values.  

• Order Values: Fields that use a replicate widget and can be associated with other fields will use the setting Ordered values.

Appendable

This setting is available for fields that store multiple values. This will set the behavior for form submission or data imports for the field when a value for this field already exists for a record.

• Replace existing values upon form submission or dataset import: This option will remove all of this field's values for the record that are not included in the new set of selected values and then add the new selected values.

  For example, a constituent interest field exists and stores multiple values, and the record already has the values of Golf and Fishing. When importing Golf and Travel, the values on the record will become Golf and Travel.

• Append to existing values upon form submission or dataset import: This option will keep all existing field values for the record intact and add the newly selected values.

  For example, a constituent interest field exists and stores multiple values, and the record already has the values of Golf and Fishing. When importing Golf and Travel, the values on the record will become Golf, Fishing, and Travel.

Unique for Merging

Use this setting with caution.

When configured as Value containing a unique ID that identifies a single record for merging, Upload Dataset and Form/Event/Interview submissions will use this field's value to match records automatically. Consolidate Records will also use this field to find potential matching records. Fields should only be configured as unique if each record is guaranteed to have a unique value for this field.

Examples of unique fields include:

• SIS IDs, including Banner ID, EmplID, ColleagueID

[Advancement Only] Giving Tabs Insert

When the scope of Gift is selected, the Giving Tabs Insert setting will appear.

The Gift scope covers Gifts, Pledged, and Planned gifts. When no tab is selected, the field will appear for all giving tabs. Selecting specific tabs will display the field only for those chosen giving tabs.

[Advancement Only] Giving Tabs

When the scope of Gift is selected, the Giving Tabs setting will appear.

This setting will display any giving tabs selected in the Giving Tabs Insert setting.

Unsafe

• Unsafe: If a field is configured as Unsafe, then the safe setting for files uploaded through Upload Dataset and form submissions will always be ignored for that particular field. The Unsafe setting means that the field value will be updated by a source/form submission, even if the record has an application in an active application period.

• Safe: Since applicants will give accurate information when completing an application, the Safe setting will protect biographical data, such as race/ethnicity, from being updated by less accurate sources.

Application-scoped fields are always considered Unsafe.

Data Type

This setting provides the ability to specify if the field will contain free text or will conform to specific types of values. Filters will become available in the Slate Template Library for text-based fields based on the Data Type selected. Numeric types (Real, Int), as well as Date and Date/Time types, will be available as filters with comparison operators (<, <=, =, >=, >).    

XML Configuration Data

This is a legacy setting previously used to drive conditional logic on legacy XSLT application pages. This can now be handled on each form in a less technical format via forms.

Read Permission

This optional setting restricts the ability to view particular fields on a tab by setting a custom read permission. If the setting is blank, anyone who can view the field's tab on the record can see the value of this field.

Write Permission

This optional setting restricts the ability to edit particular fields on a tab by setting a custom write permission. If the setting is blank, anyone who can view the field's tab on the record can update the field value.