A PowerSchool SIS Data Target delivers approved submission data to a customer's PowerSchool SIS through the selected SIS Connection. The Data Target contains the settings that control student and contact matching, the Target Records that identify the SIS entities to deliver, and the Field Mappings that supply destination values.
Create a PowerSchool SIS Data Target by selecting PowerSchool SIS as the Target type and selecting an available PowerSchool SIS Connection. The system creates the required Student Target Record with its default Field Mappings. Add other Target Records, configure their mappings and settings, then use Sync & Validate to refresh SIS metadata and validate the complete configuration.
PowerSchool SIS 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, "Deliver Now" mode, Enhanced match criteria, "Permissive Delivery" mode, and Allow "Deliver All" records. |
Controls which submission records can be delivered and which delivery modes are available. |
|
Student |
Auto-match to student when one exact match found, Include inactive students, Include historical students, Student protective checks, Matched students are undeliverable, Prohibit new student creation, and Use pre-assigned student numbers for new students. |
Controls how incoming student data is matched to existing PowerSchool SIS students and how the target handles new or matched students. |
|
Contacts |
Contact matching, contact relationship, address, email, and phone handling settings. |
Controls how incoming contacts are matched to existing contacts and how existing related data is retained, ended, or removed. |
|
Documents |
Document matching set to Automatic or Manual. |
Controls the document matching mode used by Document Target Records. |
Auto-match to the student when one exact match found is available when Enhanced match criteria is enabled.
PowerSchool SIS Target Records
Each PowerSchool SIS Target Record represents one SIS entity or record group. A PowerSchool SIS Data Target always contains one required Student Target Record. Add other Target Records from the Data Target detail page as needed.
Refer to Default, Required, and Must-Exist Field Mappings for the shared default-mapping and constraint behavior used by PowerSchool SIS Target Records.
Student Target Record
The system automatically creates a Student Target Record when a PowerSchool SIS Data Target is created. The Student Target Record includes default Field Mappings for commonly used student fields.
The Student Target Record cannot be deleted or duplicated, and a second Student Target Record cannot be added to the same PowerSchool SIS Data Target. Configure its Field Mappings to supply the student values required by the district's delivery configuration.
Contact Target Record
A Contact Target Record delivers guardian and contact data. It supports root contact mappings and nested Address, Phone, and Email subrecords. Required relationship mappings are applied when Calculate original contact types is enabled.
Required relationship mappings are applied when Calculate original contact types is enabled. Configure the Data Target's Contacts settings before finalizing Contact mappings because those settings control matching, relationship handling, and removal behavior.
Student Extension Target Record
A Student Extension Target Record delivers data to a customer-specific PowerSchool SIS extension table. Select the required Table name from the extension tables discovered through metadata sync. A table that is not available in the list cannot be selected until it is returned by a successful metadata sync.
Extension configuration supports one-to-one and one-to-many extension behavior. For one-to-many extensions, configure the matching criteria that determines how delivered records match existing extension rows. Available configuration includes exact-match and potential-match behavior, match-window columns, removal behavior, and tie handling.
Race and Ethnicity Target Record
A Race/Ethnicity Target Record delivers student race and ethnicity data through Race subrecords. Choose the Race behavior that determines whether delivery appends to or replaces the applicable race data.
Fees Target Record
A Fees Target Record delivers fee data through Fee subrecords. Select the applicable Fee type: Student Fee, Course Fee, or School Fee.
Health Target Records
PowerSchool SIS provides three health-related Target Record types:
-
Health Concerns delivers health concern data through Health Concern subrecords. Its settings include Set 'Show Concern in Alert' to false, Set 'Show Comment in Alert' to false, and End Old Health Concerns.
-
Medications delivers medication data through Medication subrecords. Its settings include End Old Health Medications.
-
Health Misc delivers other health-related data through its available Field Mappings.
These Target Records can also use configured one-to-one extensions where applicable.
Documents Target Record
A 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.
PowerSchool SIS Schema Discovery
PowerSchool SIS Field Mapping targets come from two sources:
-
Core fields are available for standard PowerSchool SIS entities without a metadata sync.
-
Discovered fields are customer-specific extension tables and columns returned from the district's PowerSchool SIS and cached for configuration use.
Use Sync & Validate on the Data Target detail page to refresh available PowerSchool SIS metadata and validate the configuration in one operation. The system also refreshes metadata when a PowerSchool SIS Data Target is created or when its SIS Connection changes. Use an inline sync action when one is available beside an extension-table or extension-field selection.
After a successful sync, the Data Target displays Last SIS Table/Column Metadata Fetch. If an expected extension table or field does not appear, refresh the metadata and confirm that the table or field exists in the customer's PowerSchool SIS. A mapping that references a Target Field no longer available in the customer's SIS is reported during validation.
PowerSchool SIS Extension Mappings
Beginning with PowerSchool SIS version 26.9.0.0, extension mappings are retrieved automatically during metadata synchronization. The required functionality is included with the PowerSchool SIS upgrade and cannot be installed separately.
Customers running a PowerSchool SIS version earlier than 26.9.0.0 must use manual extension mappings when an extension’s Extension Table Name differs from its Extension Group Name. The Extension Table Name identifies the table returned by the metadata sync, while the Extension Group Name is the name required to configure and deliver data to that extension.
The PowerSchool SIS Extension Mappings section appears on the SIS Credentials page only after extension metadata has synchronized for the selected PowerSchool SIS connection. It is available only for connections previous to version 26.9.0.0.
A District Administrator can create and maintain these mappings for the customer's SIS connection. Create a mapping only when the Extension Table Name and Extension Group Name differ. No mapping is needed when both names are the same.
Creating and Maintaining Manual Mappings
-
Open the customer's SIS Credentials page for the applicable PowerSchool SIS connection.
-
Confirm that extension metadata has synchronized. The manual mapping section is not available until the sync completes.
-
In PowerSchool SIS Extension Mappings, select Add Mapping.
-
Select the Extension Table Name returned by the completed metadata sync.
-
Enter the corresponding Extension Group Name used by the customer's PowerSchool SIS.
-
Select Save.
Mappings are scoped to the selected SIS connection and are immediately available to Data Targets. A connection cannot contain duplicate Extension Table Names or duplicate Extension Group Names. The same Extension Table Name cannot be used as its Extension Group Name because that pairing does not require a manual mapping.
Use Edit to correct an unused mapping or Delete to remove one that is no longer needed. A mapping referenced by a Data Target or Data Source is marked In use and cannot be edited or deleted until those references are removed.
When the Customer Upgrades to PowerSchool SIS 26.9.0.0 or Later
After the customer upgrades and the connection synchronizes successfully, Enrollment uses the extension mappings returned by PowerSchool SIS. The manual mapping section no longer appears on the SIS Credentials page. After the upgrade, run Sync & Validate for affected PowerSchool SIS Data Targets and confirm that each Student Extension Target Record and its Field Mappings show the expected extension and columns.
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 |
|---|---|---|---|---|
|
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 Address, Email, and Phone subrecords |
|
Contact, Address subrecord |
addresses[n]/street, addresses[n]/linetwo, and addresses[n]/unit |
Street, Line Two, and Unit |
All three values are empty or not provided for the same address instance |
All other Field Mappings in that Address instance |
|
Contact, Email subrecord |
emails[n]/address |
Email Address |
The value is empty or not provided for the same email instance |
All other Field Mappings in that Email instance |
|
Contact, Phone subrecord |
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 |
|
Health Concerns |
n_healthConcern |
Health Concern |
The value is empty or not provided for the same instance |
All other Field Mappings in that Health Concern instance |
|
Medications |
n_medicationName |
Medication Name |
The value is empty or not provided for the same instance |
All other Field Mappings in that Medication instance |
|
Fees (Student Fee, Course Fee, School Fee) |
feen_TypeID |
Fee Type |
The value is empty or not provided for the same fee instance |
All other Field Mappings in that Fee instance |
|
Fees (Student Fee, Course Fee, School Fee) |
feen_Transaction1_Amount |
Transaction Amount |
The value is empty or not provided for the same transaction instance |
All other Field Mappings in that transaction instance |