Skip to main content

Deleting Related Records in FleetWave

Michael Elliott
  • Updated

Summary of the Issue

When deleting records in FleetWave—such as vehicles, assets, or other master records—related records (e.g., allocations, expenses, fuel transactions) are not automatically deleted unless the system is configured to do so. This article explains how to set up FleetWave so that related records are removed at the same time.

Resolution Steps

  1. Understanding Related Record Deletion

    • By default, deleting a record (e.g. a vehicle) will not delete its associated records.

    • To enable this functionality, two configuration areas must be set up:

      • INI Codes

      • Table Schema Dependencies

  2. INI Code Configuration

    • The following INI codes control deletion behavior:

      • BR:NODEL:

        • 0: Fully delete the record.

        • 1: Archive instead of deleting (soft delete).

        • 2: Prevent deletion entirely.

      • BR:CASCADE:

        • Set to 1 to allow deletion of related records based on schema configuration.

  3. Setting Up Table Schema Dependencies

    • To tell FleetWave which related records to delete:

      1. Open the table for the main record type (e.g. VEHICLES_FW).

      2. Click the ⋮ (more options) > Show Details.

      3. Navigate to Table Schema > Management tab.

      4. Add or update the Dependents field.

    • The format should be:

      <RELATION_FIELD>=<RELATED_TABLE_1>,<RELATED_TABLE_2>,<RELATED_TABLE_3>
    • Example:
      VEHICLE_RECORD_NUMBER_FW=JOB_HEADERS_FW,FUEL_ISSUES_FW,ALLOCATIONS_FW,COSTINGS_FW,VEHICLES_ORDERS_FW

    • This tells FleetWave to delete related records in those tables where VEHICLE_RECORD_NUMBER_FW matches.

  4. Archived Records

    • Archived records will also be deleted if they meet the matching field condition.

    • For example, an archived vehicle order will be deleted as long as the VEHICLE_ID_FW matches the deleted vehicle.

     

  5. Customizing Relationships

    • You can adjust dependencies for any table type (not just vehicles), as long as the correct relation field and table names are used.

    • This makes the approach applicable to a wide range of use cases, such as deleting related orders, incidents, or service records.

Additional Notes

  • This setup supports both deletion and archiving operations.

  • Always double-check field names and relationships in your database before applying changes.

  • Deletion may fail silently if the relation field or table name is incorrect or if INI settings are not properly applied.

Related articles