Fields
Fields store information about your org, your people, and your jobs. You can use them in tasks performed across ChartHop. For example, you might design a form for one-on-one meetings between your managers and their direct reports and leverage a custom field to capture feedback about what went well that week. Or, you might add a custom field that shows employee business units so members of your org can view that information on the Data Sheet.
This section describes how to work with fields and includes how to leverage the built-in fields that come with ChartHop as well as the custom fields you’ll create when you want to import unique data from your org.
Fields are made up of the following elements:
- Field label - Field name; indicates how a field is displayed in ChartHop.
- Field code - Unique identifier for a field; used in ChartHop’s search language, Carrot Query Language (CQL).
- Dated - Whether the field has an effective date; for example, the announce date for a new hire.
- Sensitivity - The level of data access a ChartHop user must have in order to view this field's data. Learn more.
- Category - Groupings for fields; defines how they’re displayed on the Data Sheet.
- In use - Whether the field has data stored against it, or if it calculates data based on other fields.
ChartHop comes with an extensive set of built-in fields, which store diverse data in features across the platform.
You cannot delete, modify, recategorize, or create new built-in fields. However, you can hide them on the Fields page. Learn more.
The following table contains built-in field examples.
Label | Field code | Data type | Description |
Age | age | Number | A person’s age, for example 34. |
Start Date | startDate | Date | The date on which a person joined your org, for example 6/1/2022. |
Band | band | Group | The compensation band to which a person is assigned, for example L3. |
You create custom fields when you need to store information that doesn’t fit into built-in fields.
For example, you might have a payroll system with proprietary data elements. You could design custom fields to map that information into ChartHop. Or, you might need a custom survey to capture employee feedback. You could add custom fields to store responses to each org-specific question.
The following table contains other custom field examples along with appropriate field codes and data types for clarity.
Label | Field code | Data type | Description |
1-on-1 Negatives | oooNeg | String (LongText) | On a custom form for one-on-one meetings, captures responses to the question, "What could have gone better over the past week?" |
Vaccination Status | vaccinationStatus | Enum (Single Select) | On a custom survey, captures responses to the question, "Are you currently vaccinated?" Has three options: Vaccinated, Unvaccinated, and Scheduled. |
