Lookups with metadata
Metadata is data about data and provides even more flexibility for lookup use, enabling data associated directly with a particular lookup selection. When adding a lookup group, you can select a dataform to act as the metadata form for that group (see 1. Add a Lookup Group in Configuring lookups). These forms store information related to the lookup values used with the lookup group.
The Uses Metadata column shows whether a lookup has a metadata dataform associated with its lookup group and whether associated metadata has been configured for a specific lookup:
Three possible values can display in the Uses Metadata column:
Value |
Definition |
No |
There is no metadata associated with the lookup. |
Yes (Not Created) |
There is metadata associated with the lookup but it is not configured. |
Yes |
There is metadata associated with the lookup and it is configured. |
Examples
The Contract Type lookup in ClientSpace PEO has associated metadata that can determine:
- What Template is associated with the contract type?
- What Legal Entity / SUTA defaults are available when that contract type is selected?
- Default Workers' Comp Configuration for a workspace.
The Pay Frequency lookup in ClientSpace PEO has metadata associated that can determine:
- How many pay cycles per year for that frequency, such as Weekly = 52, SemiMonthly = 24, Bi-Weekly = 26.
- Minimum per check fee to ensure a certain amount of administrative costs are submitted for the year.
The Survey Rating lookup group is automatically linked to a Survey Metadata dataform. It contains a single field named Survey Rating (Integer Only). The field is used to store the integer equivalent of a survey rating value. This allows you to store survey results as numeric value (i.e., integer) metadata and use the metadata for calculations in Business Intelligence reports.
For example, if four survey recipients select 10 on a 1-10 point star rating scale, an integer value of 10 is associated with their selections. If another survey recipient selects 3, an integer value of 3 is associated with their selection. You can then use the integer metadata to calculate an average score of 8.6.
If you need help configuring metadata, please log an Extranet case.