District Validation During Roster Sync No Longer Blocks Edge Cases
Roster sync workflows that span multiple schools within a district involve a validation step that checks whether the district identifier in the incoming data matches what's configured in PTC Wizard. In certain edge cases—particularly when schools are newly added to a district account or when the source data includes variations in how the district identifier is formatted—this validation step failed and blocked the sync entirely.
What changed in district validation
The district ID validation logic now handles these edge cases gracefully. Newly added schools complete their first sync without requiring a support ticket to adjust configuration. Variations in district identifier formatting that previously caused hard stops are now normalized before validation runs.
If your district has experienced blocked syncs during onboarding of new buildings, this fix should resolve the pattern. We recommend running a test sync for any school that previously required a workaround and reviewing the sync log to confirm a clean import.