Project Worker 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?	Notes/Description
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.)	This field is a primary key. If the worker identifier exists in the application, enter the value in this field. If you are creating a worker record, leave this field blank, and enter 'Yes' in the Create user account field.
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 woke engagement begins. This date is validated against the parent project start date.
Estimated End Date	MM/DD/YYYY	No	Enter the estimated end date for the worker engagement. This date is validated against the parent project end date.
Parent Project ID	Alphanumeric	No	Enter the parent project identifier.
Engagement ID	Alphanumeric	No	Enter the engagement identifier. This field can be used as a primary key if populated.
Manager GUID	Alphanumeric	No	Enter the manager identifier.
Time & Expense Approver	Alphanumeric	No	Enter the manager identifier.
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.
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.
Custom Field1 (1-n)	Alphanumeric Note: Field input must conform to the input format defined for the custom field.	No (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.