An eSchoolPlus Data Target delivers approved submission data to a customer's eSchoolPlus SIS through the selected SIS Connection. The Data Target contains matching and contact-handling settings, Target Records for the eSchoolPlus entities to deliver, and Field Mappings that supply destination values.
Create an eSchoolPlus Data Target by selecting eSchoolPlus as the Target type and selecting an available eSchoolPlus SIS Connection. The system creates the required eSchoolPlus Student Target Record with its default Field Mappings. Add the other Target Records needed for the district's delivery configuration, then configure their mappings and settings.
Simplified Match Logic Requirement
eSchoolPlus Data Targets use Simplified Match Logic. New eSchoolPlus Data Targets have Simplified Match Logic enabled by default.
When a user opens an existing eSchoolPlus Data Target that does not have Simplified Match Logic enabled, the system displays the Simplified Match Logic Required dialog before opening the detail page. Select Save to enable Simplified Match Logic and continue. Select Cancel to return to the Data Targets list without making a change.
eSchoolPlus Data Target Settings
Configure these settings in the Data Target drawer before or after configuring Target Records.
|
Section |
Settings |
Configuration Purpose |
|
General |
Allow unapproved records and Enhanced match criteria |
Controls the submission records available for delivery and the student matching behavior. |
|
Student |
Auto-match to student when one exact match found, Include inactive students, Student protective checks, Remove old student phones, and Display student location |
Controls how incoming student data is matched to and updated in eSchoolPlus student records. |
|
Contacts |
Contact matching, student scope, contact relationship, phone, and unlinking settings |
Controls how incoming contacts are matched and how existing contact relationships and phone data are handled. |
|
Documents |
Document matching set to Automatic or Manual |
Controls the document matching mode used by Documents Target Records. |
Auto-match to student when one exact match found is available when Enhanced match criteria is enabled.
eSchoolPlus Target Records
An eSchoolPlus Data Target always contains one required eSchoolPlus Student Target Record. Add other Target Records from the Data Target detail page as needed:
-
eSchoolPlus Contact
-
eSchoolPlus User Fields
-
eSchoolPlus Medical Alerts
-
eSchoolPlus Transportation
-
eSchoolPlus Documents
Refer to Default, Required, and Must-Exist Field Mappings for shared automatic default-mapping and subrecord behavior, including required and must-exist constraints.
Student Target Record
The system automatically creates an eSchoolPlus Student Target Record when an eSchoolPlus Data Target is created. It supports root student mappings plus Hispanic Code, Phone, and Race subrecords. The record cannot be deleted or duplicated.
The eSchoolPlus Student Target Record cannot be deleted or duplicated, and a second eSchoolPlus Student Target Record cannot be added to the same eSchoolPlus Data Target. Existing eSchoolPlus Data Targets that do not already contain a Student Target Record retain the option to add one manually.
Student Target Fields are organized into meaningful eSchoolPlus groups in the Field Mapping Target selector. These groups include student demographic, mailing and physical address, Entry/Withdrawal, phone, and race information. Mailing and physical address fields are shown separately so the configured mapping clearly identifies the destination address.
Contact Target Record
An eSchoolPlus Contact Target Record delivers contact data and supports root contact mappings with Phone subrecords. It includes default Field Mappings for common contact values.
Configure the Contacts settings before finalizing Contact mappings. Those settings determine the student scope used for matching, whether existing relationships or contacts are unlinked, and how existing phone records are handled.
User Fields Target Record
An eSchoolPlus User Fields Target Record delivers user-defined student field values through User Field subrecords.
Medical Alerts Target Record
An eSchoolPlus Medical Alerts Target Record delivers medical alert data through Medical Alert subrecords.
Transportation Target Record
An eSchoolPlus Transportation Target Record delivers transportation data through Trip subrecords.
Documents Target Record
An eSchoolPlus Documents Target Record delivers document attachment data through Document subrecords. Set the Data Target's Document matching mode to Automatic or Manual before configuring the document mappings.
The default Field Mappings reflect the selected matching mode. The eSchoolPlus SIS Connection must have Document Integration enabled before document delivery can be configured.
eSchoolPlus Field Discovery and Target Selection
The Field Mapping Target selector displays the eSchoolPlus fields applicable to the selected Target Record. Fields are grouped by their eSchoolPlus destination area so users can select the intended destination without working from internal table names.
Select the Target Record before adding or editing a Field Mapping so the selector loads the fields and subrecord groups for that record. If a required Target Field is missing or unavailable, use validation results to identify the affected Target Record and confirm that the selected eSchoolPlus connection and Target Record are correct.
Automatic Handling of Empty Records
When a record’s identifying value is empty, its remaining values are left empty automatically, and nothing is sent for a record that does not exist. This affects only values prepared for the delivery, not the saved Field Mapping configuration or existing SIS data.
When a record supports repeatable instances, such as subrecords or indexed records, only the instance with the empty identifying value is affected, and the other instances are left unchanged. In the internal names used below, “n“ represents the instance index, for example, the second phone or the third health concern.
In the following table, if the value in the Identifying Value column is empty in the delivery record, the expected outcome is that the fields in the Related Values Left Empty column are also left empty. The internal name is the identifier used in the underlying delivery configuration, while the customer-facing name is the label shown in the Field Mapping Target selector.
|
Target Record |
Identifying Value (Internal Name) |
Identifying Value (Customer-Facing Name) |
Applies When |
Related Values Left Empty |
|---|---|---|---|---|
|
Student, Phone subrecord |
StudentContact/AddressAndPhone/Phones[n]/PhoneNumber |
Phone Number |
The value is empty or not provided for the same phone instance |
All other Field Mappings in that Phone instance |
|
Contact |
FirstName and LastName |
First Name and Last Name |
Both values are empty or not provided |
All other Field Mappings in the Contact Target Record, including its Phone subrecords |
|
Contact, Phone subrecord |
AddressAndPhone/Phones[n]/PhoneNumber |
Phone Number |
The value is empty or not provided for the same phone instance |
All other Field Mappings in that Phone instance |
|
Documents, Manual matching |
doc_File |
File |
The value is empty or not provided |
All other Field Mappings in the Documents Target Record |
|
Documents, Automatic matching |
docn_File |
File |
The value is empty or not provided for the same document instance |
All other Field Mappings in that Document instance |
|
User Fields |
usern_Field |
Field |
The value is empty or not provided for the same instance |
All other Field Mappings in that User Field instance |
|
Medical Alerts |
medAlertn_Code |
Code |
The value is empty or not provided for the same instance |
All other Field Mappings in that Medical Alert instance |
|
Transportation |
traveln_Type |
Travel Type |
The value is empty or not provided for the same instance |
All other Field Mappings in that Trip instance |