Release Notes
      Back to home
      1. Clarity Human Services Help Center
      2. Data Analysis
      3. Release Notes

      Data Analysis Release Notes 6/20/2023

      Release Notes Summary:

       

      The changes outlined here will be released to Looker training instances on 6/6/23 and production and migration instances on 6/20/23. There may be changes to this article until the release date. 

       

      General Notes: 

       

      When looks and dashboards are deleted by users they go to the trash and cannot be used but can still appear in the embedded data analysis reports section. We will be hard deleting all soft deleted items that have been in the trash for longer than 3 months by July 3rd, 2023. Moving forward, deleted looks and dashboards over 3 months old will be deleted on a quarterly basis.

       

      Required Action: Users should reach out to the Help Desk by 6/16 to restore any items they believe may have been deleted in error.

       

      LookML Dashboards: No changes

      Coordinated Entry Model: No changes

      Client Model: 

      • Added new Service Expenses and Service Attendance Dates Fields. 

       

      HMIS Performance Model: 

      • Added new Service Expenses and Service Attendance Dates Fields. 
      • Addressed bugs in Household Income sources. 
      • Addressed a bug in the Assessing Program Field

       

      Services Model: 

      • Added new Service Expenses and Service Attendance Dates Fields. 

       

      Inventory Model: No changes

       

      Data Quality Model: 

      • Corrected labels on "Reason Not Receiving HIV AIDS Medical Assistance Errors Count" Field

       

      Outreach Model: 

      • Added Encampment CoC to “Encampments” and “Encampment Stays” Views.
      • For embedded users, now only Encampment Stays created by Agencies within the same CoC as the Home Agency of the user can be seen. 

       

      Detailed Notes: 

       

      LookML Dashboards: No changes

       

      Coordinated Entry Model: No changes

       

      Client Model: 

       

      The "Service Attendance Dates" and "Service Expenses" sections have been improved to provide information about how the attendance dates and the expenses are connected. A group called “Attendance Dates” has been added in the “Service Expenses” View. Attendance Dates are joined to Service Expenses based on Service Attendance Date ID linked to the service expense. 

       

      A group called “Expenses” has been added in the “Service Attendance Dates” View. Service Expenses are linked to Service Attendance Dates based on the Service Attendance Date ID. 

       Both sections can work independently of each other, but it is recommended to not include dimensions or measures from both sections on the same query because it can cause issues with performance. 

       

      The "Service Attendance Dates" View has a new "Expenses" group that includes the necessary dimensions or measures to get all the expense information connected to each service attendance date record. The "Service Expenses" View has a new "Attendance Dates" dimension group that allows the user to get extra information about expenses connected to a service attendance date record. 

       

      New Fields: 

      • Field Name: expenses_service_dates.date_date, Location: “Service Expenses:Attendance Dates:Attendance Date”
      • Field Name: expenses_service_dates.date_month, Location:  “Service Expenses:Attendance Dates:Attendance Month”
      • Field Name: expenses_service_dates.date_quarter, Location:  “Service Expenses:Attendance Dates:Attendance Quarter”
      • Field Name: expenses_service_dates.date_year, Location:  “Service Expenses:Attendance Dates:Attendance Year”
      • Field Name: expenses_service_dates.id, Location:  “Service Expenses:Attendance Dates:ID”
      • Field Name: expenses_service_dates.time_of_service,  Location:  “Service Expenses:Attendance Dates:Time of Service”
      • Field Name: expenses_service_dates.total_attendance_dates,  Location:  “Service Expenses:Attendance Dates:Total Dates:”
      • Field Name: expenses_service_dates.ref_user, Location: “Service Expenses:Attendance Dates: User Creating”
      • Measure Name: expenses_service_dates.count,  Location: “Service Expenses:Measures:Attendance Dates:Count”
      • Measure Name: expenses_service_dates.total_amount,  Location: “Service Expenses:Measures:Attendance Dates:Total Amount”
      • Field Name: attendance_service_expenses.amount,  Location: “Service Attendance Dates:Expenses:Amount”
      • Field Name: attendance_service_expenses.check_number,  Location: “Service Attendance Dates:Expenses:Check Number”
      • Field Name: attendance_service_expenses.added_date,  Location: “Service Attendance Dates:Expenses:Expenses Added Date”
      • Field Name: attendance_service_expenses.added_month,  Location: “Service Attendance Dates:Expenses:Expenses Added Month”
      • Field Name: attendance_service_expenses.added_quarter,  Location: “Service Attendance Dates:Expenses:Expenses Added Quarter”
      • Field Name: attendance_service_expenses.added_time,  Location: “Service Attendance Dates:Expenses:Expenses Added Time”
      • Field Name: attendance_service_expenses.added_week,  Location: “Service Attendance Dates:Expenses:Expenses Added Week”
      • Field Name: attendance_service_expenses.added_year,  Location: “Service Attendance Dates:Expenses:Expenses Added Year”
      • Field Name: attendance_service_expenses.date_date,  Location: “Service Attendance Dates:Expenses:Expenses Date”
      • Field Name: attendance_service_expenses.date_month,  Location: “Service Attendance Dates:Expenses:Expenses Month”
      • Field Name: attendance_service_expenses.date_quarter,  Location: “Service Attendance Dates:Expenses:Expenses Quarter”
      • Field Name: attendance_service_expenses.date_Week,  Location: “Service Attendance Dates:Expenses:Expenses Week”
      • Field Name: attendance_service_expenses.date_Year,  Location: “Service Attendance Dates:Expenses:Expenses Year”
      • Field Name: attendance_service_expenses.id,  Location: “Service Attendance Dates:Expenses:ID”
      • Field Name: attendance_service_expenses.notes,  Location: “Service Attendance Dates:Expenses:Expenses Date:Notes”
      • Field Name: attendance_service_expenses.vendor,  Location: “Service Attendance Dates:Expenses:Vendor”
      • Measure Name: attendance_service_expenses.count,  Location: “Service Attendance Dates:Measures:Expenses:Count”
      • Measure Name: attendance_service_expenses.total_amount,  Location: “Service Attendance Dates:Measures:Expenses:Total Amount”

       

      Required Actions: None

       

      HMIS Performance Model: 

       

      A bug was addressed so that “Entry Screen:Total Income Sources and Amounts:Total Household Income”, “Entry Screen:Total Income Sources and Amounts:Total Household Annual Income”, and “Entry Screen:Total Income Sources and Amounts:Area Median Income” only pull from households that are active within the Reporting Period Filter. 

       

      A bug was addressed so that deleted enrollments no longer appear as a null row when linked to assessments in the “Client Assessments:Assessing Program” field.

       

      The "Service Attendance Dates" and "Service Expenses" sections for Client, HMIS Performance and Services model has been improved to provide information about how the attendance dates and the expenses are connected. Both sections can work independently of each other, but it is recommended to not pick dimensions or measures from both sections on the same query because it can cause issues with performance. 

       

      The "Service Attendance Dates" View has a new "Expenses" group that includes the necessary dimensions or measures to get all the expense information connected to each service attendance date record. The "Service Expenses" View has a new "Attendance Dates" group that allows the user to get extra information about expenses that are connected to a service attendance date record.

       

      New Fields: 

      • Field Name: expenses_service_dates.date_date, Location: “Service Expenses:Attendance Dates:Attendance Date”
      • Field Name: expenses_service_dates.date_month, Location:  “Service Expenses:Attendance Dates:Attendance Month”
      • Field Name: expenses_service_dates.date_quarter, Location:  “Service Expenses:Attendance Dates:Attendance Quarter”
      • Field Name: expenses_service_dates.date_year, Location:  “Service Expenses:Attendance Dates:Attendance Year”
      • Field Name: expenses_service_dates.id, Location:  “Service Expenses:Attendance Dates:ID”
      • Field Name: expenses_service_dates.time_of_service,  Location:  “Service Expenses:Attendance Dates:Time of Service”
      • Field Name: expenses_service_dates.total_attendance_dates,  Location:  “Service Expenses:Attendance Dates:Total Dates:”
      • Field Name: expenses_service_dates.ref_user, Location: “Service Expenses:Attendance Dates: User Creating”
      • Measure Name: expenses_service_dates.count,  Location: “Service Expenses:Measures:Attendance Dates:Count”
      • Measure Name: expenses_service_dates.total_amount,  Location: “Service Expenses:Measures:Attendance Dates:Total Amount”
      • Field Name: attendance_service_expenses.amount,  Location: “Service Attendance Dates:Expenses:Amount”
      • Field Name: attendance_service_expenses.check_number,  Location: “Service Attendance Dates:Expenses:Check Number”
      • Field Name: attendance_service_expenses.added_date,  Location: “Service Attendance Dates:Expenses:Expenses Added Date”
      • Field Name: attendance_service_expenses.added_month,  Location: “Service Attendance Dates:Expenses:Expenses Added Month”
      • Field Name: attendance_service_expenses.added_quarter,  Location: “Service Attendance Dates:Expenses:Expenses Added Quarter”
      • Field Name: attendance_service_expenses.added_time,  Location: “Service Attendance Dates:Expenses:Expenses Added Time”
      • Field Name: attendance_service_expenses.added_week,  Location: “Service Attendance Dates:Expenses:Expenses Added Week”
      • Field Name: attendance_service_expenses.added_year,  Location: “Service Attendance Dates:Expenses:Expenses Added Year”
      • Field Name: attendance_service_expenses.date_date,  Location: “Service Attendance Dates:Expenses:Expenses Date”
      • Field Name: attendance_service_expenses.date_month,  Location: “Service Attendance Dates:Expenses:Expenses Month”
      • Field Name: attendance_service_expenses.date_quarter,  Location: “Service Attendance Dates:Expenses:Expenses Quarter”
      • Field Name: attendance_service_expenses.date_Week,  Location: “Service Attendance Dates:Expenses:Expenses Week”
      • Field Name: attendance_service_expenses.date_Year,  Location: “Service Attendance Dates:Expenses:Expenses Year”
      • Field Name: attendance_service_expenses.id,  Location: “Service Attendance Dates:Expenses:ID”
      • Field Name: attendance_service_expenses.notes,  Location: “Service Attendance Dates:Expenses:Expenses Date:Notes”
      • Field Name: attendance_service_expenses.vendor,  Location: “Service Attendance Dates:Expenses:Vendor”
      • Measure Name: attendance_service_expenses.count,  Location: “Service Attendance Dates:Measures:Expenses:Count”
      • Measure Name: attendance_service_expenses.total_amount,  Location: “Service Attendance Dates:Measures:Expenses:Total Amount”

       

      Required Actions: None

       

      Services Model: 

       

      The "Service Attendance Dates" and "Service Expenses" sections for Client, HMIS Performance and Services model has been improved to provide information about how the attendance dates and the expenses are connected. Both sections can work independently of each other, but it is recommended to not pick dimensions/measures from both sections on the same query because it can cause issues with performance. 

       

      The "Service Attendance Dates" View  has a new "Expenses" group that includes the necessary dimensions/measures to get all the expense information connected to each service attendance date record. The "Service Expenses" View has a new "Attendance Dates" group that allows the user to get extra information about expenses that are connected to a service attendance date record.

      New Fields: 

      • Field Name: expenses_service_dates.date_date, Location: “Service Expenses:Attendance Dates:Attendance Date”
      • Field Name: expenses_service_dates.date_month, Location:  “Service Expenses:Attendance Dates:Attendance Month”
      • Field Name: expenses_service_dates.date_quarter, Location:  “Service Expenses:Attendance Dates:Attendance Quarter”
      • Field Name: expenses_service_dates.date_year, Location:  “Service Expenses:Attendance Dates:Attendance Year”
      • Field Name: expenses_service_dates.id, Location:  “Service Expenses:Attendance Dates:ID”
      • Field Name: expenses_service_dates.time_of_service,  Location:  “Service Expenses:Attendance Dates:Time of Service”
      • Field Name: expenses_service_dates.total_attendance_dates,  Location:  “Service Expenses:Attendance Dates:Total Dates:”
      • Field Name: expenses_service_dates.ref_user, Location: “Service Expenses:Attendance Dates: User Creating”
      • Measure Name: expenses_service_dates.count,  Location: “Service Expenses:Measures:Attendance Dates:Count”
      • Measure Name: expenses_service_dates.total_amount,  Location: “Service Expenses:Measures:Attendance Dates:Total Amount”
      • Field Name: attendance_service_expenses.amount,  Location: “Service Attendance Dates:Expenses:Amount”
      • Field Name: attendance_service_expenses.check_number,  Location: “Service Attendance Dates:Expenses:Check Number”
      • Field Name: attendance_service_expenses.added_date,  Location: “Service Attendance Dates:Expenses:Expenses Added Date”
      • Field Name: attendance_service_expenses.added_month,  Location: “Service Attendance Dates:Expenses:Expenses Added Month”
      • Field Name: attendance_service_expenses.added_quarter,  Location: “Service Attendance Dates:Expenses:Expenses Added Quarter”
      • Field Name: attendance_service_expenses.added_time,  Location: “Service Attendance Dates:Expenses:Expenses Added Time”
      • Field Name: attendance_service_expenses.added_week,  Location: “Service Attendance Dates:Expenses:Expenses Added Week”
      • Field Name: attendance_service_expenses.added_year,  Location: “Service Attendance Dates:Expenses:Expenses Added Year”
      • Field Name: attendance_service_expenses.date_date,  Location: “Service Attendance Dates:Expenses:Expenses Date”
      • Field Name: attendance_service_expenses.date_month,  Location: “Service Attendance Dates:Expenses:Expenses Month”
      • Field Name: attendance_service_expenses.date_quarter,  Location: “Service Attendance Dates:Expenses:Expenses Quarter”
      • Field Name: attendance_service_expenses.date_Week,  Location: “Service Attendance Dates:Expenses:Expenses Week”
      • Field Name: attendance_service_expenses.date_Year,  Location: “Service Attendance Dates:Expenses:Expenses Year”
      • Field Name: attendance_service_expenses.id,  Location: “Service Attendance Dates:Expenses:ID”
      • Field Name: attendance_service_expenses.notes,  Location: “Service Attendance Dates:Expenses:Expenses Date:Notes”
      • Field Name: attendance_service_expenses.vendor,  Location: “Service Attendance Dates:Expenses:Vendor”
      • Measure Name: attendance_service_expenses.count,  Location: “Service Attendance Dates:Measures:Expenses:Count”
      • Measure Name: attendance_service_expenses.total_amount,  Location: “Service Attendance Dates:Measures:Expenses:Total Amount”

       

      Required Actions: None

       

      Data Quality Model:

       

      Addressed a bug where the measure counting Reason Receiving Public HIV / AIDS Medical Assistance was labeled incorrectly. 

      • Changed “DQ Client Program Specific:Measures:Reason Not Receiving Public HIV / AIDS Medical Assistance Error Count” -> “DQ Client Program Specific:Measures:Reason Receiving Public HIV / AIDS Medical Assistance Error Count”

       

      Required Actions: Update any processes that use the field “Reason Not Receiving Public HIV / Aids Medical Assistance Error Count”. 

       

      Outreach Model:  

       

      An "Encampment CoC" field was added to the “Encampments” and "Encampment Stays" Views. The CoC is pulled from the Agency CoC field of the Agency that created the encampment. Encampment stays embedded looker users can see are now limited to Encampments created by agencies in the same CoC as the user's agency.

      New Fields: 

      • Field Name: outreach_encampments.coc, Location: “Encampments:CoC”
      • Field Name: encampment_occurrences_details.coc, Location: “Encampment Stays:CoC”

      Required Actions: None