Difference between revisions of "Creating Custom Fields"
Nancy Sabo (talk | contribs) |
Nancy Sabo (talk | contribs) |
||
| Line 44: | Line 44: | ||
'''Field Name''': This should be unique (to simplify locating and referencing it at a later date) and can only contain alphanumeric, underscore, or dash characters. | '''Field Name''': This should be unique (to simplify locating and referencing it at a later date) and can only contain alphanumeric, underscore, or dash characters. | ||
Once these settings are populated, you can '''Save''' your new field, or add further specifications. | Once these settings are populated, you can '''Save''' your new field, or add further specifications. | ||
| + | |||
| + | Tip: To modify a custom field, you can use [[Configuration Mode]] from within a record. Enable it from the Options menu, then select the field. | ||
==See Also== | ==See Also== | ||
| Line 201: | Line 203: | ||
[[Image:Creat19.png]]--> | [[Image:Creat19.png]]--> | ||
| − | <!--<span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name="Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1">{{ | + | <!--<span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name="Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1"><span class="mceNonEditable template" id="bs_template:@@@TPL1@@@" data-bs-name=" Template:Move to Common Level" data-bs-type="template" data-bs-id="1">{{ Template:Move to Common Level }}</span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span></span>--> |
[[Category:System Management]][[Category:Custom Fields]] | [[Category:System Management]][[Category:Custom Fields]] | ||
Latest revision as of 15:14, 9 October 2018
 Please note that this page is currently under construction. There is more information to come.
|
Overview
Custom fields can be created at any time, and associated with any one of a list of objects: UTA records (at any level), contacts (Users), companies (Organizations), and roles. They can be accessed and controlled via links on the Global Settings page or on the Entity Settings Page within a UTA, and that's also where they can be created.
Locating and Viewing a Custom Field
To see a list of all custom fields, navigate to Global Settings > System tab > Custom Fields. From here, you can search for and modify any custom field; click on any of the column headings to sort by that column.
This page in Global Settings is also where you can view all Deleted Fields--click on the Deleted Fields button in the top left-hand corner. From the Deleted Fields list view, you can either Restore or Purge any field: select the checkbox next to the desired field, then click either the Restore (clock) or Purge (garbage bin) button, and when the confirmation window appears, select 'yes' or 'no'.
Creation and Setup
When creating a new custom field, consider its intended function: what kind of data will it contain, and who will need to use it? These answers will directly affect field configuration.
To create a new custom field, navigate to the appropriate location (UTA, role, Organization settings or Contact settings) and then select the New Field button, which looks like a plus sign: '+'. The New Custom Field screen will then appear. The below table shows where each associated custom field can be created:
| Entity | Location |
| UTA: L1, 2 or 3 | Navigate to the desired UTA > Configuration Settings > L1, 2, or 3 Object Tab > Custom Fields |
| Role | Menu Icon > Roles and Security > User Roles > Edit Role > Custom Fields tab |
| Organization | Menu Icon > Global Settings > Organizations tab > Custom Fields |
| Contact/User | Menu Icon > Global Settings > Users tab > Custom Fields |
Only two values on this screen must be populated before you can save your new field:
- Field Type
- Field Name
Field Type: this choice will determine how the field will handle and display the data it will hold. For a complete list of all custom field types, see the table on the Custom Fields page.
Note: to see all available field types when creating a new custom field, enable Advanced Options on the top right of the display.
Field Name: This should be unique (to simplify locating and referencing it at a later date) and can only contain alphanumeric, underscore, or dash characters.
Once these settings are populated, you can Save your new field, or add further specifications.
Tip: To modify a custom field, you can use Configuration Mode from within a record. Enable it from the Options menu, then select the field.
See Also
Please visit Custom Fields General Information to see the more common custom field settings.
