Tasks Property Import Fields
Part of successfully importing items/objects into PSA is the PSA Microsoft Excel Import template (in .xlsx), which contains the necessary predefined tabs which allow you to specify the item/object properties to import.
Click here to view the article detailing how to import items/objects using Excel.
PSA Microsoft Excel Import Template: Tasks sheet
This article is designed to facilitate the smooth import of tasks into PSA using the Excel Import Template (.xlsx). It outlines the available fields, offering administrators concise descriptions to populate their Excel templates effectively. This resource aims to simplify the process, ensuring seamless task imports.
Let us delve into the key fields and empower you to efficiently transfer your task data into PSA.
Caution: Please be advised that it is recommended to fill all fields, even if no changes are intended. Leaving fields blank may result in some values reverting to their default settings.
| Task Property Import Fields | Definitions |
|---|---|
| Tenrox_Excel_Process_Status | Import status (populated by the system after the task import is processed) |
| UniqueId | - Upon Creation: The Unique ID of a new Task is automatically populated by the system once the creation process is completed. - Upon Update: The Unique ID of Tasks being updated must be entered by you, ensuring it matches the one initially generated by the system during the initial import. For further details on how to extract this Unique ID refer to Create a Report to View Unique Ids. Note: Do not edit this column if you are creating a new Task using Excel Import. |
| Name * | Name of the task (required field) |
| Project Name * | Name of the Project the task belongs to (required field) |
| WorkType_Name * | Name of the Work Type (required field) |
| Id | Task ID |
| Description | Description of the Task |
| State | Defines the State of the Task. Possible Values:
1 Low 2 Medium 3 Normal 4 High 5 Late 6 Critical |
| Priority | Defines the Task Priority. Possible Values:
1 Low 2 Medium 3 High 4 Important 5 Urgent |
| Start_Date | Defines the Task start date Note: Set column format to Date (MM/DD/YYYY). |
| End_Date | Defines the Task end date Note: Set column format to Date (MM/DD/YYYY). For Open Ended enter 11/27/2737 |
| Is_Suspended | Defines whether or not the task is suspended Note: Enter 1/0 for Yes/No. |
| Enable_ETC | Defines whether or not the ETC is enabled on the Task. Note: Enter 1/0 for Yes/No. |
| Project_Overhead | Defines whether or not the Task is considered a Cost / Overhead to the company Note: Enter 1/0 for Yes/No. |
| Payable | Defines whether or not the Payable attribute is set at the Task level Note: Enter 1/0 for Yes/No. |
| Billable | Defines whether or not the Billable attribute is set at the Task level Note: Enter 1/0 for Yes/No. |
| Capitalized | Defines whether or not the Capitalized attribute is set at the Task level Note: Enter 1/0 for Yes/No. |
| Funded | Defines whether or not the Funded attribute is set at the Task level Note: Enter 1/0 for Yes/No. |
| RandD | Defines whether or not the R&D attribute is set at the Task level Note: Enter 1/0 for Yes/No. |
| Time_Entry_Notes_Option | Defines the Task s Entry Notes option. Possible Values: PROJECTSETTINGS TEMPLATESETTINGS REQUIRED NOTALLOWED OPTIONAL |
| Is_Decommissioned | Defines whether the Task is Decommissioned Note: Enter 1/0 for Yes/No. |
| Used_By_Time | Defines whether or not the Task is used by Time. Note: Enter 1/0 for Yes/No. |
| Used_By_Expense | Defines whether or not the Task is used by Expense. Note: Enter 1/0 for Yes/No. |
| Used_By_Charge | Defines whether or not the Task is used by Charge. Note: Enter 1/0 for Yes/No. |
| Used_By_Product | Defines whether or not the Task is used by Product. Note: Enter 1/0 for Yes/No. |
| Used_By_Resource_Planning | Defines whether or not the Task is used by Resource Planning. Note: Enter 1/0 for Yes/No. |