Configuring a Table to Contribute to Odometer History

Summary of the Issue

FleetWave builds each vehicle’s odometer history from readings stored across various tables, such as fuel transactions, job records, or inspection forms. Any table can contribute to odometer history, but it must contain specific columns and be correctly configured in the Table Schema. If odometer readings exist in a table but do not appear in the vehicle’s odometer history or current value, the table has not been properly configured as an odometer source.

Resolution Steps

1. Confirm the required fields exist
   To allow a table to contribute odometer readings, the following fields must exist in the Table Schema Standards:

• Odometer value – numeric field containing the reading (e.g. ODOMETER_FW)

• Odometer date – date field (and optional time field) showing when the reading was recorded (TRANSACTION_DATE_FW, TRANSACTION_TIME_FW)

• Vehicle ID – field linking to the vehicle (VEHICLE_RECORD_NUMBER_FW, VEHICLE_ID_FW, or VEHICLE_ID2_FW)

• Record status – short text field (RECORD_STATUS_FW) used to flag if the reading is valid or invalid

• Error message – text field (ERROR_MESSAGE_FW) used to record any validation errors

If any of these fields are missing, they must be added before the table can be used as an odometer source.

2. Check the fields in the Table Schema Standards tab
   Open the table’s Browse Page.
   Click the three dots in the top-right corner and select Show Details.
   Click Table Schema, then open the Table Schema Standards tab (next to Management).
   Review the field list and confirm the required columns exist with suitable data types:

• Odometer value → Number

• Odometer date → Date (and optional Time)

• Vehicle ID → Text or Number (must match the vehicle key)

• Record status → VARCHAR(2)

• Error message → VARCHAR(100)

3. Add any missing fields
   If any of the above fields are not listed, they can be added through the Redesign Screen.
   For instructions on how to create a field, refer to the Redesign Screen guide:
   Redesign Screen Explained – How to create a field

4. Enable Odometer History Mode
   Open the Management tab of the Table Schema.
   Set Odometer History Mode to Yes.
   Save the schema.

5. Map the odometer fields
   In the same Management tab, confirm the correct field mappings:

• Vehicle ID: field linking to the vehicle record

• Odometer Value: numeric odometer field

• Odometer Date: date (and optionally time) field

• Record Status: RECORD_STATUS_FW

• Error Message: ERROR_MESSAGE_FW

6. Rebuild the odometer history
   After saving the configuration, rebuild the odometer history to include readings from the table.
   This can be done by running the Odometer History Builder event or using the Odometer Correction Tool to rebuild specific vehicles manually.

Additional Notes

• Only records where ARCHIVE_STATUS_FW = 'N' are included in odometer builds.

• If both date and time fields exist, FleetWave automatically merges them into a single timestamp.

• Turning Odometer History Mode off stops future processing but does not remove existing readings.

• FleetWave automatically updates RECORD_STATUS_FW and ERROR_MESSAGE_FW when readings are found to be invalid (for example, a value decreases or jumps excessively).

• Always review and test configuration changes in a non-production environment before applying them live.

• If a table is missing standard odometer fields across multiple environments, contact your FleetWave administrator or system integrator for schema synchronisation.