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).
If your users have and ID, this can be used during the import process: Click on Import Data
Choose the Event Type
Once the Event Type is selected, upload the csv file
This is an example of a the csv file which contains an ID for each athlete. Note, no first or last name is included in this file.
To import the data using ID to match users, tick the "Use Uuid to identify athletes" selection.
N.B. If username was included in the spreadsheet you import in, you will be asked if you want to ignore these mapping, click Yes
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)
Once the tick box is ticked, the field containing the ID in the csv needs to be selected.
Once the ID column is selected, the mapping appear
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
The example here shows an example use case where the csv file has the wrong ID listed for an athlete, so during the import process, this data is ignored so that it is not imported for the wrong athlete.
No data will be imported for ID's which have been Ignored
When you are ready to import, click on "Next"
Continue with the import process as per the regular import process
The file will import in as per the standard importing work flows
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.
The data will NOT import if an incorrect Uuid letter case is used
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.
The data is imported for everyone but the user's without a correct ID listed in the csv
IMPORTANT: When doing an import the system will automatically try and use the Name identifier workflow
But, you cannot use this workflow for Uuid imports; This will not work. Only the Uuid tick box work flow is supported.
If the Uuid is selected as an identifier WITHOUT the tick box being selected (as shown here), then the import will not be able to map ID using this workflow and it will fail
0 Comments
Add your comment