Custom fields can be included when importing and exporting schedules using the Touchplan Excel, MS Project, and P6 XLSX formats.
During an import, you can either import values into existing custom fields or create new custom fields directly from unmatched spreadsheet columns.
Add New Custom Fields to a Touchplan Project during Import
You can create new custom fields directly from unmatched spreadsheet columns during the import process.
Columns that do not match an existing custom field appear in Step 2, Custom Fields, of the import wizard.
For each new custom field column, users can:
Use the checkbox to choose whether to include or exclude the new custom field from the import.
Select the appropriate field type from the Field Type drop-down menu.
Choose which ticket types the custom field should appear on:
Tasks (selected by default)
Constraints
Milestones
Note: Custom fields created during an import are automatically available to all project roles.
Import Values into Existing Custom Fields
During an import, column headers in the Touchplan Ticket Import Template are matched to existing custom fields in the project. If a matching custom field is found, the imported value is applied to that field when creating new tickets or updating existing tickets.
To add custom fields to the Touchplan Ticket Import Template:
Click the Plan Actions tab in the top-right corner of the plan.
Select Import Tickets from the drop-down menu.
Click Download Blank Sample to download the Touchplan Ticket Import Template.
In the desired ticket type sheet, enter the name of your custom field as a column header in the next available blank column.
Save the completed template.
During the import, Touchplan will match the column header to an existing custom field in the project and apply the values to the imported tickets.
Click on the links below for additional resources on adding custom fields to the following formats:
Export Custom Fields from Touchplan
When exporting tickets out of a project, all active custom fields are included as columns after the standard export columns. Custom field values are preserved when exporting and can be updated during the import process.
Click on the links below for additional resources on exporting tickets out Touchplan in the following formats:
Best Practices:
Match column headers exactly: Differences in spelling, spacing, or capitalization may prevent a column from matching an existing custom field.
Review the Custom Fields step: Check unmatched columns before completing the import to avoid creating unintended fields.
Review warnings: Warnings do not mean the import failed. Review them to identify any custom field values that were skipped.
Confirm field types: Review the field type before creating a new custom field to ensure the data is formatted and validated correctly.