Field Mapping

Here is a spreadsheet that you can use for mapping fields from your source system into Interact if you are using UMI (i.e. General Profile Source) to import the data.

Field Label Field Name Required Description Possible Values
Sync Setting - Domain domain Yes Name of Sync in Manage Profile Sources  
Sync Setting - ID ldapid Yes ID of Sync in Manage Profile Sources  
Sync Setting - Companies syncCompanies Yes indicates if Company values should be taken from file data true, false
Sync Setting - Locations syncLocations Yes indicates if Location values should be taken from file data  
Sync Setting - Departments syncDepartments Yes indicates if Department values should be taken from file data  
Sync Setting - Managers syncManagers Yes indicates if Manager values should be taken from file data  
Sync Setting - Disabled Users actionDisabledUsers Yes action taken for disabled User accounts d' (disable only), 'a' (archive), 'x' (do nothing)
Sync Setting - Missing Users actionMissingDeletedUsers Yes action taken for missing User accounts d' (disable only), 'a' (archive), 'x' (do nothing)
Sync Setting - Authentication Type loginType Yes preferred login method.  Setting at global level for file feed 0 (Interact User), 1 (Windows User), 2 (SAML)
Sync Setting - Default Culture defaultCulture Yes Culture default… can be overwritten by culture field in user record integer referencing an Id in the Interact CULTURE table - culture to apply to new Users
Sync Setting - Default Company defaultCompany No integer referencing an Id in the Interact ORGANISATION table - default Company to apply  
Sync Setting - Default Department defaultDepartment No integer referencing an Id in the Interact ORGANISATION table - default Department to apply  
Sync Setting - Default Location defaultLocation No integer referencing an Id in the Interact ORGANISATION table - default Location to apply  
Sync Setting - Password Type newUserPasswordBehaviour Yes string describing the approach to the password in a new profile strict' takes the supplied password and applies strength checks as the PERSON row is saved
'random' generates a random password
'blank' saves a blank password - this is the default option if the element is not supplied
Unique ID field uid Yes When importing a user into Interact, the Processor will attempt to find an existing user based on four pieces of data - this is the first lookup value - UID  
DN dn No When importing a user into Interact, the Processor will attempt to find an existing user based on four pieces of data - this is the first lookup value - DN  
User Name userName Yes When importing a user into Interact, the Processor will attempt to find an existing user based on four pieces of data - this is the first lookup value - Username  
Email Address email No When importing a user into Interact, the Processor will attempt to find an existing user based on four pieces of data - this is the first lookup value - Email  
Active statusEnabled Yes Determines if user is Active or not true, false
Password password No    
Surname surname Yes Last Name  
First Name firstname Yes    
Profile Type N/A No Defaults to Intranet User  
Forced Password Reset N/A No Flag to toggle the user to change their password - for users that use a password to login.  
Title title No The title eg. Mr, Mrs, Miss etc.  
Initials initials No The user's initials - eg. SD, DMW, TW etc.  
Pronouns N/A No user's preferred pronoun which will be displayed on their profile  
Date of Birth dateofbirth No The User's date of birth is in this format: eg. 1990-01-23  
Timezone timezone No Timezone for user https://developer.interactsoftware.com/docs/valid-timezone-entries
Expertise N/A No Supported in separate feed https://developer.interactsoftware.com/docs/expertise-and-interests
Interests N/A No Supported in separate feed https://developer.interactsoftware.com/docs/expertise-and-interests
Picture N/A No Supported in separate feed https://developer.interactsoftware.com/docs/profile-pictures
Alternate Email Address N/A No    
Address address No Address in combined format (i.e. street address, city, state, zip)  
Home Phone Number N/A No  
Work Phone Number phone No  
Mobile Phone Number mobile No  
Facsimile fax No    
Extension extension No    
Manager - UID manager uid No First lookup value for manager  
Manager - DN manager dn No Second lookup value for manager  
Manager - username manager username No third lookup value for manager  
Manager - email manager email No Fourth lookup value for manager  
Job Start Date urn:ietf:params:scim:schemas:extension:interactsoftware:2.0:User:jobStartDate No The User's job start date is in this format: 2021-01-23  
Job End Date urn:ietf:params:scim:schemas:extension:interactsoftware:2.0:User:jobEndDate No The User's job end date is in this format: 2021-01-23  
Job Title title No    
Bio bio No Field is available in UMI but will not import (known defect)  
Primary Department organisation type="department" primary="true" Yes Primary Department / Division  
Additional Departments organisation type="department" primary="false" No    
Primary Location organisation type="location" primary="true" Yes Primary Location / City / Office   
Additional Locations organisation type="location" primary="false" No    
Primary Company organisation type="company" primary="true" Yes Primary Organisation / Company   
Additional Companies organisation type="company" primary="false" No    
Facebook N/A No Facebook ID for the user's profile. Please do not include the prefix https://www.facebook.com/  
LinkedIn N/A No LinkedIn ID for the user's profile. Please do not include the prefix https://www.linkedin.com/in/  
Twitter N/A No Twitter Tag for the user's profile. Please do not include the prefix https://www.twitter.com/ 0
Instagram N/A No Instagram Tag for the user's profile. Please do not include the prefix https://www.instagram.com/  
Skype N/A No Instant messaging address  
Chat N/A No Instant messaging address  
Additional Fields <additionalfields> section.  Format example <field name="first_aider">  No Do not use special characters (except space) when creating additional fields.  Once field is created, the field name will be lowercased and any spaces will be replaced with _.  Eg: "Employee ID" becomes "employee_id" Additional field date type formatted as: 0|mm/dd/yyyy||||||||.
Additional field boolean type formatted as true or false.
Additional field string type passed as a string.
Theme N/A No    
Home Page N/A No    
Activate an Onboarding homepage for this User N/A No    
Preferred Language language No User's preferred written or spoken language 0 for English UK and 1 for English US
Culture culture No Indicates the User's default location for purposes of localizing items such as currency, date time format, or numerical representations 1 for English UK and 2 for English US
Person ID N/A No Numerical system field generated by Interact.  Value seen in URL as id=<value>  
Groups group object Yes At least one group is required for each user