HMIS / LSASampleCode

Longitudinal System Analysis (LSA) Sample Code and Documentation
22 stars 10 forks source link

LSA Upload Error - HHFleeingDV #1320

Closed TanyaPieterse closed 2 weeks ago

TanyaPieterse commented 4 weeks ago

Hi, I am testing our LSA Uploads, and we are receiving this error indicating an incorrect value for HHFleeingDV. Our CSV files have the value "3" in the rows indicated.

image

The list in the Data Dictionary indicates only values 0, 1, and 2.

image

I am using Molly's lates code on GitHub (THANK YOU SO MUCH MOLLY, it is a life saver!!!).

Script 07 looks for DVStatus between 1 and 3 on tlsa_Enrollment:

image

This lines up with the LSA Specifications indicating for tlsa_Exit the values can be 1, 2, or 3.

image

I believe the HUD HDX should not be flagging this as an error and the list in the LSA Dictionary should be updated.

Thanks,

cwanska commented 3 weeks ago

@MollyMcEvilley it looks like this is actually a disconnect between the LSA Data Dictionary and the code so I'm assigning to you to take a look.

MollyMcEvilley commented 3 weeks ago

I am about to commit the very most current version of the Dictionary with the value for 3. I am not sure when that got out of sync.

MollyMcEvilley commented 3 weeks ago

Actually, I'm going to re-open this and send it back to you for the HDX dictionary update... :)

cwanska commented 2 weeks ago

The change to the data dictionary has been implement on HDX.

JessFleming commented 2 weeks ago

@cwanska - I'm still getting a file rejection when uploading to HDX when HHFleeingDV is 3. I attempted an upload on Friday 10/18 and again today, Monday 10/21.

cwanska commented 2 weeks ago

@JessFleming I'm seeing the same and sorry for the false start here. I am working with the developer and reopening this ticket and figured out how to replicate this issue so I can better test before passing back.

cwanska commented 2 weeks ago

@JessFleming this has been updated and I retested and am now able to upload a file with HHFleeingDV value of 3 in LSAExit. It turns out I updated our dictionary in the wrong place and that was the culprit.