Behavior Field Data Types in openSIS Explained

Understanding Behavior Field Data Types in openSIS

Overview

When creating custom Behavior Fields in openSIS, administrators must select an appropriate data type. The chosen data type determines how information is entered, stored, and displayed in behavior incident records.

This article explains the available behavior field data types and when to use each one.

Why Data Types Matter

Selecting the correct data type helps to:

  • Ensure consistent data entry

  • Improve clarity for staff recording incidents

  • Support better reporting and review

  • Avoid confusion or misuse of fields

Once a behavior field is created, its data type cannot be changed, so choosing correctly is important.

Available Behavior Field Data Types

openSIS currently supports the following data types for custom behavior fields:

Long Text

Description

  • Allows free-form text entry

  • Supports detailed explanations or notes

Best Used For

  • Incident descriptions

  • Counselor or administrator notes

  • Follow-up remarks

  • Observational comments

Example

  • Detailed Incident Notes

  • Counselor Remarks

Date

Description

  • Allows selection of a specific date

  • Uses the school’s configured date format

Best Used For

  • Follow-up dates

  • Review or hearing dates

  • Parent meeting dates

Example

  • Next Review Date

  • Parent Meeting Date

Description

  • Allows selection from predefined options

  • Ensures standardized responses

Best Used For

  • Status-based information

  • Categorized responses

  • Repeated values across incidents

Example

  • Parent Notified – Yes / No

  • Action Required – Counseling / Warning / Suspension

Choosing the Right Data Type

Requirement​
Recommended Data Type​
Detailed explanation
Long Text
Scheduled or follow-up date
Date
Standardized selection
Dropdown

Important Notes

  • Data types cannot be modified after field creation

  • Use dropdowns wherever consistency is required

  • Avoid long text fields for data that needs analysis or filtering

Best Practices

  • Plan field requirements before creating them

  • Keep dropdown options clear and limited

  • Avoid unnecessary free-text fields

  • Maintain consistency across behavior records

    • Related Articles

    • How to Access Behavior Fields Settings in openSIS

      Overview The Behavior Fields Settings section in openSIS allows administrators to view and manage all behavior-related fields used when recording student behavior incidents. This article explains where this setting is located and who can access it. ...

    • Understanding Behavior Fields in openSIS

      Overview Behavior Fields in openSIS allow schools to structure, document, and manage student behavior incidents in a consistent and configurable way. These fields define what information is captured when a behavior incident is recorded under the ...

    • How to Edit a Behavior Field in openSIS

      Overview openSIS allows administrators to edit existing behavior fields to keep behavior data aligned with school policies and operational needs. Editing a behavior field lets you update its title or display order without creating a new field. This ...

    • Sorting and Display Order of Behavior Fields in openSIS

      Overview In openSIS, Sort Order controls the sequence in which behavior fields appear on the Behavior Incident form. Proper ordering helps staff enter information efficiently and ensures that critical fields are noticed first. This article explains ...

    • How to Add a Custom Behavior Field in openSIS

      Overview Custom Behavior Fields in openSIS allow administrators to capture school-specific behavior information that is not covered by default fields. These fields help schools document additional details required by internal policies or reporting ...