This article covers the concept of Scope as it relates to objects in a Slate database.  

A Slate database has many standard and custom object types that store record data. Each object type has a stored relationship with a particular record, known as its scope. The relationship created through using scope will, for example, ensure data scoped to a person record stays connected to a person's record and is not available for use with other objects.  


Object Relations

Objects can have their own scope and be related to other objects in the database. Objects like gifts, addresses, devices, jobs, etc., are scopes unto themselves yet are also associated with Person/Dataset/Relation records. In the everyday vernacular of Slate, these objects might be referred to in the context of the record on which they reside. 

For example, a constituent's address can be referred to as a person-scoped address since the address data is related to the person record upon which the address data resides. Likewise, a company's address can be referred to as Companies and Foundations scoped since the address resides with a record in the Companies and Foundations dataset.


Field Scope Examples

Person Scope

To capture a primary constituency type for a person record, the field would need to have the scope set to person. With the relation between the field and the person established, the database can then treat the data stored in the field as if it was stored on the person record.  


With the Primary Constituent Type custom field scoped to person will ensure that the field is only available for person records in other areas of the database.

Gift Scope

Capturing a stock symbol for a gift would require a custom gift-scoped field. As with the person example above, with the relationship established between the gift and the custom field, the database can treat the data stored in the custom field as if it was stored on the gift.  


The Stock Symbol custom field scoped to gift will ensure that the field is only available for gifts in other areas of the database.


Form Scope Examples

Primary Form Scope

Form submissions are another example of an object linked to another object through scope. 

When creating a form, scope is used to determine which primary object types in the database the form should have a relationship with. A form scoped to person will relate the form to a person record in the database. The primary relationship through the form scope will also determine the object the form submission will reside with. 

For example, an online giving form scoped to person when submitted will reside with the person record the form is submitted for.  


With a primary scope of a form established, the database can then determine which other objects should be accessible for the form. While gifts have their own scope, gifts can also be related to a person or dataset record. Gift fields added to a form scoped to person will create a relationship between the gift fields and the person record for which the form is being submitted. Likewise, if the form's primary scope is to a specific dataset, like Companies and Foundations, any gift fields added to the form would relate to the dataset record for which the form is being submitted.   

Subgrouping Scoped Objects

When scope relates to an object that encompasses subsets of grouped data, the dataset scope, for example, then there will be an additional option to relate the scope to one of the subsets of data. In the example below, the Scope of Dataset has been selected, followed by the subset of Companies and Foundations.


Was this article helpful?
0 out of 1 found this helpful