Closed nataliesus closed 9 months ago
@MollyMcEvilley This change results in an error for SQL Servers Msg 8124, Level 16, State 1, Line 7837 Multiple columns are specified in an aggregated expression containing an outer reference. If an expression being aggregated contains an outer reference, then that outer reference must be the only column referenced in the expression.
@jbloescw did you have a fix for this? (Or has it been fixed?)
@eanders There was another push Molly did that rearranged the query in a way where SQL does not error out. It compiled and gave me the all clear.
@jbloescw thank you!
Hi @MollyMcEvilley ,
Step 7.9.2 was updated recently. I would like to confirm with you the current logic for [HHDisability]:
hhid.HoHID = disability.PersonalID
is OK, and we do not need to usedisability.RelationshipToHoH = 1
instead;ex.Cohort
which was added recently, and notcd.Cohort
as it was done for [HHFleeingDV];coalesce( ..., 0 )
condition. I wonder if we do not need the same condition for [HHDisability] as well to cover cases when client is not HoH and not adult (now [HHDisability] is NULL in this case, but according to the spec it should be 0 )Thank you! Natalie