Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This page is designed to explain how SchoolEngage interacts with specific PASI fields that may cause confusion among users.

Infonote

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

...

How Updates and

...

Additions Work

...

Between SchoolEngage and PASI

When you writeback write back records in from SchoolEngage to PowerSchool, here’s what happensthe following process occurs:

1. Sending Data

...

SchoolEngage sends the updated data along with a specific flag

...

indicating whether the changes

...

Processing the Changes:

...

If it's an update: PASI will perform a sync that should pull the updated information into PASI.

...

should be treated as:

  • An Update: Modifies existing data.

  • An Addition: Adds new data.

2. Processing the Changes

  • Updates:
    PASI syncs the updated information, ensuring it reflects in PASI and PowerSchool.

  • 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.

3. 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 may be updated. During writeback an additional flag is sent indicating and add vs edit

...

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.