travelidmapping Table (43)
Some tooltip text!
• 2 minutes to read
• 2 minutes to read
Mapping of primary keys between Travel databases and the mother database All travel database transactions get a high id to be able to see that this entry came from a database outside the central database. When update files are read into the central database, they get a normal low id. This table remembers the high travel id to map it to the low central id as long as this travel user is travelling.
Fields
| Name | Description | Type | Null |
|---|---|---|---|
| travelidmapping_id | Primary key | PK | |
| associate_id | Associate id (traveller) | FK associate | |
| table_number | Database table number | TableNumber | |
| local_id | ID on traveller | Id | |
| parent_id | ID on parent database | Id | |
| counter | How many consecutive ID's | UInt | ● |
| cdbName | Conceptual database name if != standard database | String(29) | ● |
| registered | Registered when | UtcDateTime | |
| registered_associate_id | Registered by whom | FK associate | |
| updated | Last updated when | UtcDateTime | |
| updated_associate_id | Last updated by whom | FK associate | |
| updatedCount | Number of updates made to this record | UShort |
Indexes
| Fields | Types | Description |
|---|---|---|
| travelidmapping_id | PK | Clustered, Unique |
| local_id | Id | Index |
| associate_id, table_number, parent_id | FK, TableNumber, Id | Index |
Relationships
| Table | Description |
|---|---|
| associate | Employees, resources and other users - except for External persons |
Replication Flags
- None
Security Flags
- No access control via user's Role.