1. Fields

1. Fields

Huume field definitions

The Huume Field Definitions spreadsheet defines all the standard fields that appear on each of the forms. We recommend updating this spreadsheet to capture all of the new fields that you wish to add to the system. It is easier capture this information in this format initially to make sure you are adding things in the right place in the system.
Once you have added your own custom questions we will then review the spreadsheet with you and provide feedback/suggestions where relevant.
We would suggest completing the forms in the following order:
  1. Person - Admin
  2. Housing Register - Admin
  3. Person - My profile
  4. Person - My family
  5. Housing Register - Portal
  6. Homeless - Admin
  7. Homeless - Portal
Important things to consider when completing the spreadsheet:
  1. If you do not want to use a standard field set it to show as strikethrough instead of deleting it
  2. Highlight any new fields you add so they are easy to identify
  3. Use a consistent approach with your field names
  4. Think about the field type carefully to match the data you want to store in it
  5. If a field is added to the Portal version of a form you must add it to Admin version of the form as well

People sub-forms

Information from People records can be embedded within the following forms, using people sub forms:
  1. Housing Register - both Admin and Portal versions
  2. Homeless - both Admin and Portal versions
  3. Health assessment - Admin version
Typical information that is captured through the use of people sub forms is medical, employment, convictions, education, etc. Any information where it needs to be captured per person is best suited to be entered and displayed in a people sub form.
Alert
Any information you want to display/capture in a people sub-form must also appear on the Person Admin form

Data migration

If you are undertaking a data migration exercise then you will need to create the fields to match your existing data. Each field will need to match the format that it is currently in and lookups will need to contain the same values.
New questions that you don't currently ask can be created but they will not be populated as part of the data migration.

Adding fields

Only start creating fields in the system once you are happy that they are being created in the correct locations.
Fields can either be added through the Fields list or directly to a form through the Form editor.
Important things to remember when adding fields:
  1. Check the spelling of the fieldname is correct - it cannot be changed once created
  2. Check the field type is correct - it cannot be changed  once created
  3. When creating a single/multi select field check if you need a new lookup or link it to an existing lookup. Once a lookup is selected it cannot be changed in the future

    • Related Articles

    • 8. Fields

      The Fields list displays all fields that have been added to the system through the administration screens. When a field is edited the details of the field are displayed. Item Details Field name The short unique name of the field used in lists and ...

    • Appendix I - Special/calculated fields

      A number of special/calculated fields exist in the system that are not used in the Form Editor but can be added as columns to lists. These fields are designed to provide specific information and vary depending on the table they are connected to. ...

    • Why don't fields appear in the Filter Builder?

      Only those fields that are displayed as columns in the List appear in the Filter Builder. If you wish to use a field in the Filter Builder but not display it, then it can be marked as Invisible.

    • How do you sort on multiple fields in a list?

      Clicking on the column header will sort a list ascending or descending on that specific field. If you wish to add a secondary sort on another field hold the Shift key while clicking on the column header of the second field. Alternatively right click ...

    • Release v1.17.3 30/04/2021

      Fixes Back office Form Editor Fixed an issue where Min/Max values for number, decimal and money fields were not being correctly saved in the Form Editor.