Ticket
| Project | RCM Ultimate |
|---|---|
| Summary | Drivers import issue |
| Sequence | 4279 |
| Classification | Bug |
| Priority | Medium |
| Status | Done |
| Kickoff date | Sep 18, 2026 |
| Maturity date | Sep 18, 2026 |
| Responsible | |
| Version | 2.5.7.2876 |
| Expense | 0 |
| Description | I have encountered an issue with the new RCM version.
When importing a registration file, if I choose to replace drivers with those from the FFVRC database (Yes - All), the import completes successfully with no error message, but no drivers are added to the race. Using the exact same file, if I select No - All instead, the drivers are imported correctly and appear in the race. I have attached the race file (without drivers) and the CSV file for reference. |
Comments
| Timestamp | Who | Comment |
|---|---|---|
| Sep 18, 2026 8:17:36 AM | Felix Romer | I just checked it and found the source of this issue. The participant data import exists actually out of 2 steps:
1.) execute the pilot data import (which is syncing the persons and section assignmentsa) 2.) execute the participant import The problem is now caused in the first step, where the federation data sync is adjusting the birthday of the imported persons in this case. Then the second step has the problem, that he can't find the person anymore with the lookup, as of the changed birthday. Have now solved this issue by adding an out parameter on the function which is executing the first step. This out parameter contains the keys of the synchronized persons, which is then used by the second step. On this way, the current lookup of the person on the second step based on the combination of "firstname, lastname, birthday" is not necessary anymore and the new lookup based on the passed key is returning the right person (and it's even faster). |
Change history
| Timestamp | Who | Modification |
|---|---|---|
| Sep 18, 2026 8:17:24 AM | Ticket created | |
| Sep 18, 2026 8:20:36 AM | Felix Romer | Field: VersionOld value: 2.5.7 New value : 2.5.7.2876 |
| Sep 18, 2026 8:20:40 AM | Felix Romer | Field: StatusOld value: Opened New value : Running |
| Sep 18, 2026 8:42:12 AM | Felix Romer | Field: StatusOld value: Running New value : Done |

Always there for you - support response time of max. 24 hours