A task record stores details about a unit of work to be completed. NetSuite supports the creation of two different types of tasks: CRM Tasks and Project Tasks. The Tasks import supports the import of CRM tasks, not project tasks. CRM tasks, usually labeled Tasks in the NetSuite user interface, do not have to be associated with projects.
The CRM tasks data that you can import depend on the fields available on either your preferred Task form, or the custom task form selected on the Import Assistant Import Options page. For details about specifying a custom form, see Set Advanced CSV Import Options. For details about fields that can be mapped in the Task record. You can use the field definitions here as a basis for creating your own CSV import template file. For information about working with the Schema Browser, see Working with the SuiteTalk Schema Browser.
Be aware of the following:
- Required task fields for import are: Assigned To, Due Date, Priority, Start Date, Status, and Title.
- You need to understand the use of the Start Date and End Date fields on task records, and to exercise care when you format values for the Start Date, End Date, and Due Date fields in your CSV files. To avoid errors, review and follow the guidelines in Setting Date Field Values for Tasks Imports.
- Unlike in the user interface, the Assigned To field does not default to be the logged in user. You need to include values for this field in your CSV file or set up a default on the Import Assistant Field Mapping page. See Assigning Default Values during Field Mapping.
- The Send Email field is not available for import mapping. Imports cannot send email to task assignees.
- The Tasks import supports the import of the following sublist data
|Contacts||selectively updatable based on Company/Project(Entity) or Contact key fieldMaps to Companies and Contacts subtab on Related Records subtab of Task record, can include other records, such as customers and contacts, that are related to each task.|
|Time Tracking||when Time Tracking feature enabled|
- If you are doing a tasks import for the addition of new tasks, select the Add data handling option, rather than Add or Update.
- If you need to use an import to update existing task records, you must map either the Internal ID or External ID field to uniquely identify records. This requirement is enforced when you select the Update data handling option and when you select the Add or Update data handling option. The Title field is not a key field and does not have to be unique.
Setting Date Field Values for Tasks Imports
Before you set up a CSV file for a tasks import, you need to understand how Start Date and End Date fields are used, and you need to be aware of formatting requirements for Start Date, End Date, and Due Date field values.
Understanding Start Date and End Date Fields
You can review the standard Task form to understand the use of the Start Date and End Date fields in task records, in order to properly specify their values in your CSV files.
- Reserve Time - Indicates whether to schedule time for the task on the assignee's calendar. How the Start Date and End Date fields are used depends upon whether Reserve Time is enabled (set to True). By default, Reserve Time is not enabled (set to False).
- Start Date - The date when a task is started, as shown in the field labeled Start Date on the standard Task form. If Reserve Time is enabled, the Start Date value should also include a time that is the beginning of reserved time on the assignee's calendar, as shown in the field labeledStart Time.
- End Date - If Reserve Time is enabled, the time that is the end of reserved time on the assignee's calendar, as shown in the field labeled End Time on the standard Task form. The date is not shown, and is assumed to be the same as the date in the Start Date field.
Formatting Guidelines for Task Date Field Values
Follow these guidelines when you enter values for date fields in CSV files used for tasks imports.
- For Start Date fields:
- If Reserve Time is set to False, a Start Date value requires only a date, for example:04/12/2010. If a time is included, it is ignored.
- If Reserve Time is set to True, Start Date requires both a date and a time, for example:04/12/2010 09:00 AM
- For End Date fields:
- If Reserve Time is set to False, no End Date value is required.
- If Reserve Time is set to True, End Date requires both a date, that should be the same as the date set for Start Date, and a time, for example: 04/12/2010 11:00 AM.
- For Start Date, End Date, and Due Date fields, values should be specified according to the NetSuite Date Format, and if applicable, Time Format, set at Home > Set Preferences for the user doing the import. The following are example formats:
- Date Format is MM/DD/YYYY.
- Time Format is hh:mm AM/PM.
- For a Start Date or End Date field that includes both date and time, a space should be included between them, for example: 04/12/2010 10:00 AM.
If your tasks import returns date-related errors such as “You have entered an Invalid Field Value” or “Due Date occurs before Start Date”, try removing leading zeros from date values in your CSV file, for example changing 08/01/2010 to 8/1/2010.
- To avoid Excel formatting errors for Start Date, End Date, and Due Date values, it is recommended that you right-click the column and choose Format Cells to explicitly select a format that matches the Date Format (and if applicable, Time Format) set up in NetSuite.