MollyMcEvilley
commented
10 months ago Notes:
102 Avg days to return after exit to street (this is all households who return after exit, regardless of system path) 23 Avg days to return after exit (all households regardless of system path) 36 Avg days to return after any system path (this excludes households with a system path of -1 – it is row 23 without those households) 24-35 Avg days to return after specific system paths (that are not -1)
It is possible to have row 102 without row 36; It is possible to have row 23 without row 36; and It is possible to have row 23 without rows 24-35.
JulesABrown
I'm getting a rejected error and I feel that it boils down to how 8.8/10 and 8.11 are set.
There is one client who in section 8.8/10 ends up getting dropped by the final where statement: AND (rv.RowID <> 36 OR ex.SystemPath <> -1)
The record has report row 36 and a system path of -1 which is what excludes them from populating a Report Row 36.
Now, in section 8.11, the client meets all of the join and where clause criteria. This is where they get picked up and set a ReportRow of 102. Here's how the data looks:
So there are a couple of questions here.
I think I have exhausted my knowledge here of looking for a data anomaly and need your input to see what might be going on. I'm not sure if the other errors with RowID 23 are related to this one or not, but this ticket is focused on the first error in the screenshot.