What are detail tables?
Detail tables extend certain object types with specialized data fields that are necessary for the technical management of these objects. When you assign a detail table to an object type, additional fields and functions become automatically available for that object type.
The system automatically establishes the connection between an object and its detail table. Changes to the base data (code, barcode, description, room) are synchronized bidirectionally.
Important: Not all object types require a detail table. This feature is only useful for object types that require specific information beyond the standard object fields.
Available Detail Tables
Currently, two detail tables are available in the system:
Doors
For object types that represent doors. This detail table is primarily used in lock management.
Use Case:
Lock management uses the door detail table to assign lock cylinders and keys to specific doors. The unique door number allows lock plans to be created and managed. If changes are made to the location (room), the assignment is automatically updated.
Synchronized fields:
Object: Code ↔︎ Door: Code
Object: Barcode ↔︎ Door: Barcode
Object: Name ↔︎ Door: Name
Object: Room ↔︎ Door: Room
Object: ID ↔︎ Door: Door number
Vehicles
For object types that represent vehicles. This detail table is used in fleet management.
Use Case:
Fleet management uses this detail table for professional management of the vehicle fleet. You can track general inspections, tire changes, and contract expiration dates. Pool vehicles can be assigned to employees. Integration with cost center management enables accurate cost allocation.
Synchronized fields:
Object: Code ↔︎ Vehicle: Code
Object: Description ↔︎ Vehicle: Vehicle Note
Technical Functionality
Automatic synchronization
When you create or edit an object whose object type is linked to a detail table, the following happens automatically:
When creating an object: The system automatically creates a corresponding record in the detail table and transfers the basic data (code, barcode, description, room).
When changing an object: Changes to the synchronized fields are automatically transferred to the detail table.
When deleting an object: The corresponding data record in the detail table is also deleted.
This synchronization is bidirectional via database triggers and ensures that the data always remains consistent.
Configure mapping
The mapping between object type and detail table is configured in Object Type Management:
Navigation: Control Panel → Objects/Assets → Object Types → [Edit Object Type]
In the edit form, you will find a [Detail Table] field where you can select the desired detail table. The following options are available: - None (default for most object types) - Doors - Vehicles
Note: This mapping should only be performed by administrators with the appropriate expertise. Changing the detail table mapping after the fact may result in data loss.
📄 Objekttypen und Matchcodes anlegen IC12529
When should you use detail tables?
Detail tables are useful when:
The object type requires subject-specific data fields that are not relevant to other object types
The objects are used in specialized modules (e.g., lock management, fleet management)
Separate management and evaluation of this object group is required
Additional master data (e.g., vehicle types, status) must be maintained for this object group
Examples:
Doors: If you operate a professional lock management system and want to manage lock cylinders, keys, and locking plans.
Vehicles: If you operate a fleet management system and want to centrally manage vehicle inspection appointments, fuel cards, tire changes, and vehicle contracts.
For object types without these specific requirements (e.g., furniture, office equipment, tools), the standard object fields are perfectly sufficient.
Technical Background Information
The detail tables are linked to the object table via an internal reference. Data synchronization occurs automatically via database triggers and stored procedures. This ensures that changes to an object are immediately reflected in the corresponding detail table and vice versa.
The mapping between object type and detail table is stored in the system configuration and can only be changed by administrators.