Overview
This page is designed to explain explains how SchoolEngage interacts with specific PASI fields that may cause confusion among , addressing potential areas of confusion for users.
| Note |
|---|
Important: Any MapSource with V2 in the name should not be used as that references the corresponding Child table, and will generally result in duplicate data |
...
Table of Contents
| 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 syncs reads the flag sent with the data and pulls the updated information , ensuring it reflects in PASI and into PASI to sync with PowerSchool.For Additions:
Initially, it may appear as though existing data in PowerSchool is removed. Once PASI completes its synchronization, the child table in PowerSchool repopulates with the original data, now including the newly added records.
...
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:
...