Supplier Users may be bulk imported into the BuyerQuest system. This topic details the import file structure and process relevant to importing Supplier Users.
Overview
The Supplier User Import capability allows for many supplier users to be quickly and easily created in the BuyerQuest system.
Supplier User records may be imported automatically, using the on-demand Master Data Import function, or may be imported from the Admin Control Panel.
The fields described in this topic apply to both import methods.
Supplier Users - Automatic Import
Buying organizations may request implementation assistance to enable them to initiate automatic, on-demand Master Data imports from staging folders specifically set up for this purpose.
When the required folders have been set up, a Master Data Import is triggered when a csv file is dropped into the file system.
The required file path must be in the following form, where information specific to the buying organization, import entity type, mode, and filename are provided (as shown within <>):
<Client Organization>/MasterData/AutomatedImport/<entity_type>/<mode>
<filename.csv>
Requirements for an Automatic Supplier Users Import
The requirements for an automatic Supplier Users Import are as follows:
- Valid entity type is user_supplier.
- Accepted mode is delta.
- File type must be csv.
- Fields in the file must conform with the requirements set out in the section Supplier Users Import Fields
Supplier Users Automatic Import Sample Path
Example: Organization Company A may initiate a delta Supplier Users import by dropping the following file into the file system that has been set up through BuyerQuest implementation:
Company A/MasterData/AutomatedImport/user_supplier/delta/April2021.csv
Import Supplier Users from the Admin Control Panel
The ability to import Supplier Users is managed in the Admin Control Panel at DATA LOADS > Manage File-Based Integrations > Import.
Supplier Users Import Templates
SupplierUserImportRequiredFields8.0.csv SupplierUserImportRequiredAndOptional8.0.csv
Supplier Users Import Fields
| Field Name | Description | Type | Required | Example |
| last_name | Last name of the user | Text | Yes | Smith |
| first_name | First name of the user | Text | Yes | John |
|
email OR login_id |
File can contain a column name of either 'email' OR 'login_id' - they are the exact same columns and will work in the exact same way. This is for backwards compatibility, the preferred column name is 'login_id'. |
Text |
Yes |
"User1" or "sample@buyerquest.com" |
|
supplier_id |
Supplier ID/Global Supplier ID |
Text |
Yes |
23678 |
|
external_id |
External ID associated to the Supplier User |
Text |
No |
john.smith_28 |
|
is_activated |
Status of the user: 1 = Active 0 = Inactive |
Boolean |
No |
1 |
|
contact_email |
Contact Email for user |
Text |
No |
|
|
content_group |
Content group associated to user (if not set, will default to Content Group set under User Management |
Text |
No |
General |
|
user_permission |
User permission associated to user. |
Text |
No |
Supplier |
|
preferred_language |
Preferred language for user |
Text |
No |
fr_FR |
|
preferred_currency |
Preferred default currency for user (Identified in CSV by a standard 3 character currency code). e.g. USD, AUD, CAD, EUR etc. |
text |
No |
USD |
|
telephone |
telephone number for the user |
string |
No |
888-478-1678 |
Notes
- All fields after supplier_id are treated as defining which system is the System of Record for that information. If the column is listed in the CSV file, then the System of Record is NOT BuyerQuest. This means all information related to this column is over-written by what is in the file. If the column is not present in the CSV file, then the System of Record should be considered to be BuyerQuest, meaning that the information should not be over-written by the import.
- The system will default the external_id to a combination of email and supplier_id.
- If is_activated is not set - system will default the user to 1 (Active).
- If no contact_email is specified for a supplier user, the system will default to the required email or login_id; if the login_id value is not a valid email format the row is skipped with a warning.
- If content_group is not set - system will default the user to the Content Group specified in the Admin Control Panel at:
Menu > System Administration > Settings and Configurations > Manage System Configurations > Master Data Management > User Management > Supplier User Default Settings
If no default content_group is specified in the Supplier User Default, settings, the importer will report a warning that the content group is invalid and skip the row. - If no default user_permission is set for a User, the system will default to the User Permission specified in the Admin Control Panel at:
Menu > System Administration > Settings and Configurations > Manage System Configurations > Master Data Management > User Management > Supplier User Default Settings - If no default preferred_language is identified for a Supplier User, the system will default it to the Site Default Language.
- If no preferred_currency is set for the Supplier User, the system will default it to the Site Default Currency.
Auto-generated Values Based on the Supplier User Import Type
The following information is defaulted for new supplier users:
- User Type = Supplier
- Associate to Website = Main Website
- Allow Access To = 0 Customer site only
- auto_generated_password = 1 (Password should be auto-generated for the Supplier User. The Supplier User will have the ability to update the password when logging in the first time)
- change_passwd_on_login = 1
Primary Key Algorithm
This algorithm determines whether a Supplier User should be updated or if a new Supplier User record is created.
- First check if External ID already exists and email matches, if so, then update any other information for that User.
- If External ID exists but email does not match, then check 'Email':
If Email does not exist already in system, then update Email and any other information for that User.
If Email does exist in the system, then produce the Warning: "External ID and Email already exist for different Users." - If External ID does not exist, check 'Email':
If Email does not exist, then create User and update any other information for that User.
If there is a User with that email, update the External ID and then update any other User information for that User.
Comments
0 comments
Article is closed for comments.