Imports
Assemble supports importing users (including custom fields), adding notes or touchpoints, teams, address book entries, tasks and training records from CSV, XLS or XLSX files.
Example files for each import type are available for download below to help with your importing.
When working with exports from other systems there is no need to match the export files to the examples, i.e. field names or order, as the import process allows for field mapping. However the system will use the first row for column headings (to support mapping), so this should be added if it is not included.
To support import planning please download the Excel mapping template. This contains all the available fields and related options for each import type.
Importing data
The process is identical for all imports, but fields and options vary depending on the type of import being run. See below each import type section for more details.
Imports are available from the settings menu under bulk actions. The page will show any running, or previously run imports and you can click on these to view their status/history.
As a file is loaded the system will analyse the file, using the first row as column headers for the mapping process. If you're repeating an import, the system will remember which fields you mapped with which and pre-populate the import tool.
The headers will be listed on the screen with a dropdown beside each for selection of the related Assemble field. Selecting nothing will ignore the field on import.
To avoid creating duplicates, select a field to be the unique identifier. If a field cannot be used as a unique identifier eg postcode, you will not be able to select it. The system will then use the related field to match the existing record for updates (e.g. User ID) or create a new record if none exists. If you don't set a unique identifier, the system will perform a basic check for email address or first name/last name before creating a new user.
The final field on the import allows you to rename the import if you want, to make it easier for you to know what it was when viewing the history. This is just for your own reference.
Once triggered an import runs as a separate process in the background. While you can monitor from the page (which will live update), this is not required, as the system will trigger a notification email once the entire import process has finished.
Progress will be shown on the header, and errors (by default) shown on the detail pane. You can change the view to show All, completed or Not processed rows using the filter button.
On completion, each successfully imported item will show a view link allowing you to check the imported data if desired. Please allow up to 24 hours for the data to be aggregated to the organisation statistics.
Error items can be corrected and re-run on screen, or you can correct the original file and re-import it, in the case of large numbers of issues.
Importing data from XLS or XLSX
Using XLS or XLSX files is best when importing multi-line text in a single field. However, you need to take care using these file types as you can format fields and manipulate cells in various different ways within spreadsheet software such as Excel. Sometimes this can cause unintended formatting of dates which, if you forget to double-check, can lead to the wrong date or other information being imported eg a start date of 5 December rather than the intended 12 May. CSV files are easier for most users to use for most imports (requiring less checking) but when text fields with line breaks are required XLS or XLSX should be used.
For best results, the date format YYYY-MM-DD should be used. They also should be marked as not regional specific within their fields/ cells.
Imports cannot be "undone" easily. Please carefully validate import files before loading large volumes of data. Once you click to import, you cannot cancel it.
Imported users will be checked against the unique ID or the email and first/last name match before a new record is created.
User imports must meet the requirements below to create a user:
- role profile
- team
- manager
- role start date.
* You can add a role end date too but if a role has an end date in the past, users will be made inactive (if no other active role remains). This may take up to 24 hours to show.
Only one role can be imported with a user, for users with multiple roles add these by repeating the import of the user as an update with the additional role. Each additional import will add another role based on the unique ID. It's best to try to use UserID where possible to ensure a match foradditional roles. You can get this by simply looking up the User ID from the header in the user record, or by exporting the imported users to obtain a list for an Excel lookup.
General notes:
- Unique Identifier can only be set to User ID, Email Address or any custom field that has been marked in its setup as 'unique'.
- For both custom fields and training, these must be configured manually in the system prior to the import to be available for mapping.
- You cannot import to custom fields that are the following formats: file, photo, date period.
- When importing to a custom field ensure the importing user has access to write to the field and your imported data matches what you have configured as acceptable values for the custom field.
- You need to have the parent level teams in place first for your team hierarchy so manually adding may be easier if you only have a few teams. Do multiple imports if you have many levels in the team hierarchy.
- When importing training you only import completion date (where relevant), as what training is needed is configured by role, not user. Ensure the training mapped is relevant to the role you are importing.
- When importing diversity data for any field containing the word "other" the other category can also be provided. For example, if for "Nationality" column the value provided is "other", then provide a value for "other nationality" column.
- If you want to include addresses in your teams import, add/import your addresses first and then export your address book to carry out an Excel lookup or similar.
Touchpoints can only be imported to existing volunteers and the volunteer needs to be identified by the UserID. This can be seen on a users record or exports of users from Assemble.
- On user - This is the ID of the user you wish to add the touchpoint on/to
- Author - This is the ID of the user who should be shown as writing the touchpoint, if not specified this will default to the user performing the import.
Notes can only be imported to existing volunteers and the volunteer needs to be identified by the UserID. This can be seen on a users record or exports of users from Assemble.
- On user - This is the ID of the user you wish to add the note on/to
- Author - This is the ID of the user who should be shown as writing the note, if not specified this will default to the user performing the import.
The address book import will default to all users, but can also be imported on a per-user basis where specific addresses are limited in use. To limit to a user you must specify the UserID from Assemble in the import.
The name field specifies what can be searched on, for example 'Your Name HQ'. Latitude and longitude (decimal degrees) can be provided instead of an address to pinpoint a location. If not supplied the address will be used via Google to translate to a location. You should only provide the postcode OR the latitude/longitude. Using both will create an error on the import.
Icons
|
Users |
Building |
Sitemap |
Shopping-bag |
University |
|
Bed |
Cutlery |
Industry |
Map-marker |
Paw |
Imported tasks will only import new tasks to Assemble and cannot be used to update existing ones. If the same details as an existing task are entered, the task will simply be duplicated.
Task imports must meet the requirements below to create a new task:
- Either Due date (by) or Due date (on).
- A task title.
- The Assemble ID of the user who will be the owner of the task must be entered into 'Owner ID'.
- An activity category ID.
- Priority exactly matching one of the following:'low', 'normal', 'high', 'urgent'.
General notes:
- Ensure that you only provide IDs for resources in your current organisation. Also, ensure all IDs including Geolocation ID are configured in Assemble before importing.
- If importing Team IDs and Role IDs, we recommend XLS or XLSX files to be used. CSV files should still work, however, you can now import using the equivalent Excel sheet. This means text fields with line breaks are now also supported.
- If a postcode is provided without geo location id, the address will be parsed from the postcode.
Training records can only be imported to existing volunteers using existing training modules. The volunteer needs to be identified by the UserID created by Assemble. This can be seen on a users record or exports of users from Assemble. The training module should be identified by the Training ID created by Assemble. This can be seen by superusers in the training settings. We strongly recommend that the Training ID is used, however, you are able to use the Training name if it's unique.
General notes:
- Users, training modules and custom fields (if used) must be configured in the system prior to the import to be available for mapping. This includes the training modules being applied to the user's role in the compliance section of the role profile.
- The unique identifier should be set to User ID, email address or any Custom field ID and Training ID or Training name should also be unique.
- The completion date is required.
- When importing to a custom field ensure the importing user has access to write to the field and your imported data matches what you have configured as acceptable values for the custom field.
Equality, diversity and inclusion (EDI) data is part of the ‘users’ import process and can be imported with the creation of new users or to update existing users.
General notes:
- When importing EDI data each field must exactly match a given variable within Assemble. You can find these variables in the ‘Assemble Import Mapping Template’ above within the ‘Reference’ tab.
- If importing EDI data for existing users, we recommend using the Assemble ID as the unique identifier.
- When importing EDI data for any field containing the word "other" the other category can also be provided. For example, if for "Nationality" column the value provided is "other", then provide a value for "other nationality" column.
- Once imported, following GDPR guidelines, you will not be able to directly see this data per individual, however, it will update and be represented within the analytic reports.