@rbs Using the same logic for the “catch all” part of the code for Transgender code transform, I updated the logic in the other branch of code that was only looking for specific gender codes, and stopping if it didn’t fit any of them properly which was resulting in the nulls you were seeing. It now properly finishes the logic path so we don’t end up with nulls any longer.

I’ve sent Michael that student selection so he can compare the FV_DEM_GET_GENDER code to the Banner values.

<redacted PII>
See above. These students have a transgender status of *B but are being returned as null for the gender code Michael worked on. I believe Transgender Status is the field you’re referencing. I’m working from warehouse verbiage, is what it is.

I do have concerns that i’m auditing against data elements that are not a source of truth, so my confidence is at 97%. I can discuss with you outside of Jira if youd like.

@rbs Can you be more specific, when you say “Transgender code” are you referring to SPBPERS_GNDR_CODE or

https://sequoias.atlassian.net/browse/GOVPUB-8? Also on your last sentence, what is labeled null? The FV_DEM_GET_GENDER value? Can you talk with us offline to share an example?

Bump on the below action. Might benefit from re-ordering the logic statement to work through non-binary and unknown, else return legal sex. I’ve done a bit of auditing and I believe there’s a small batch of students Transgender code B that are labeled as null.