AB PowerSchool Writeback ver.2

Overview

This page explains how SchoolEngage interacts with specific PASI fields, addressing potential areas of confusion for users.

Table of Contents

How Updates and Additions Work Between SchoolEngage and PASI

When you write back records from SchoolEngage to PowerSchool, the following process occurs:

Sending Data

SchoolEngage sends the updated data along with a specific flag indicating whether the changes should be treated as:

• An Update: Modifies existing data.

• An Addition: Adds new data.

Processing the Changes

In both updates and additions, the PowerSchool fields are edited.

• For Updates:
  PASI reads the flag sent with the data and pulls the updated information into PASI to sync with PowerSchool.

• For Additions:
  PASI reads the flag and retrieves the old data from its existing records, repopulating it in PowerSchool. At the same time, PASI creates a new record with the added data.

Monitoring Changes

To track data changes or troubleshoot issues:

• Use the PASI event queue to check if records have been processed or rejected.

Field-Specific Details

Addresses

During writeback, the system updates the relevant S_AB_STU_X and student.Address fields based on the selected action. A flag is sent to indicate whether the operation is an addition or an update.

Names

Names can be:

• Edited

• Ignored

Rules for Name Fields:

• Legal Name Fields: Always update the legal name.

• AKA Name Fields: Write to the AKA name fields (deprecated).

• Preferred Name Field Logic:

  • If the preferred indicator is mapped and the selected value is AKA, the AKA name will write to the preferred name field.

  • If the preferred indicator is mapped and the selected value is legal, the legal name will write to the preferred name field.

  • If the preferred indicator is not mapped:

    • The system defaults to the AKA or preferred name if available.

    • If both are empty, the legal name is used.