Holman
DLH.io documentation for Holman
Holman provides fleet management, leasing and maintenance services. This connector replicates your Holman fleet data, including vehicles, accident claims, contacts, safety drivers, fuel transactions, maintenance purchase orders, odometer readings and invoices, so fleet and finance teams can analyze cost and utilization in your warehouse.
Setup Instructions
Follow the setup steps guide for configuring your Holman connection to enable data to flow into your destination via DLH.
Supported Features
Here are key features supported for this connector.
| Sync Feature | Supported | Details |
|---|---|---|
| Custom Data and Development | ✓ | Ability to enhance connector upon request |
| Historical Re-Load/Load | ✓ | |
| Incremental/Delta Load | ✓ | Vehicles, contacts, claims, fuel, maintenance and odometer read as changes since the previous run |
| Column Selection | ✓ | |
| Column Hashing | ✓ | |
| Re-Sync Table/Entity | ✓ | Select at the table level to reload data history (on next Sync Bridge run) |
| Custom Queries | Utilizing SQL Data Query Connector | |
| Custom Data | ||
| Captures Deleted Rows | Deletes in Holman are picked up only by a historical re-sync | |
| API Sync Bridge Initiation | ✓ | |
| Priority Scheduling | ✓ | |
| Private VPC/Link | ☂ | |
| DLH Data Model Available | - |
If you have any questions about these supported features please reach out to our Customer Support team.
Details on Sync Processing
Vehicles, contacts, accident claims, fuel, maintenance and odometer records are read as changes since the previous run, with a one hour overlap. Safety drivers and invoices are read in full on every run. The documents, chassis and upfit components of a vehicle are read for the vehicles that changed since the previous run, so a change made only to a component is picked up by a historical re-sync. Anything deleted in Holman is also picked up by a historical re-sync. Holman allows 300 requests a minute for your whole company, shared with your other integrations, and the first synchronization of a large fleet can take a while. Holman enables each endpoint on request: a table whose endpoint is not enabled for your credentials is skipped with a warning, and loads once Holman enables it and you run a historical re-sync. Each connection targets one environment (Production or Staging) and uses the lessee codes you add on the Configurations tab. The connection is read only.
Be sure to also check the change log and notes page from time to time for any changes.
Issue Handling
If any issues occur with the connection simply return to the sources page in DLH.io, edit the source details and click the Save & Test button to confirm connectivity. If any issues persist please contact our support team via the DLH.io Support Portal.
Replicated Entities
The following 13 entities are replicated by default to your Target Connection. These are the table names you will see in your Target Connection. If you believe any entities/tables are missing please open a ticket with Customer Support:
VEHICLEACCIDENT_CLAIMCONTACTSAFETY_DRIVERFUEL_TRANSACTION_USFUEL_TRANSACTION_CAMAINTENANCE_PURCHASE_ORDERODOMETERINVOICE_MISCINVOICE_NEOVEHICLE_DOCUMENTCHASSISUPFIT
Schema Details (ER Diagram)
This entity relationship diagram (ERD) provides you with information about what entities/tables DLH provides for you out-of-the-box and how they are related to one another.