[11:15:24 CDT(-0500)] <pspaude1> Jason do we have to fix how student_type sync behaves in light of SSP-1443?
[11:16:31 CDT(-0500)] <pspaude1> Basically if student_type is null or empty search doesn't work and caseload assignment has a visual fit.
[11:16:51 CDT(-0500)] <pspaude1> However, student_type_code sync was designed to set student_type to null if StudentTypeUnsetFromExternalData is true based on discussion during that issue.
[11:18:56 CDT(-0500)] <JasonElwood> setting to null should work fine
[11:19:10 CDT(-0500)] <JasonElwood> so you are saying that a null in the results blow things up
[11:20:09 CDT(-0500)] <pspaude1> Blows the caseload assignement appointment screen up yes, but that should be a bug I can fix.
[11:20:58 CDT(-0500)] <JasonElwood> cool. and search the same?
[11:21:09 CDT(-0500)] <pspaude1> However, student search doesn't work with student_type to null or empty per SSP-1443.
[11:21:49 CDT(-0500)] <pspaude1> So, we have a config option and potential for users to set the type to null from external data, and then when they do, they won't be able to find that student in search.
[11:22:05 CDT(-0500)] <JasonElwood> so this would only occur if a student were succesfully added with a student type (or coach for that matter) then unset = true and the student type were null in external data?
[11:22:36 CDT(-0500)] <pspaude1> Yes, or syncd over from external data and it was null in the first place.
[11:22:37 CDT(-0500)] <JasonElwood> and the sync over-wrote the selected value when the student was added
[11:22:47 CDT(-0500)] <pspaude1> yes
[11:22:49 CDT(-0500)] <JasonElwood> it can't be null in the first place
[11:22:56 CDT(-0500)] <JasonElwood> the UI requires a coach and type to add