Using the Business Object Uploader

When the system detects a business property link type (for example, ParentLink), the system displays the Select Link Column form.

This form displays the following:

• Link Property: Display name of the business property from the business object determined to be a link property.
• Select Property to Search on From business object: Table name linked to this business property. The system retrieves record IDs from this table for insertion into the business object.
• Choose Property: A drop-down list of all fields in the linked business object (all business properties in the linked business object).

Click Select to save the business property. During the upload, the system looks up items in the linked business object based on values in the input file and the selected business property.

The following sections contain mapping information that you must follow to successfully upload incident and employee profile records. See a Sample Mapping File.

• When uploading tasks with a completed status, you must add an input file column mapped to the ActualEffort business property.
• You can add files containing ParentLink relationships. Insert a *ParentLinkRelationship* column in the input file, then add relationship names corresponding to each entry. You must also include a ParentLink column, or these entries will be ignored during the upload.
• When loading employee profiles, make sure to include the employee login and password to facilitate use of the system.

Notes for Incident Record Mapping

When mapping active incidents, add the status, owner team, and owner columns in order.

When uploading logged incidents, you must specify an owner in the spreadsheet, or the upload fails.

The following table contains column heading mappings for incident records:

Column heading	Map to business object
Customer Name	Profile.Link-Link LoginID OR Primary Email
Reported By	AlternateLink-Link.LoginID
Summary	Subject
Description	Symptom
Closed By	Internal Services
Task ID (when adding records with Task information)	AssignmentID

Notes for Employee Profile Mapping

When uploading employee records, create separate objects for managers and employees. Upload manager records first, as the system resolves relationship links to employees.

When loading employee profiles, make sure to include the employee login and password to facilitate use of the system.

The display name used in an uploaded employee record computes the name using the First Name, Middle Name and Last Name field values. Uploading a record with a DisplayName value in the spreadsheet does not produce a value in the system's Display Name field.

The following table contains column heading mappings for employee records

Spreadsheet entry	Map to database entry
Primary Phone	Phone1
Organizational Unit	OrgUnitLink-Link   Move this mapping to the bottom of the spreadsheet.

The system does not support inserting certain information into employee tabs, such as group, computer, journal, and attachments.

Adding Employees with Multiple Roles

Add a Role column to the input file that contains the role display names. If you are updating an existing employee record during the upload, any new roles are added to the roles already assigned to the employee in the employee record.  The system separates roles by commas.

The Role column should be named *Role* (with the asterisks included) and should include the role display name and not the actual role name. For example, include Self Service and not SelfService. All role names should be in the column and separated by commas.

In the application configuration file (called app.config), you can set the AddRoleBehavior parameter to merge or overwrite.

• Merge: Adds new roles from the input file to existing role assignments.
• Overwrite: Deletes existing role assignments and adds roles from the input file.

Add Employees Linked to Multiple Teams

Add a Teams column to the input file that lists the team names (separated by commas) for a particular employee. The team names must match the team entries in the StandardUserTeam table in HEAT.

You can import cost data to the Frs_data_cost_items table and associate it with a specific configuration item. The cost items table column uses ParentLink entries.

• The input file column name can use a name other than ParentLink, but it must be mapped to ParentLink.
• The values in this column must correspond to unique business object field values.

Mapping Input Values to a ParentLink Entry

Shown below is a sample mapping file.

Sample Mapping File

Ensure that the header name in the sample profile file maps to the HEAT property name.