Release Notes

11/20/2020 - Release Notes

The following changes will be implemented in the data analysis tool.

  • Interaction Date, Client Interaction - A recent bug about the Interaction Date within the interaction period has been fixed
  • County, Agencies - new dimension added
  • State code, Agencies - new dimension added
  • State name, Agencies - new dimension added  
  • End Date, Referrals - Added Week, Month and Year options to the date

Data Analysis Optimization Efforts

As the use of the data analysis tool expands, there have been challenges to the performance of the Looker tool. Basically, we are using it outside of best practices recommended by Looker. The following are some best practices that need to be put into place.

  • Dashboards, limit the number of elements 
    • Dashboards with more than 25 Looks or tiles will drag down the system
      • If you have a dashboard with more than 25 Looks, please consider breaking the dashboard into two or more dashboards
      • Users may be contacted in the future about reducing the number of Looks
  • Scheduled Looks and Dashboards
    • Schedules which reoccur more frequently than once per hour will be bumped to 1 time per hour
  • Auto-Refresh
    • Dashboards or Looks with an "auto-refresh" set below 1 hour will be bumped to 1 hour

New Explore Field Picker

The user interface for choosing fields in data analysis will be getting an upgrade.

The new interface includes the following:

  1. Explore name - Displays the name of the current Explore (Please see Note)
  2. Search bar 
  3. All Fields tab - lists all the dimensions and measures available in the model/explore
  4. In Use tab - lists all the fields currently included in the query
  5. Field-specific information and actions - Displays a field's current and potential functions in an Explore, as well as more details about a field.
  6. Explore summary - Displays the total number of fields in and Explore in the bottom left corner, and the Go to LookML link in the bottom right
    • Go to LookML is only visible to users with development privileges


The Explore name is more of a shortcut name used by Bitfocus developers. Below is a crosswalk between the Explore name and the Model Name.

Explore Name Model Name
Client Model Client Model
Client Coordinated Entry
Imports Data Import Analysis
Base HMIS Performance
Population HMIS Population over Time
Agencies Project Descriptor Model
Reservations By Date Reservations
Clients Services Model

Client Model

  • Referral Connections Enrollment Count  - the drill down has been modified to reflect the correct program name values

Action Needed - Changes to querying Services in the Client Model

The previously announced change has been pulled back pending further review.

Data Quality Model

  • Enrollments CoC Code at Project Start - The client location was showing two times, removed one reference
    • No action needed
  • The following dimensions are now included in the model:
    • acceptable_exit
    • age
    • age_tier
    • any_disability
    • any_income
    • average_cash_income
    • average_income_change
    • average_income_earned
    • disabling_condition
    • disabled
    • entered_stably_housed
    • exit_destination_text
    • exit_type
    • housed_on_exit
    • is_latest_move_in_date
    • prior_duration_text
    • prior_residence_text
    • program_date
    • rhy_school_status
    • screen_type_text
    • total_adults
    • total_cash_income
    • total_children
    • total_income_earned
    • total_unemployment_income
    • total_workers_comp_income

Project Descriptor Model

  • Area Median Income view - A new view has been added which contains all the relevant dimensions and measures that are included in Clarity for the System Variable "Area Median Income"

New Model - Enrollments Progression

The Enrollments Progression model is available for beta testing by standalone data analysis users.

What is it?

The Enrollments Progression model is designed to provide users with a tool to view a client's enrollment path through the user's system. This model takes a specific enrollment (referred to as Primary Enrollment) and examines up to ten Subsequent Enrollments, which are enrollments that have a start date after the exit date of the Primary Enrollment.

Who can access the model?

At this time, access is limited to standalone analysis (Looker) users who have no restrictions on their access to agencies, CoCs, or counties within their instance and who are able to view all sensitive data. This access limitation is due to the design of the model, which aims to give data analysis users a system-wide perspective.

If a user tries to access the model without the proper permissions, they will receive the following error message.

How to access the model?

While this model is in beta testing, this model will not appear in the Explores list within Looker. If you are interested in using the beta version of this model, please contact the Help Desk ( to request access.

For more information about this model, please refer to Enrollments Progression Model.