Project requests Map-to feature [in-depth guide]
Guide contents: Define custom fields | Map-to | Tips & tricks | Resources
This guide will help you to understand and use the "Map-to" custom field option in project request forms.
The basic thing to understand here is that if you want a custom field in a project request to map to a custom field on a new project, then both fields MUST be defined exactly the same.
NOTE: On the project side, all project-selected custom fields will be visible, regardless if they are being mapped-to or not. This may be important if you have requested fields on the project side.
Define custom fields
Before we can use the Map-to option, we must first define both sides of this feature.
Project custom fields
Go to Menu > Admin > System setup > Custom fields > Project custom fields
For more information, please refer to the Custom fields overview [in-depth guide].
Project request custom fields
Go to Menu > Admin > Tracking > Define project requests > Edit "any" request > With "any" request open, click on Define fields
To define a custom field to use in a project request, click 'actions: define fields' located at the top of the screen.
To create a new field click the New button.
Field name: Required. Enter a descriptive name for the field. This is used for selecting the field in the project request.
Caption: Required. Enter an appropriate caption. This is what will be visible to people filling out the project request form.
Display type: Required. Select the appropriate field type.
Numeric: Allows entry of numbers and a period. Any other characters will break the functionality.
Currency: Allows entry of numbers & period. Any other characters will break the functionality.
Date: Allows entry of date based on your system style: but is in the format of MM/DD/YYYY. Any other characters or formats will break the functionality
Text: A text field is seen as a single line box of a defined # of characters.
Text area: A text field seen as a box of defined size, # of lines, # of characters.
Single checkbox: A single checkbox.
Multiple checkbox: Allows you to create individual checkboxes by entering a label & enter. Each line will be seen as an individual checkbox. Each checkbox can be selected individually.
Radio button: Allows you to create a list from which you can only select one via a radio button style.
Dropdown: Allows you to create a dropdown list that can be selected from.
Separator text: A display field that can be used to separate groups of custom fields. The field can only be used once in the layout.
Description: Enter a description of the field. This is only seen in the Custom field list.
Hint: Enter a hint that will be visible as a blue 'i' icon. This is recommended for numeric, currency & date to demonstrate how data should be entered.
Required: If checked, this field must be filled in or the project request cannot move forward.
Map-to: This dropdown list allows you to select an existing project custom field. When a project is created from the project request, the field will map into the project custom field.
WARNING: The field type must match exactly or it will not map. For multiple checkboxes or dropdowns, the list order MUST be exactly the same in the project custom field & the project request custom field.
Active: Checked by default. It designates this field as an active field that will be available to be placed on a project request form.
Now that both fields are ready, do the following:
- Go to the Project request custom fields.
- Edit the field in question.
- Find the 'map-to' drop-down.
- Choose the project field you want this request field to map to.
If you have more fields to map, repeat the above steps for all fields.
Tips & tricks
On the project side, you can create "separator" or "tab" custom fields to make the data appear in a cleaner state. For example, request A has custom fields that map to the fields under tab A only. While request B has fields that only map to fields under tab B only. Then on the project side, you can click on the tab that is relevant to the project you are viewing.
NOTE: You can't hide project fields if they are to be visible, or used on at least one type of project. The best you can do is create categories like the above described.
Define project requests [in-depth guide]
Define spec sheets [in-depth guide]