Event and Profile Data can be imported in using a ID field to do the user mapping
When importing in Event Data or Profile Data, you currently need to map across the athletes' names on the spreadsheet being imported, to the athletes' names listed in the system. Now you can map athlete's using the ID field (which is set up on the athlete's account).
The workflows below show importing for Event Forms, but the Profile Form Imports work using the same structure.
Depending on how your organisation is structure, you may use an ID field to identify each user.
Depending on the structure of your organisation, you may use an ID field to identify each user, this can either be a field which is configurable (Organisational ID), non-configurable (Smartabase ID which is automatically assigned), or some organisation may not have this field enabled at all (No ID).
Once the Event Type is selected, upload the csv file
To import the data using ID to match users, tick the "Use Uuid to identify athletes" selection.
An Identifier field selector appears. Select the Column which contains the athletes' ID (e.g. the name of the ID field in the csv file)
The ID from the imported file will be displayed and the Athlete ID (Organisational or Smartabase ID) and the athlete with that ID will appear in the Athlete Uuid and Athlete Details Columns
If there is no corresponding ID to the ID on the import file, the details will display "No user found".
If "No user found" is displayed it will be because of one of three reasons:
1. The ID is incorrect on the csv file (as shown in the first line, the Uuid of 19762 exists, but excel formatted the ID with a decimal place, and an ID of 19762.0 does not exist)
2. The athlete is not included in the group that you are trying to import in the data for
3. No athletes are on the system with that ID.
If any of the ID mappings are incorrect, you can also select to Ignore the import for a specific ID
Continue with the import process as per the regular import process
The system will confirm whether the data was imported in correctly
Once imported, the data will be available to view in the reports page, athlete history, etc.
IMPORTANT: Uuids are case sensitive. If a user is in a csv spreadsheet with an upper case T, but they have a lower case t in their Uuid on their account, the import will FAIL for this athlete.
N.B. If a Uuid is NOT entered for each athlete on the csv spreadsheet, then the data will not be able to be imported for the athletes. The example here shows how the import will FAIL for two users without it!
The example in the image here shows that two athletes do not have a Uuid added for them in the csv file. A user is going to try and import in this data using the Uuid import process.