Staffing EDIT Template

The fields described in this reference information must appear in an upload file in the order listed here. The header value also must match the field names in this reference information. If not, you receive an error.

You can download this template by clicking here.


Field	Format	Required?	Description/Notes
Worker GUID	Alphanumeric	No (Conditional. You must enter a value in at least one of the primary key fields.)	This field is a primary key. Enter the value if the worker has a client-assigned worker identifier. If not, leave this field blank. Note: If multiple worker records exist with the same GUID, you receive an error. You must log into the application and change the worker GUID (Worker > Account Information > GUID).
WAND Worker ID	Alphanumeric	No (Conditional. You must enter a value in at least one of the primary key fields.)	If the worker identifier exists in the application, enter the value in this field. This field is a primary key.
Engagement ID	Number	No (Conditional. You must enter a value in at least one of the primary key fields.)	If this field is populated, the engagement identifier is used as the primary key. This ensures that workers with multiple engagements in the system are updated.
Worker First Name	Alphanumeric	No	Enter the worker's first name.
Worker Last Name	Alphanumeric	No	Enter the worker's last name.
Legal First Name	Alphanumeric	No	Enter the worker's legal first name.
Legal Last Name	Alphanumeric	No	Enter the worker's legal last name.
Phone Number	Number	No	Enter the worker's telephone number.
Worker Email Address	Alphanumeric	No	Enter the worker's email address. This value is used to email the worker from the application. The address also defaults to their username for login if you do not enter a value in the Worker GUID and WAND Worker ID fields. This field: Cannot contain spaces Must end with a dot extension, for example, '.com' name and domain must be separated by an '@'
Start Date	MM/DD/YYYY	No	Enter the date that the engagement begins.
Estimated End Date	MM/DD/YYYY	No	Enter the estimated end date for the engagement.
Manager GUID	Alphanumeric	No	Enter the manager identifier. This associates a client manager with the engagement.
Department Number	Number	No	Enter the department number to associate with the engagement. Note: If the client organization/OpUnit is configured to not allow client managers to create departments (Configuration > <op_unit> > Settings > Configuration > Manager tab > Allow Managers to add departments to their accounts during request creation), then the department number must exist in the client manager's Associated Department list.
Parent Department Code	Number	No	If the client organization has identical department identifiers across different department hierarchies, enter the parent department identifier (from the department hierarchy). Note: If you have identical department identifiers, and do not enter a parent department identifier, you receive an error.
Building Code	Alphanumeric	No	Enter the building code tied to the location for the engagement.
Worker Offsite Country	Alphanumeric	No	If the work is completed offsite, enter the offsite country.
Worker Offsite City	Alphanumeric	No	If the work is completed offsite, enter the offsite city.
Worker Offsite State	Alphanumeric	No	If a value is entered, then the Work Completed Offsite option on the engagement is selected. The value populates the State field.
Worker Offsite Address	Alphanumeric	No	If a value is entered, then the Work Completed Offsite option on the engagement is selected. The value populates the Street Address field.
Worker Offsite Postal code	Alphanumeric	No	If a value is entered, then the Work Completed Offsite option on the engagement is selected. The value populates the Postal Code field.
Job Category	Alphanumeric	Yes (conditional) If a value is added in the Job Code column for this engagement, then you must include a corresponding value for Job Category.	If populated, this value must be a configured job category for the organization/operational unit.
Job Code	Alphanumeric	Yes (conditional) If a value is added in the Job Category column for this engagement, then you must include a corresponding value for Job Code.	If populated, this value must be a configured job code for the job category in the organization/operational unit.
Job Title	Alphanumeric	No	Enter the job title for the engagement.
Hours per week	Number	No	Enter the number of hours per week for the engagement. If you do not enter a value, the number is set to '40' by default.
Hours per day	Number	No	Enter the number of hours per day for the engagement. If you do not enter a value, the number is set to '8' by default.
Days per week	Number	No	Enter the number of days per week for the engagement. If you do not enter a value, the number is set to '5' by default.
Currency	Alphanumeric	No	Enter the currency for the engagement. This value overrides the value selected in the Currency drop down on the process configuration page. For more information about this field, see Use Bulk Upload.
Pay Rate	Number	No	Enter the pay rate for the engagement. Note: Editing this field using the Bulk Upload process recalculates the engagement financials.
Bill Rate	Number	No	Enter the bill rate for the engagement. Note: Editing this field using the Bulk Upload process automatically recalculates the financials on the engagement. For multi rate engagements, this value must correspond to the value in the Rate Type field. If this field is blank, then the value defaults to the regular bill rate value.
Rate Application	Alphanumeric	No	Enter the rate application for the engagement. If entered, this value overrides the value selected in the Rate Application field. For more information about this field, see Use Bulk Upload.
TEI	Alphanumeric	No	Enter the timecard type for the worker.
Invoice Option	Alphanumeric	No	Enter the invoice option for the engagement.
Count in Supplier Scorecard	Alphanumeric	No	Enter 'yes' to include the engagement for consideration in the Supplier Scorecard. 'no' is entered by default (no value).
Custom Field 1-n	Alphanumeric Note: Field input must conform to the input format defined for the custom field.	Yes (conditional) If custom fields are mapped in the process configuration, then one column must be configured for each mapped field. In the input file the column names remain 'Custom Field<field_number>'.	Enter custom field values in the order that you define them in bulk upload interface. For more information about this process, see Use Bulk Upload. Note: If you have a custom fields set to require values (Configuration > Settings > Custom Fields > <field_type> > <field_name> > Allow Null Info), then the field must contain a value in the upload file.
Effective Date	MM/DD/YYYY	Yes	Enter the effective date for the edits to the engagement.
Justification	Alphanumeric	Yes	Enter the description the edit to the engagement.