Parent email addresses are stored in a custom table that does not connect 1:1 with the guardianid table.
All matches have to go through first/last name. First/last names in guardians and custom table are inconsistent.
This means that using guardian ID for an org defined id will not intrinsically work.
Alternatives:
use email address as org defined id
remove auditor relationship entirely and only use read-only login for parents
For read only option, it will be necessary to only create accounts for parents that pass the first/last match. Need to document this heavily so we can fix this for parents without accounts. Need advice as to where on the SIS front end this data is entered.
Parent email addresses are stored in a custom table that does not connect 1:1 with the guardianid table.
All matches have to go through first/last name. First/last names in guardians and custom table are inconsistent.
This means that using guardian ID for an org defined id will not intrinsically work.
Alternatives:
For read only option, it will be necessary to only create accounts for parents that pass the first/last match. Need to document this heavily so we can fix this for parents without accounts. Need advice as to where on the SIS front end this data is entered.