The Halo connected fields feature lets you map individual asset layout fields in Hudu directly to data points in HaloPSA. When a field is connected, Hudu automatically populates it with the corresponding Halo custom field value during each sync — keeping your documentation accurate without manual updates. This article covers how to configure field connections, what field types are supported, and how connected fields behave on assets.
Visit Connected Fields for additional information on connected fields in Hudu.
Visit Setting Up the Halo Integration for additional information on configuring and enabling the Halo integration in Hudu.
Visit Asset Layouts for additional information on creating and managing asset layouts.
Guides
How to connect a Hudu field to a Halo data point
Field connections are configured at the asset layout level in Hudu's admin settings. Each field in a layout can be mapped to a single Halo data point, and the connection applies to all assets using that layout.
Only asset layouts that are set as a default layout for a Halo object type (such as Halo Devices or Halo Contacts) will show Halo as a source option. If you do not see Halo in the source dropdown, confirm the layout is mapped as the default for the relevant Halo type.
- In Hudu, navigate to Admin > Asset Layouts.
- Open the asset layout you want to configure.
- Click Edit on an existing field, or add a new field.
- In the field editor, locate the Source dropdown.
- Select Halo as the source.
- A second dropdown will appear — select the Halo data point you want to connect to this field.
- Save the field and publish the layout.
If a Halo data point you expect to see is not listed, try refreshing the Halo integration. Select the quick refresh option from the integration dropdown in the top navigation bar, then return to the field editor.
How to identify connected fields on an asset layout
Once a field is connected to a Halo data point, it is marked in the asset layout admin view with a plug icon. Hovering over the icon shows a tooltip identifying the connected source.
How connected fields appear on assets
When viewing or editing an asset that has one or more connected fields, Hudu surfaces this clearly:
- Asset view: A banner is displayed indicating that one or more fields are populated from a connected source.
- Asset edit view: Connected fields are marked with an info badge to indicate they are managed by the integration.
Tools
Halo can only be selected as a source for the following field types:
- Text
- Rich text
- Copyable text
Other field types (such as checkboxes, dropdowns, or date fields) will not show Halo as a source option in the field editor.
The Halo data points available as sources depend on the object type the asset layout is mapped to. Supported categories include:
- Default device fields — standard fields available for Halo device records (e.g., serial number, model)
- Default contact fields — standard fields for Halo contact records (e.g., contact_phone)
- Default site fields — standard fields for Halo site records
-
Custom asset fields — Halo custom fields added to assets; appear as
asset_field_{field_name} -
Custom site fields — Halo custom fields added to sites; appear as
site_field_{field_name} -
Custom fields (assets, sites, users) — additional Halo custom fields; appear as
{type}_custom_field_{field_name}
Custom fields added to Halo after the last sync will not appear until Hudu syncs with Halo again. Use the quick refresh option in the top navigation to pull in the latest Halo field definitions without waiting for the next scheduled sync.
If your Hudu instance has both Halo and Radar configured, and both are mapped to the same asset layout, both integration sources will appear in the field source dropdown. Only one source can be active per field — selecting one will disable the other.
Additional abilities
Changes to connected field values — whether made manually or populated by a sync — are tracked in Hudu's activity logs and version history. This provides a full audit trail of when values changed and what the previous value was.
When new custom fields are added to Halo, they will not appear as source options in Hudu until a sync has occurred. There are two ways to pull in updated field definitions:
- Quick refresh — Select the Halo integration from the quick refresh dropdown in the top navigation. This refreshes field definitions without running a full sync.
- Pause and restart sync — Navigate to the Halo integration settings, pause the sync, then start it again. This also updates available field definitions.
FAQ
There are a few possible reasons:
- The Halo integration has not been configured or enabled in Hudu.
- The asset layout is not set as the default layout for a Halo object type. Only default Halo layouts show Halo as a source option.
- The field type is not supported. Only text, rich text, and copyable text fields can be connected to Halo.
Custom fields added to Halo after the most recent sync will not appear in Hudu until the integration syncs again. Use the quick refresh option from the integration dropdown in the top navigation to pull in the latest field definitions, then check the source dropdown again.
Yes — connected fields can be edited manually on an asset. The change will be saved and logged in activity logs and version history. However, the value will be overwritten with the data from Halo on the next sync.
No — the field will remain connected. After the next sync (or a quick refresh), the field name shown in the Hudu source dropdown will update to reflect the new name from Halo.
If the Halo integration is removed or disabled, connected fields will no longer receive updates from Halo. The last synced values will remain in place on existing assets, but the source connection will no longer be active. Please reach out to Hudu Support if you have questions about this.
Troubleshooting
If connected fields are not updating as expected, check the following:
- Confirm the Halo integration is active and syncing. Navigate to the integration settings to verify the sync status.
- Confirm the field in the asset layout is still mapped to the correct Halo data point.
- If a custom field was recently added or renamed in Halo, run a quick refresh or pause and restart the sync to update field definitions in Hudu.
If the issue persists, contact Hudu Support with the asset layout name and the field in question.
If a connected field value is blank after a sync, it is likely that the corresponding field is not populated on the Halo record, or the field is not in use on the Halo asset. Halo data points only appear as options in Hudu if they are actively used on Halo assets — unused fields will not carry data over during the sync.