Available for | Roles | Super Admin |
Permissions | • Access Visual Insights Report Builder (Data Explorer) | |
Packages | LeverTRM for Enterprise, Advanced Analytics add-on LeverTRM for Enterprise or Advanced HR add-on for requisitions |
|
This article depicts and describes Lever's Data Explorer Ease of Use Updates scheduled to roll out in the Summer 2025 release. For release information, refer to our Summer 2025 Release Notes |
Data fields are used to compose your dashboard charts in Visual Insights. The Data Explorer gives you the ability to pull fields from a dataset into a chart that you can then filter and/or pivot to visualize the insights you wish to see. This article lists all data fields available in the Requisitions opportunities data set.
Read on to learn about the differences between the types and groups of data fields listed below. Given the large number of available data fields, we recommend using a keyword search on this webpage (Mac: ⌘ + F || Windows: Ctrl + F ) to locate fields in the data fields table.
For instructions on how you can use the data fields in the 'Requisition opportunities' data set to build custom charts, refer to our help article on how to use the Data Explorer to build custom charts.
Understanding data fields
Data fields are organized by type and group in the picker. There are also functional considerations to consider when including specific data fields in a custom chart. This section provides an overview of data field types, groups, and functional considerations.
Types of data fields
There are three data field types you can select from when building a custom chart:
Dimensions
Dimensions are fields for non-aggregate data. Dimensions consist of a single data point.
Measures
Measures are fields for aggregate data, such as counts, sums, and averages.
Filter-only fields
Nearly all dimensions can also be used as filters. However, some fields can only be used as filters. These fields typically have logic related to advanced features.
Data field groups
In the 'Requisition opportunities' data set, data fields are organized into the following groups:
- Requisitions
- Requisition financials
- Requisition fields (1:n)
- Requisition fields choose by name
- Requisition fields pivot
- Postings
- Posting opportunities
- Posting opportunities conversion (1:n)
- Posting opportunities pipeline history (1:n)
- Dates and durations
- Period over period analysis
- Dynamic date by interval
- Formatted dates
- General
Functional considerations
Some data fields exhibit unique behaviour when added to a custom chart. Look for the following signifiers when adding data fields to understand how they will display in your chart:
Fan outs
If a data field has '(1:n)' appended to the end of its name, it means that field may result in a fan out when the report is run. A 'fan out' occurs when multiple results are returned for a single field. For example, if a 'Requisition fields (1:n)' data field is added to a chart visualized as a table, that field may yield multiple rows for a single opportunity (one for each stage it reached in the pipeline). To prevent the fanning out of multiple fields in a chart, try using 'Summary list' fields (see below).
Summary lists
If a data field has '(list)' appended to the end of its name, it means that if the field returns multiple results when the report is run, those results will be contained in single cell as a comma-separated list. For example, if a 'Opportunity sources (list)' data field is added to a chart visualized as a table, opportunities with multiple sources will have them listed in a single cell with each source separated by a comma.
Hyperlinks
If a data field has '(hyperlink)' appended to the end of its name, it means that results in this field will be clickable. Clicking the result will bring you to the corresponding item in your Lever environment. For example, if a 'Requisition ID (hyperlink)' field is added to a chart, clicking a posting title in the resulting chart will open that posting in Lever (in a new browser tab). User access permissions will be enforced when an item is clicked (i.e. if a user clicks the hyperlink for an item they do not have access to, Lever will prevent them from seeing it).
Data fields in the Requisition opportunities data set
|
Fields from the Opportunities and Postings data set can also be added as of the Spring 2025 release. Available fields in Summer 2025 release:
|
Requisitions | |
DIMENSIONS | |
Attributes | |
Requisition status | The current status of the requisition. |
Requisition status formatted | The current status of the requisition, capitalized. |
Requisition status sorted-ordered | The current status of the requisition ordered and capitalized. |
Age | Days from requisition create date till today. |
Aging 15, 30, 45 days bucket | Days from requisition create date till today in 15 day increments. |
Aging 30, 60, 90 days bucket | Days from requisition create date till today in 30 day increments. |
Employment status | Requisition employment status such as full-time, part-time, intern. |
Job department on the requisition | Requisition department. |
Job location on the requisition | Requisition location. |
Job team on the requisition | Requisition team. |
Requisition code | The code assigned to the requisition. |
Requisition description | The requisition description. The field is also known as internal notes. |
Requisition description (short) | The first 128 characters of the requisition description. The field is also known as internal notes. |
Requisition text | The description of the requisition. |
Conditions | |
Headcount infinite (yes/no) | Is this a requisition where hires are done as needed? (Sometimes referred to as evergreen.) |
Is backfill (yes/no) | Is this requisition for a backfill |
Is confidential (yes/no) | Is this requisition tied to a confidential posting. All requisitions shown in data explorer are not confidential. |
People | |
Requisition creator email | The email of the requisition creator |
Requisition creator name | The name of the requisition creator |
Requisition hiring manager email | The email of the requisition hiring manager |
Requisition hiring manager name | The name of the requisition hiring manager |
Requisition owner email | The email of the requisition owner |
Requisition owner name | The name of the requisition owner |
Headcount | |
Headcount active offers | The number of active offers against the requisition. |
Headcount hired | The number of headcount hired so far on the requisition |
Headcount open | Open headcount = total headcount - hired headcount - active offer count. |
Headcount total | The headcount for the requisition. |
Last close date | |
Last close date (UTC) | The last requisition event date where the requisition was closed. date (UTC) |
Last close date second (UTC) | The last requisition event date where the requisition was closed. second (UTC) |
Last open date | |
Last open date (UTC) | The last requisition event date where the requisition was last opened. |
Last open date second (UTC) | The last requisition event date where the requisition was last opened. |
Last rejected | |
Last rejected date | The most recent date of an event where the requisition was rejected date |
Last rejected hhmm | The most recent date of an event where the requisition was rejected hhmm |
Last rejected millisecond | The most recent date of an event where the requisition was rejected millisecond |
Last rejected date (UTC) | The most recent date of an event where the requisition was rejected date (UTC) |
Last rejected hhmm (UTC) | The most recent date of an event where the requisition was rejected hhmm (UTC) |
Last rejected millisecond (UTC) | The most recent date of an event where the requisition was rejected millisecond (UTC) |
Last updated | |
Last Updated date (UTC) | The last requisition event date where the requisition was updated. date (UTC) |
Last Updated second (UTC) | The last requisition event date where the requisition was updated. second (UTC) |
Requisition approvers | |
Requisition approval status | A calculated approval status. If the requisition status is open then Approved, if the requisition status is rejected then Rejected, otherwise a blank is returned. |
Approver 2 decided at date | The date that the approver made a decision |
Last approval date | The most recent date of an event where the requisition was approved (opened) date |
Approver 1 decided hhmm | The date that the approver made a decision |
Approver 2 decided hhmm | The date that the approver made a decision |
Approver 3 decided hhmm | The date that the approver made a decision |
Approver 4 decided hhmm | The date that the approver made a decision |
Approver 5 decided hhmm | The date that the approver made a decision |
Approver 6 decided hhmm | The date that the approver made a decision |
Approver 7 decided hhmm | The date that the approver made a decision |
Approver 8 decided hhmm | The date that the approver made a decision |
Approver 9 decided hhmm | The date that the approver made a decision |
Last approval hhmm | The most recent date of an event where the requisition was approved (opened) hhmm |
Approver 10 decided hhmm | The date that the approver made a decision |
Last approval millisecond | The most recent date of an event where the requisition was approved (opened) millisecond |
Last approval second | The most recent date of an event where the requisition was approved (opened) millisecond |
Last approval date (UTC) | The most recent date of an event where the requisition was approved (opened) |
Last approval hhmm (UTC) | The most recent date of an event where the requisition was approved (opened) |
Approver 1 decided at (UTC) | The date that the approver made a decision |
Approver 2 decided at (UTC) | The date that the approver made a decision |
Approver 3 decided at (UTC) | The date that the approver made a decision |
Approver 4 decided at (UTC) | The date that the approver made a decision |
Approver 5 decided at (UTC) | The date that the approver made a decision |
Approver 6 decided at (UTC) | The date that the approver made a decision |
Approver 7 decided at (UTC) | The date that the approver made a decision |
Approver 8 decided at (UTC) | The date that the approver made a decision |
Approver 9 decided at (UTC) | The date that the approver made a decision |
Approver 10 decided at (UTC) | The date that the approver made a decision |
Last approval second (UTC) | The most recent date of an event where the requisition was approved (opened) |
Approver 1 decided at second (UTC) | The date that the approver made a decision |
Approver 2 decided at second (UTC) | The date that the approver made a decision |
Approver 3 decided at second (UTC) | The date that the approver made a decision |
Approver 4 decided at second (UTC) | The date that the approver made a decision |
Approver 5 decided at second (UTC) | The date that the approver made a decision |
Approver 6 decided at second (UTC) | The date that the approver made a decision |
Approver 7 decided at second (UTC) | The date that the approver made a decision |
Approver 8 decided at second (UTC) | The date that the approver made a decision |
Approver 9 decided at second (UTC) | The date that the approver made a decision |
Approver 10 decided at second (UTC) | The date that the approver made a decision |
Approver 1 ID | The user id of the first approver. |
Approver 1 decision | The decision of the first approver. |
Approver 1 email | The email address of the first approver. |
Approver 1 name | The name of the first approver. |
Approver 1 order | Approver 1 order |
Approver 1 responded | The first approver has responded. |
Approver 1 step | Approver 1 step |
Approver 2 ID | The user id of the second approver. |
Approver 2 decision | The decision of the second approver. |
Approver 2 email | The email address of the second approver. |
Approver 2 name | The name of the second approver. |
Approver 2 order | Approver 2 order |
Approver 2 responded | The second approver has responded. |
Approver 2 step | Approver 2 step |
Approver 3 ID | The user id of the third approver. |
Approver 3 decision | The decision of the third approver. |
Approver 3 email | The email address of the third approver. |
Approver 3 name | The name of the third approver. |
Approver 3 order | Approver 3 order |
Approver 3 responded | The third approver has responded. |
Approver 3 step | Approver 3 step |
Approver 4 ID | The user id of the fourth approver. |
Approver 4 decision | The decision of the fourth approver. |
Approver 4 email | The email address of the fourth approver. |
Approver 4 name | The name of the fourth approver. |
Approver 4 order | Approver 4 order |
Approver 4 responded | The fourth approver has responded. |
Approver 4 step | Approver 4 step |
Approver 5 ID | The user id of the fifth approver. |
Approver 5 decision | The decision of the fifth approver. |
Approver 5 email | The email address of the fifth approver. |
Approver 5 name | The name of the fifth approver. |
Approver 5 order | Approver 5 order |
Approver 5 responded | The fifth approver has responded. |
Approver 5 step | Approver 5 step |
Approver 6 ID | The user id of the sixth approver. |
Approver 6 decision | The decision of the sixth approver. |
Approver 6 email | The email address of the sixth approver. |
Approver 6 name | The name of the sixth approver. |
Approver 6 order | Approver 6 order |
Approver 6 responded | The sixth approver has responded. |
Approver 6 step | Approver 6 step |
Approver 7 ID | The user id of the seventh approver. |
Approver 7 decision | The decision of the seventh approver. |
Approver 7 email | The email address of the seventh approver. |
Approver 7 name | The name of the seventh approver. |
Approver 7 order | Approver 7 order |
Approver 7 responded | The seventh approver has responded. |
Approver 7 step | Approver 7 step |
Approver 8 ID | The user id of the eighth approver. |
Approver 8 decision | The decision of the eighth approver. |
Approver 8 email | The email address of the eighth approver. |
Approver 8 name | The name of the eighth approver. |
Approver 8 order | Approver 8 order |
Approver 8 responded | The eighth approver has responded. |
Approver 8 step | Approver 8 step |
Approver 9 ID | The user id of the ninth approver. |
Approver 9 decision | The decision of the ninth approver. |
Approver 9 email | The email address of the ninth approver. |
Approver 9 name | The name of the ninth approver. |
Approver 9 order | Approver 9 order |
Approver 9 responded | The ninth approver has responded. |
Approver 9 step | Approver 9 step |
Approver 10 ID | The user id of the tenth approver. |
Approver 10 decision | The decision of the tenth approver. |
Approver 10 email | The email address of the tenth approver. |
Approver 10 name | The name of the tenth approver. |
Approver 10 order | Approver 10 order |
Approver 10 responded | The tenth approver has responded. |
Approver 10 step | Approver 10 step |
Requisition time to fill (TTF) | |
Approved to TTF end | The days from when the requisition was approved to the fill end date. |
Approved to closed | The days from when the requisition was approved to the most recent requisition close date |
Approved to employee start | The days from when the requisition was approved to when the employee starts, related to offers. |
Approved to headcount filled | The days from when the requisition was approved to when headcount is filled and latest closed. |
Created to TTF end | The days from the requisition created to the fill end date. |
Created to closed | The days from the requisition created to when latest closed. |
Created to employee start | The time from the requisition created to when the employee starts, related to offers. |
Created to headcount filled | The days from the requisition created to when headcount is filled and latest closed. |
TTF start to TTF end | The days from the requisition time to fill (TTF) start date to the time to fill end date. |
TTF start to closed | The days from the requisition time to fill (TTF) start date to when latest closed. |
TTF start to employee start | The days from the requisition time to fill (TTF) start date to when the employee starts, related to offers. |
TTF start to headcount filled | The days from the requisition time to fill (TTF) start date to when headcount is filled and latest closed. |
Dates used for time to fill (TTF) | |
TTF end date | A time to fill (TTF) end date. Used in several time to fill calculations. |
TTF end employee start | A time to fill (TTF) end date, based on employee start date from the related offer. Used in several time to fill calculations. |
TTF end headcount filled | A time to fill (TTF) end date, based on requisition headcount filled and latest closed. Used in several time to fill calculations. |
TTF end latest closed | A time to fill (TTF) end date, based on requisition latest closed. Used in several time to fill calculations. |
TTF start approved | A time to fill (TTF) start date, based on latest requisition approved date. Used in several time to fill calculations. |
TTF start created | A time to fill (TTF) start date, based on requisition created. Used in several time to fill calculations. |
TTF start date | The time to fill (TTF) start date. Used in several time to fill calculations. |
Time to fill end date. | The time to fill end date as entered on the requisition |
Time to fill start date | The time to fill start date as entered on the requisition |
Requisition created date | |
Requisition created at date | Requisition created at date |
Requisition created at hhmm | Requisition created at hhmm |
Requisition created at millisecond (UTC) | Requisition created at millisecond (UTC) |
Requisition created at second | Requisition created at second |
Requisition created at date (UTC) | Requisition created at date (UTC) |
Requisition created at hhmm (UTC) | Requisition created at hhmm (UTC) |
Requisition created at millisecond (UTC) | Requisition created at millisecond (UTC) |
Requisition created at second (UTC) | Requisition created at second (UTC) |
Requisition hire dates | |
Requisition hired count | The number of hires within the date range. The requisition must be directly associated to a opportunity. (date filter enabled) |
Requisition first hire | The first hire date for the requisition. Std date filter enabled. (date filter enabled) |
Requisition last hire | The last hire date for the requisition. (date filter enabled) |
Hyperlinks | |
Requisition ID (hyperlink) | The requisition id hyperlink to the Lever application |
Requisition description (hyperlink) | The requisition description. The hyperlink points to the requisition id in the Lever hire application. The field is also known as internal notes. |
Ids | |
Requisition ID | The requisition unique identifier. |
Account ID | Your account ID |
Job Location ID | The requisition job location identifier |
Job department ID | The requisition job department identifier |
Job department team ID | The requisition job department team identifier |
Requisition creator ID | The user id of the requisition creator |
Requisition hiring manager ID | The user id of requisition hiring manager |
Requisition owner ID | The user id of requisition owner |
MEASURES | |
Headcount | |
Total active offers | The total number of active offers Regardless of the number of times the requisition appears, its active offer count will only be included once in the total. |
Total headcount | The total headcount. Regardless of the number of times the requisition appears, its headcount will only be included once in the total. |
Total headcount open | The total open headcount. Headcount open = total headcount - hired - active offer count. Regardless of the number of times the requisition appears, its open count will only be included once in the total. |
Requisition time to fill (TTF) | |
Avg. TTF start to closed | Average days from the requisition time to fill (TTF) start date to when latest closed. |
Avg. TTF start to employee start | Average days from the requisition time to fill (TTF) start date to when the employee starts, related to offers. |
Avg. TTF start to end | Average days from the requisition time to fill (TTF) start date to the time to fill end date. |
Avg. TTF start to headcount filled | Average days from the requisition time to fill (TTF) start date to when headcount is filled and latest closed. |
Avg. approved to TTF end | Average days from when the requisition was approved to the fill end date. |
Avg. approved to closed | Average days from the requisition approved date to the headcount the most recent requisition close date. |
Avg. approved to employee start | Average days from when the requisition was approved to when the employee starts, related to offers. |
Avg. approved to headcount filled | Average days from when the requisition was approved to when headcount is filled and latest closed. |
Avg. created to TTF end | Average days from the requisition created to the fill end date. |
Avg. created to closed | Average days from the requisition created to when latest closed. |
Avg. created to employee start | Average time from the requisition created to when the employee starts, related to offers. |
Avg. created to headcount filled | Average days from the requisition created to when headcount is filled and latest closed. |
Median TTF start to closed | Median days from the requisition time to fill (TTF) start date to when latest closed. |
Median TTF start to employee start | Median days from the requisition time to fill (TTF) start date to when the employee starts, related to offers. |
Median TTF start to headcount filled | Median days from the requisition time to fill (TTF) start date to when headcount is filled and latest closed. |
Median approved to closed | Median days from the requisition approved date to the headcount the most recent requisition close date. |
Median approved to employee start | Median days from when the requisition was approved to when the employee starts, related to offers. |
Median approved to end | Median days from when the requisition was approved to the fill end date. |
Median approved to headcount filled | Median days from when the requisition was approved to when headcount is filled and latest closed. |
Median created to TTF end | Median days from the requisition created to the fill end date. |
Median created to closed | Median days from the requisition created to when latest closed. |
Median created to employee start | Median time from the requisition created to when the employee starts, related to offers. |
Median created to headcount filled | Median days from the requisition created to when headcount is filled and latest closed. |
Median days TTF start to end | Median days from the requisition time to fill (TTF) start date to the time to fill end date. |
Last rejected | |
Last rejected date | The most recent date of an event where the requisition was rejected date |
Last rejected date (UTC) | The most recent date of an event where the requisition was rejected date (UTC) |
Last rejected hhmm | The most recent date of an event where the requisition was rejected hhmm |
Last rejected hhmm (UTC) | The most recent date of an event where the requisition was rejected hhmm (UTC) |
Last rejected millisecond | The most recent date of an event where the requisition was rejected millisecond |
Last rejected millisecond (UTC) | The most recent date of an event where the requisition was rejected millisecond (UTC) |
Requisition | |
Last Updated date (UTC) | The last requisition event date where the requisition was updated. date (UTC) |
Last close date (UTC) | The last requisition event date where the requisition was closed. date (UTC) |
Last open date (UTC) | The last requisition event date where the requisition was last opened. |
Total hired | The total hired. Regardless of the number of times the requisition appears, its hired count will only be included once in the total. |
Requisition approvers | |
Last approval date | The most recent date of an event where the requisition was approved (opened) date |
Last approval date (UTC) | The most recent date of an event where the requisition was approved (opened) |
Last approval hhmm | The most recent date of an event where the requisition was approved (opened) hhmm |
Last approval hhmm (UTC) | The most recent date of an event where the requisition was approved (opened) |
Last approval millisecond | The most recent date of an event where the requisition was approved (opened) millisecond |
Requisition count | Count of distinct requisitions. |
Requisition financials | |
DIMENSIONS | |
Compensation bands | |
Requisition band min | The compensation band minimum of the requisition. |
Requisition band max | The compensation band maximum of the requisition. |
Requisition band currency | Currency for the compensation bands |
Requisition band interval | The compensation band interval of the requisition. |
Salary band percent | The salary range percent. Formula: (salary grade maximum - salary grade minimum/salary grade minimum) X 100. |
Offers | |
DIMENSIONS | |
Attributes | |
Offer status | The offer status of the offer for the opportunity |
Offer ID | The offer ID of the offer for the opportunity |
Postings | |
DIMENSIONS | |
Attributes | |
Posting ID (hyperlink) | Provides a html link to the posting in the Lever application. |
Posting additional | The additional field of a posting associated with the requisition |
Posting additional (short) | The first 132 characters of the additional field of a posting associated with the requisition |
Posting department | The department of the posting for the opportunity. |
Posting description | The description of a posting associated with the requisition |
Posting description (short) | The first 132 characters of the description of a posting associated with the requisition |
Posting location | The location of the posting for the opportunity. |
Posting location type | The location type associated with the posting. |
Posting salary currency | The currency for the posting salary. |
Posting salary description | The description of the posting salary range. |
Posting salary interval | The interval of the posting salary. |
Posting salary maximum | The maximum of the posting salary. |
Posting salary minimum | The minimum of the posting salary. |
Posting status | The status of a posting associated with the requisition |
Posting status capitalized | The status of a posting associated with the requisition |
Posting team | The team of the posting for the opportunity. |
Posting text | The text of a posting associated with the requisition |
Posting text (short) | The first 132 characters of the text of a posting associated with the requisition |
Posting work level | The work level of the posting for the opportunity. |
Posting work type | The work type of the posting for the opportunity. |
People | |
Posting hiring manager email | The email of the posting hiring manager for the opportunity. |
Posting hiring manager name | The name of the posting hiring manager for the opportunity. |
Posting owner email | The email of the posting owner for the opportunity. |
Posting owner name | The name of the posting owner for the opportunity. |
Posting created | |
Posting create date | The date the posting is created date |
Posting create hhmm | The date the posting is created hhmm |
Posting create millisecond | The date the posting is created |
Posting create week | The date the posting is created week |
Posting create month | The date the posting is created month |
Posting create quarter | The date the posting is created quarter |
Posting create year | The date the posting is created year |
Posting create date (UTC) | The date the posting is created date (UTC) |
Posting create hhmm (UTC) | The date the posting is created hhmm (UTC) |
Posting create millisecond (UTC) | The date the posting is created millisecond (UTC) |
Posting first published | |
Posting first published date | The most recent date the posting was published date |
Posting last closed | |
Posting last closed date | The most recent date the posting was closed date |
Posting last closed hhmm | The most recent date the posting was closed hhmm |
Posting last closed millisecond | The most recent date the posting was closed millisecond |
Posting last closed week | The most recent date the posting was closed week |
Posting last closed month | The most recent date the posting was closed month |
Posting last closed quarter | The most recent date the posting was closed quarter |
Posting last closed year | The most recent date the posting was closed year |
Posting last closed date (UTC) | The most recent date the posting was closed date (UTC) |
Posting last closed hhmm (UTC) | The most recent date the posting was closed hhmm (UTC) |
Posting last closed millisecond (UTC) | The most recent date the posting was closed millisecond (UTC) |
Posting last published | |
Posting first published hhmm | The most recent date the posting was published hhmm |
Posting first published millisecond | The most recent date the posting was published millisecond |
Posting first published week | The most recent date the posting was published week |
Posting first published month | The most recent date the posting was published month |
Posting first published quarter | The most recent date the posting was published quarter |
Posting first published year | The most recent date the posting was published year |
Posting first published date (UTC) | The most recent date the posting was published date (UTC) |
Posting first published hhmm (UTC) | The most recent date the posting was published hhmm (UTC) |
Posting first published millisecond (UTC) | The most recent date the posting was published millisecond (UTC) |
Posting last update | |
Posting last updated hhmm | The most recent data there was a posting event hhmm |
Posting last updated millisecond | The most recent data there was a posting event millisecond |
Posting last updated week | The most recent data there was a posting event week |
Posting last updated month | The most recent data there was a posting event month |
Posting last updated quarter | The most recent data there was a posting event quarter |
Posting last updated year | The most recent data there was a posting event year |
Posting last updated date (UTC) | The most recent data there was a posting event date (UTC) |
Posting last updated hhmm (UTC) | The most recent data there was a posting event hhmm (UTC) |
Posting last updated date | The most recent data there was a posting event date |
Posting last updated millisecond (UTC) | The most recent data there was a posting event millisecond (UTC) |
IDs | |
Posting ID | The posting id associated with the requisition. |
Posting department ID | The ID of the posting department for the opportunity. |
Posting department team ID | The ID of the posting department team for the opportunity. |
Posting hiring manager ID | The ID of the posting hiring manager for the opportunity. |
Posting job level ID | The ID of the posting job level for the opportunity. |
Posting job location ID | The ID of the posting job location for the opportunity. |
Posting job work type ID | The ID of the posting job work type for the opportunity. |
Posting owner ID | The ID of the posting owner for the opportunity. |
Posting opportunities | |
DIMENSIONS | |
EEO | |
Gender | Response to the EEO gender question. |
Race | Response to the EEO race question. |
People | |
Contact name | The name of the contact associated with the opportunity. |
Contact name (hyperlink) | A hyperlink to the opportunity in the Lever hire application. |
Opportunity archived by email | The email of who archived the opportunity. |
Opportunity archived by name | The name who archived the opportunity. |
Opportunity owner email | The email of the owner/recruiter for the opportunity |
Opportunity owner name | The name of the owner/recruiter for the opportunity |
Sourced by email | The email of who sourced the opportunity |
Sourced by name | The name of who sourced the opportunity |
Sources (1:n) | |
Opportunity source (1:n) | A source on the opportunity |
Source rank (1:n) | The ranking of the source. There are two origins of sources, applications and opportunities. The lower the ranking, the source was applied first. |
Source type (1:n) | The origin of the source. There are two origins of sources, applications and opportunities. A source can come from one or both. |
Source application rank (1:n) | The order in which sources that came from the applications process were applied to the opportunity. |
Source opportunity rank (1:n) | The order in which sources that came from the opportunities process were applied to the opportunity. |
Opportunity source id (1:n) | The ID of a opportunity-source combination |
Time to hire (TTH) | |
Opportunity create to hire | The number of days from when the opportunity is created until mark archived as hire. |
Contact location | |
Contact city | The location of the contact associated with the opportunity |
Contact country | The location of the contact associated with the opportunity |
Contact location name | The location of the contact associated with the opportunity |
Contact postal code | The postal code of the contact location |
Contact region | The region of the contact location |
Latitude | The location's latitude. |
Location geometry | The geometry of the location. Useful for specialized exports. Currently format is for a point. May be simpler to use the latitude and longitude directly |
Location geometry type | The type of geometry in location geometry. Currently always point. |
Location is structured (yes/no) | Is the location geographically structured? Are latitude and longitude available? |
Location source | The source of the contact information |
Location updated by ID | The user id that updated the location |
Location updated by email | The email of who updated the location. |
Location updated by name | Who updated the location. |
Longitude | The location's latitude. |
Map UK postcode area | Place this field on a map visualization to produce a map based on UK postcode areas. Includes only locations where GB is the country. |
Map US state | Place this field on a map visualization to produce a map based us states. Includes only locations where US is the country. |
Map US zip | Place this field on a map visualization to produce a map based us zip codes. Includes only locations where US is the country. |
Map country | Place this field on a map visualization to produce a map based on country code. |
Map latitude-longitude | Place this field on a map visualization. |
Other | |
Opportunity ID | The opportunity identifier |
Posting ID | The posting identifier associated with the opportunity |
Contact create | |
Opportunity hire date | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) |
Opportunity | |
Hire requisition | The ID of the requisition used to hire. Can be used when a posting is attached to multiple requisitions. |
Interviewers average feedback | The average of interviewers feedback for an opportunity. |
Is archived non-hire (yes/no) | The opportunity is archived and is not hired |
Is confidential (yes/no) | The posting associated with the opportunity is confidential |
Is hired (yes/no) | The opportunity has been archived as hired |
Is hired requisition (yes/no) | Indicates whether the opportunity was hired on this requisition. Used as a filter when a posting is attached to multiple requisitions. Attaching a posting to multiple requisitions is generally not recommended. |
Origin | The origin of an opportunity (agency, applied, internal, referred, sourced, university) |
Opportunity archive date | The opportunity archive date. (Includes archived as HIRED) date |
Opportunity create date | The create date of the opportunity |
Opportunity last advanced date | The opportunity last advanced date date |
Opportunity last interaction date | The opportunity last activity date date |
Opportunity archived | |
Opportunity archive hhmm | The opportunity archive date. (Includes archived as HIRED) hhmm |
Opportunity archive millisecond | The opportunity archive date. (Includes archived as HIRED) millisecond |
Opportunity archive week | The opportunity archive date. (Includes archived as HIRED) week |
Opportunity archive month | The opportunity archive date. (Includes archived as HIRED) month |
Opportunity archive quarter | The opportunity archive date. (Includes archived as HIRED) quarter |
Opportunity archive year | The opportunity archive date. (Includes archived as HIRED) year |
Opportunity archive date (UTC) | The opportunity archive date. (Includes archived as HIRED) date (UTC) |
Opportunity archive hhmm (UTC) | The opportunity archive date. (Includes archived as HIRED) hhmm (UTC) |
Opportunity archive millisecond (UTC) | The opportunity archive date. (Includes archived as HIRED) millisecond (UTC) |
Opportunity created | |
Opportunity create hhmm | The create date of the opportunity |
Opportunity create millisecond | The create date of the opportunity |
Opportunity create week | The create date of the opportunity |
Opportunity create month | The create date of the opportunity |
Opportunity create quarter | The create date of the opportunity |
Opportunity create year | The create date of the opportunity |
Opportunity create date (UTC) | The create date of the opportunity date (UTC) |
Opportunity create hhmm (UTC) | The create date of the opportunity |
Opportunity create millisecond (UTC) | Opportunity create millisecond (UTC) |
Opportunity hired | |
Opportunity hire hhmm | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) |
Opportunity hire millisecond | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) |
Opportunity hire week | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) |
Opportunity hire month | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) |
Opportunity hire quarter | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) |
Opportunity hire year | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) |
Opportunity hire date (UTC) | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) |
Opportunity hire hhmm (UTC) | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) |
Opportunity hire millisecond (UTC) | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) |
Opportunity last activity | |
Opportunity last interaction hhmm | The opportunity last activity date hhmm |
Opportunity last interaction millisecond | The opportunity last activity date millisecond |
Opportunity last interaction week | The opportunity last activity date week |
Opportunity last interaction month | The opportunity last activity date month |
Opportunity last interaction quarter | The opportunity last activity date quarter |
Opportunity last interaction year | The opportunity last activity date year |
Opportunity last interaction date (UTC) | The opportunity last activity date date (UTC) |
Opportunity last interaction hhmm (UTC) | The opportunity last activity date hhmm (UTC) |
Opportunity last interaction millisecond (UTC) | The opportunity last activity date millisecond (UTC) |
Opportunity last advance | |
Opportunity last advanced hhmm | The opportunity last advanced date hhmm |
Opportunity last advanced millisecond | The opportunity last advanced date millisecond |
Opportunity last advanced week | The opportunity last advanced date week |
Opportunity last advanced month | The opportunity last advanced date month |
Opportunity last advanced quarter | The opportunity last advanced date quarter |
Opportunity last advanced year | The opportunity last advanced date year |
Opportunity last advanced date (UTC) | The opportunity last advanced date date (UTC) |
Opportunity last advanced hhmm (UTC) | The opportunity last advanced date hhmm (UTC) |
Opportunity last advanced millisecond (UTC) | The opportunity last advanced date millisecond (UTC) |
Opportunity referral | |
A referrer user ID | The referrer user id for the opportunity |
Is this a social referral | Is this a social referral? |
Referrer email | The referrer email for the opportunity |
Referrer name | The referrer email for the opportunity |
Social referral code | Social referral code. |
Pipeline current state | |
Archive reason | The archive reason on the opportunity |
Archive reason ID | The archive reason ID on the opportunity |
Current account stage ID | The account stage ID when the opportunity is not archived. If the opportunity is archived, there is no value. |
Current account stage name | The account stage name when the opportunity is not archived. If the opportunity is archived, there is no value. |
Opportunity account stage name | The account stage name on the opportunity. Use current stage name to see the stage name of an active opportunity. |
Posting locations | |
Posting location is primary (yes/no)(1:n) | Is this the primary location. |
Posting location list (summary list) | A list of all locations on the posting. |
Posting location name (1:n) | The name of a posting location. |
Posting location rank (1:n) | The rank of a posting location. |
Summary List | |
A list of referral creator user IDs for the opportunity | A list of referral creator user IDs for the opportunity |
A list of referrer emails for the opportunity | A list of referrer emails for the opportunity (list) |
Application sources (list) | The sources associated with an application |
Interviewers who provided feedback (list) | A list of interviewers who provided feedback |
Opportunity completed stages (list) | The path the opportunity followed through the pipeline. When filtering, use filter option 'contains' to find specific list items. |
Opportunity education (list) | The list of educational institutions associated with the opportunity. |
Opportunity emails (list) | The list of emails associated with the opportunity. |
Opportunity files (list) | The list of files associated with the opportunity. |
Opportunity phones (list) | All phones numbers for the opportunity in a comma separated list |
Opportunity sources (list) | All sources for the opportunity in a comma separated list |
Opportunity tags (list) | All tags for the opportunity in a comma separated list |
Opportunity web links (list) | The list of web links associated with the opportunity. |
Posting IDs | A list of all posting IDs associated with a requisition |
Referrer names for the opportunity (list) | A list of referrer names for the opportunity |
Duration | |
Candidate time in current stage | The time from when opportunity entering the current stage until now when the opportunity is not archived. |
Days in pipeline | The number of days from when the opportunity is created until archived. |
Dates | |
Stage entered at (UTC) | The time the current non archived stage was entered. If the opportunity is archived no date is returned. |
IDs | |
Contact ID | The identifier of the contact associated with the opportunity. |
Opportunity ID (hyperlink) | The opportunity id hyperlink. When clicked upon will take you to the opportunity in the Lever application. |
Opportunity account stage ID | The account stage ID on the opportunity |
Opportunity archived by ID | The user ID of who archived the opportunity |
Opportunity owner ID | The user ID of the owner/recruiter for the opportunity |
Opportunity sourced by ID | The user ID of who sourced the opportunity |
MEASURES | |
Time to hire (TTH) | |
Median opportunity create to hired | The median time from when an opportunity is created to hired archive. If this is used with items that cause SQL fanning (such as progress steps and , the results will be inaccurate) |
Counts | |
Contacts | A distinct count of contacts |
Hires | A distinct count of hired opportunities. True if archived date is not null and the is hired flag is true. |
Opportunities | A distinct count of opportunities |
Duration | |
Average days from create to stage entry | The average number of days from when the opportunity is created to stage entry . |
Average days in stage | The average number of days from when the stage is entered to exit . |
Median days from create to stage entry | The median number of days from when the opportunity is created to stage entry . |
Median days in pipeline | The median number of days from when the opportunity is created until archived. |
Median days in stage | The median number of days from when the stage is entered to exit . |
Median time in current stage | The duration from when the opportunity entered a current stage in the pipeline until now. |
Posting opportunities conversion (1:n) | |
DIMENSIONS | |
Conversion attributes | |
Event Type | The event type associated with each conversion |
Event key | The unique key associated with each conversion |
Conversion from | |
From stage | The from stage of the conversion |
From milestone | From milestone |
From milestone (sort) | The from milestone sorted by rank. |
From pipeline (sort) | The pipeline that was the source of the conversion sorted by rank |
From pipeline ID | The pipeline that was the source of the conversion. |
From rank | Rank. Use as a hidden (Hide from visualization) sort. |
From stage ID | The from stage ID of the conversion |
Conversion to | |
To stage location | Converted to stage location. If stage event is opportunity-hired then Hired. If stage event is opportunity-archive then Archived. Otherwise the stage name is used. |
To milestone (sort) | To milestone. Sorted by lead, applicant, screen, onsite, offer. |
To milestone location | Converted to milestone location. If stage event is opportunity-hired then Hired. If stage event is opportunity-archive then Archived. Otherwise the milestone is used. |
To pipeline | The pipeline that is converted to. |
To pipeline (sort) | The pipeline that is converted to sorted by rank. |
Conversion movements | |
Advanced conversion | Conversion - advanced. 1 if the next stage has a higher rank, otherwise 0. |
Archive conversion | Conversion - archived. 1 if the next stage was an archive, otherwise 0. |
Hired conversion | Hired conversion. 1 if the next stage was a hire, otherwise 0. |
Moved back conversion | Move back conversion. 1 if the next stage was an archive, otherwise 0. |
Advanced milestone | Conversion - milestone advanced. 1 if the next milestone was a advance, otherwise 0. |
Archived milestone | Conversion - milestone archived. 1 if the milestone location is a archive, otherwise 0 |
Hired milestone | Conversion - milestone hired. 1 if the milestone location is a hire, otherwise 0 |
Moved back milestone | Conversion - milestone moved back. 1 if the next milestone moved back, otherwise 0. |
Conversion dates and duration | |
Days in stage | The time in days in this stage. |
Days to advance | The number of days spent in a stage before advancing |
Days to archive | The number of days spent in the stage before archiving |
Days to hire | The number of days spent in the final stage before hiring |
Days to move back | The number of days spent in a stage before moving back |
Stage enter date | The stage entry date. date |
Stage exit date | The stage exit date date |
Stage enter date (UTC) | The stage entry date. date (UTC) |
Stage exit date (UTC) | The stage exit date date (UTC) |
MEASURES | |
Conversion counts | |
Conversion count | The total number of conversions including advanced, moved back, archived and hired. |
Advanced count | The total number of advanced conversions. |
Archived count | The total of archived conversions. |
Hired count | The total of hired conversions. |
Moved back count | The total of conversions that moved back. |
Milestone conversions | The total number of milestone conversions. |
Archived milestone count | The number of archived conversions that occurred from the milestone. |
Hired milestone count | The total number of hired conversions that occurred from the milestone |
Moved back milestone count | The total number of conversions that moved back a milestone. |
Advanced milestone total | The total number of milestone advances. |
Conversion percents | |
Advanced percent | The percentage of advanced conversions to total conversions. |
Archived percent | The percentage of archived conversions to total conversions. |
Hired percent | The percentage of hired conversions to total conversions. |
Moved back percent | The percentage of conversions that moved back to total conversions. |
Advanced Ratio | The percentage of advanced conversions to total conversions. |
Archived ratio | The percentage of archived conversions to total conversions. |
Hired ratio | The ratio of hired conversions to total conversions. |
Moved back ratio | The percentage of conversions that moved back to total conversions. |
Advanced milestone percent | The percentage of advanced milestone conversions to total conversions. |
Archived milestone percent | The percentage of archived milestone conversions to total conversions. |
Hired milestone percent | The milestone percentage of hired conversions to milestone movements. |
Moved back milestone percent | The percentage of conversions that moved back to total conversions. |
Conversion average duration | |
Days in stage | The time in days in this stage. |
Avg. days to advance | The average number of days in the stage before advancing. |
Avg. days to archive | The average number of days in the final stage before archive conversion. |
Avg. days to hire | The average number of days in the final stage before hire conversion. |
Avg. days to move back | The average number of days in the stage before moving back. |
Posting opportunities pipeline history (1:n) | |
DIMENSIONS | |
Pipeline stage history (1:n) | |
Stage milestone (sort) (1:n) | The milestone of the stage for a pipeline stage change event. Sorted by rank. |
Stage pipeline name sorted (1:n) | The pipeline of the stage for a pipeline stage change event. Sorted by rank. |
Stage milestone name (1:n) | The milestone of the stage for a pipeline stage change event. Use for filtering. |
Stage name (1:n) | The stage name for a pipeline stage change event. Sorted by rank. |
Stage pipeline name (1:n) | The pipeline of the stage for a pipeline stage change event. |
Stage rank (1:n) | The rank of the stage for a pipeline stage change event. |
Pipeline stage enter (1:n) | |
Stage enter date (1:n) | The stage entry date date |
Stage enter hhmm (1:n) | The stage entry date hhmm |
Stage enter millisecond (1:n) | The stage entry date millisecond |
Stage enter week (1:n) | The stage entry date week |
Stage enter month (1:n) | The stage entry date month |
Stage enter quarter (1:n) | The stage entry date quarter |
Stage enter year (1:n) | The stage entry date year |
Stage enter date (UTC) (1:n) | The stage entry date date (UTC) |
Stage enter hhmm (UTC) (1:n) | The stage entry date hhmm (UTC) |
Stage enter millisecond (UTC) (1:n) | The stage entry date millisecond (UTC) |
Pipeline stage exit (1:n) | |
Stage exit date (1:n) | The stage exit date date |
Stage exit hhmm (1:n) | The stage exit date hhmm |
Stage exit millisecond (1:n) | The stage exit date millisecond |
Stage exit week (1:n) | The stage exit date week |
Stage exit month (1:n) | The stage exit date month |
Stage exit quarter (1:n) | The stage exit date quarter |
Stage exit year (1:n) | The stage exit date year |
Stage exit date (UTC) (1:n) | The stage exit date date (UTC) |
Stage exit hhmm (UTC) (1:n) | The stage exit date hhmm (UTC) |
Stage exit millisecond (UTC) (1:n) | The stage exit date millisecond (UTC) |
Pipeline previous stage (1:n) | |
Previous stage name (1:n) | The previous stage name for a pipeline stage change event. |
Previous stage enter date (1:n) | For a stage, when was the previous stage entered. |
Previous stage enter hhmm (1:n) | For a stage, when was the previous stage entered. |
Previous stage enter millisecond (1:n) | For a stage, when was the previous stage entered. |
Previous stage enter week (1:n) | For a stage, when was the previous stage entered. |
Previous stage enter month (1:n) | For a stage, when was the previous stage entered. |
Previous stage enter quarter (1:n) | For a stage, when was the previous stage entered. |
Previous stage enter year (1:n) | For a stage, when was the previous stage entered. |
Previous stage enter date (UTC) (1:n) | For a stage, when was the previous stage entered. |
Previous stage enter hhmm (UTC) (1:n) | For a stage, when was the previous stage entered. |
Previous stage enter millisecond (UTC) (1:n) | For a stage, when was the previous stage entered. |
Pipeline history (1:n) | |
Stage archive reason (1:n) | The archive reason of the stage for a pipeline stage change event. |
Stage name (1:n) | The stage name for a pipeline stage change event. |
Actor (1:n) | The actor associated with pipeline stage change event. |
Agency (1:n) | The agency associated with a pipeline stage change event. |
Event (1:n) | The event for a pipeline stage change event. |
Event capitalized (1:n) | The capitalized event for a pipeline stage change event. |
Is complete (yes/no) | Is stage complete. The next date is some date other than ''09/09/9999'::DATE' |
Duration | |
Days spent in completed stage | Event days spent in stage |
Pipeline - Opportunity create to stage enter | The duration from the opportunity created date to entering the stage for a pipeline stage change event |
Pipeline - Opportunity create to stage exit | The duration from the opportunity created date to exiting the stage for a pipeline stage change event |
Pipeline history IDs (1:n) | |
Previous stage id (1:n) | The previous stage id for a pipeline stage change event. |
Actor ID (1:n) | The event for a pipeline stage change event. |
Agency ID (1:n) | The agency associated with a pipeline stage change event. |
Event ID (1:n) | The event key for a pipeline stage change event. |
Stage milestone ID (1:n) | The milestone of the stage for a pipeline stage change event. |
Stage pipeline ID (1:n) | The pipeline ID of the stage for a pipeline stage change event. |
Event archive reason ID | If this was an archive event, the archive reason ID. |
Previous stage milestone (1:n) | Previous stage milestone name for a pipeline stage change event |
Previous stage pipeline (1:n) | Previous pipeline name for a pipeline stage change event |
Stage ID (1:n) | The stage ID for a pipeline stage change event. |
Posting opportunity tags (1:n) | |
DIMENSIONS | |
Opportunity tag ID | The id of the opportunity and tag relationship. |
Tag | The tag. |
Tag ID | The ID of the tag. A tag ID can be attached to many opportunities, |
Tag rank | The rank of the tag on the opportunity. |
Requisition fields pivot | |
DIMENSIONS | |
Requisition ID** | The requisition unique identifier. To display fields, the requisition id must be picked |
Requisition field label (pivot) ** | Requisition field label. Pivot on this field. |
Requisition field identifier | Requisition field internal identifier. This field may be used as a pivot instead of the label |
MEASURES | |
Pivoted requisition field value ** | Pivot by requisition field label or identifier. This is useful primarily for downloads. |
Requisition fields choose by name | |
FILTER_ONLY FIELDS | |
Choose custom fields | |
Set field01 | Use this filter to set which requisition field is used as field 01. For the filter to work properly, the 'is equal to' option must be used. |
Set field02 | Use this filter to set which requisition field is used as field 02. For the filter to work properly, the 'is equal to' option must be used. |
Set field03 | Use this filter to set which requisition field is used as field 03. For the filter to work properly, the 'is equal to' option must be used. |
Set field04 | Use this filter to set which requisition field is used as field 04. For the filter to work properly, the 'is equal to' option must be used. |
Set field05 | Use this filter to set which requisition field is used as field 05. For the filter to work properly, the 'is equal to' option must be used. |
Set field06 | Use this filter to set which requisition field is used as field 06. For the filter to work properly, the 'is equal to' option must be used. |
Set field07 | Use this filter to set which requisition field is used as field 07. For the filter to work properly, the 'is equal to' option must be used. |
Set field08 | Use this filter to set which requisition field is used as field 08. For the filter to work properly, the 'is equal to' option must be used. |
Set field09 | Use this filter to set which requisition field is used as field 09. For the filter to work properly, the 'is equal to' option must be used. |
Set field10 | Use this filter to set which requisition field is used as field 10. For the filter to work properly, the 'is equal to' option must be used. |
Set field11 | Use this filter to set which requisition field is used as field 11. For the filter to work properly, the 'is equal to' option must be used. |
Set field12 | Use this filter to set which requisition field is used as field 12. For the filter to work properly, the 'is equal to' option must be used. |
Set field13 | Use this filter to set which requisition field is used as field 13. For the filter to work properly, the 'is equal to' option must be used. |
Set field14 | Use this filter to set which requisition field is used as field 14. For the filter to work properly, the 'is equal to' option must be used. |
Set field15 | Use this filter to set which requisition field is used as field 15. For the filter to work properly, the 'is equal to' option must be used. |
Set field16 | Use this filter to set which requisition field is used as field 16. For the filter to work properly, the 'is equal to' option must be used. |
Set field17 | Use this filter to set which requisition field is used as field 17. For the filter to work properly, the 'is equal to' option must be used. |
Set field18 | Use this filter to set which requisition field is used as field 18. For the filter to work properly, the 'is equal to' option must be used. |
Set field19 | Use this filter to set which requisition field is used as field 19. For the filter to work properly, the 'is equal to' option must be used. |
Set field20 | Use this filter to set which requisition field is used as field 20. For the filter to work properly, the 'is equal to' option must be used. |
Set field21 | Use this filter to set which requisition field is used as field 21. For the filter to work properly, the 'is equal to' option must be used. |
Set field22 | Use this filter to set which requisition field is used as field 22. For the filter to work properly, the 'is equal to' option must be used. |
Set field23 | Use this filter to set which requisition field is used as field 23. For the filter to work properly, the 'is equal to' option must be used. |
Set field24 | Use this filter to set which requisition field is used as field 24. For the filter to work properly, the 'is equal to' option must be used. |
Choose custom user fields | |
Set user01 | Use this filter to set which user requisition field is used as user field 01. For the filter to work properly, the 'is equal to' option must be used. |
Set user02 | Use this filter to set which user requisition field is used as user field 02. For the filter to work properly, the 'is equal to' option must be used. |
Set user03 | Use this filter to set which user requisition field is used as user field 03. For the filter to work properly, the 'is equal to' option must be used. |
Set user04 | Use this filter to set which user requisition field is used as user field 04. For the filter to work properly, the 'is equal to' option must be used. |
Set user05 | Use this filter to set which user requisition field is used as user field 05. For the filter to work properly, the 'is equal to' option must be used. |
DIMENSIONS | |
Field values | |
Field 01 value (Use filter Set field 01) | Field 01 value. The value will be returned as text regardless of data type. |
Field 02 value (Use filter Set field 02) | Field 02 value. The value will be returned as text regardless of data type. |
Field 03 value (Use filter Set field 03) | Field 03 value. The value will be returned as text regardless of data type. |
Field 04 value (Use filter Set field 04) | Field 04 value. The value will be returned as text regardless of data type. |
Field 05 value (Use filter Set field 05) | Field 05 value. The value will be returned as text regardless of data type. |
Field 06 value (Use filter Set field 06) | Field 06 value. The value will be returned as text regardless of data type. |
Field 07 value (Use filter Set field 07) | Field 07 value. The value will be returned as text regardless of data type. |
Field 08 value (Use filter Set field 08) | Field 08 value. The value will be returned as text regardless of data type. |
Field 09 value (Use filter Set field 09) | Field 09 value. The value will be returned as text regardless of data type. |
Field 10 value (Use filter Set field 10) | Field 10 value. The value will be returned as text regardless of data type. |
Field 11 value (Use filter Set field 11) | Field 11 value. The value will be returned as text regardless of data type. |
Field 12 value (Use filter Set field 12) | Field 12 value. The value will be returned as text regardless of data type. |
Field 13 value (Use filter Set field 13) | Field 13 value. The value will be returned as text regardless of data type. |
Field 14 value (Use filter Set field 14) | Field 14 value. The value will be returned as text regardless of data type. |
Field 15 value (Use filter Set field 15) | Field 15 value. The value will be returned as text regardless of data type. |
Field 16 value (Use filter Set field 16) | Field 16 value. The value will be returned as text regardless of data type. |
Field 17 value (Use filter Set field 17) | Field 17 value. The value will be returned as text regardless of data type. |
Field 18 value (Use filter Set field 18) | Field 18 value. The value will be returned as text regardless of data type. |
Field 19 value (Use filter Set field 19) | Field 19 value. The value will be returned as text regardless of data type. |
Field 20 value (Use filter Set field 20) | Field 20 value. The value will be returned as text regardless of data type. |
Field 21 value (Use filter Set field 21) | Field 21 value. The value will be returned as text regardless of data type. |
Field 22 value (Use filter Set field 22) | Field 22 value. The value will be returned as text regardless of data type. |
Field 23 value (Use filter Set field 23) | Field 23 value. The value will be returned as text regardless of data type. |
Field 24 value (Use filter Set field 24) | Field 24 value. The value will be returned as text regardless of data type. |
User name values | |
User name 01 (Use filter Set user 01) | Requisition user field_01 name. |
User name 02 (Use filter Set user 02) | Requisition user field_02 name. |
User name 03 (Use filter Set user 03) | Requisition user field_03 name. |
User name 04 (Use filter Set user 04) | Requisition user field_04 name. |
User name 05 (Use filter Set user 05) | Requisition user field_05 name. |
Field special uses | |
Field 01 number (Use filter Set field 01) | Field 01 displayed as a number. If field_01 type is text, a null will be displayed. If field_01 type is a date, a very large strange number may be displayed. |
Field 02 number (Use filter Set field 02) | Field 02 displayed as a number. If field_02 type is text, a null will be displayed. If field_02 type is a date, a very large strange number may be displayed. |
Field 03 number (Use filter Set field 03) | Field 03 displayed as a number. If field_03 type is text, a null will be displayed. If field_03 type is a date, a very large strange number may be displayed. |
Field 04 number (Use filter Set field 04) | Field 04 displayed as a number. If field_04 type is text, a null will be displayed. If field_04 type is a date, a very large strange number may be displayed. |
Field 05 number (Use filter Set field 05) | Field 05 displayed as a number. If field_05 type is text, a null will be displayed. If field_05 type is a date, a very large strange number may be displayed. |
Field 06 number (Use filter Set field 06) | Field 06 displayed as a number. If field_06 type is text, a null will be displayed. If field_06 type is a date, a very large strange number may be displayed. |
Field 07 number (Use filter Set field 07) | Field 07 displayed as a number. If field_07 type is text, a null will be displayed. If field_07 type is a date, a very large strange number may be displayed. |
Field 08 number (Use filter Set field 08) | Field 08 displayed as a number. If field_08 type is text, a null will be displayed. If field_08 type is a date, a very large strange number may be displayed. |
Field 09 number (Use filter Set field 09) | Field 09 displayed as a number. If field_09 type is text, a null will be displayed. If field_09 type is a date, a very large strange number may be displayed. |
Field 10 number (Use filter Set field 10) | Field 10 displayed as a number. If field_10 type is text, a null will be displayed. If field_10 type is a date, a very large strange number may be displayed. |
Field 11 number (Use filter Set field 11) | Field 11 displayed as a number. If field_11 type is text, a null will be displayed. If field_11 type is a date, a very large strange number may be displayed. |
Field 12 number (Use filter Set field 12) | Field 12 displayed as a number. If field_12 type is text, a null will be displayed. If field_12 type is a date, a very large strange number may be displayed. |
Field 13 number (Use filter Set field 13) | Field 13 displayed as a number. If field_13 type is text, a null will be displayed. If field_13 type is a date, a very large strange number may be displayed. |
Field 14 number (Use filter Set field 14) | Field 14 displayed as a number. If field_14 type is text, a null will be displayed. If field_14 type is a date, a very large strange number may be displayed. |
Field 15 number (Use filter Set field 15) | Field 15 displayed as a number. If field_15 type is text, a null will be displayed. If field_15 type is a date, a very large strange number may be displayed. |
Field 16 number (Use filter Set field 16) | Field 16 displayed as a number. If field_16 type is text, a null will be displayed. If field_16 type is a date, a very large strange number may be displayed. |
Field 17 number (Use filter Set field 17) | Field 17 displayed as a number. If field_17 type is text, a null will be displayed. If field_17 type is a date, a very large strange number may be displayed. |
Field 18 number (Use filter Set field 18) | Field 18 displayed as a number. If field_18 type is text, a null will be displayed. If field_18 type is a date, a very large strange number may be displayed. |
Field 19 number (Use filter Set field 19) | Field 19 displayed as a number. If field_19 type is text, a null will be displayed. If field_19 type is a date, a very large strange number may be displayed. |
Field 20 number (Use filter Set field 20) | Field 20 displayed as a number. If field_20 type is text, a null will be displayed. If field_20 type is a date, a very large strange number may be displayed. |
Field 21 number (Use filter Set field 21) | Field 21 displayed as a number. If field_21 type is text, a null will be displayed. If field_21 type is a date, a very large strange number may be displayed. |
Field 22 number (Use filter Set field 22) | Field 22 displayed as a number. If field_22 type is text, a null will be displayed. If field_22 type is a date, a very large strange number may be displayed. |
Field 23 number (Use filter Set field 23) | Field 23 displayed as a number. If field_23 type is text, a null will be displayed. If field_23 type is a date, a very large strange number may be displayed. |
Field 24 number (Use filter Set field 24) | Field 24 displayed as a number. If field_24 type is text, a null will be displayed. If field_24 type is a date, a very large strange number may be displayed. |
Field 01 type (Use filter Set field 01) | The type associated with field_01. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_01 value dimension will return values as text regardless of the data type |
Field 02 type (Use filter Set field 02) | The type associated with field_02. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_02 value dimension will return values as text regardless of the data type |
Field 03 type (Use filter Set field 03) | The type associated with field_03. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_03 value dimension will return values as text regardless of the data type |
Field 04 type (Use filter Set field 04) | The type associated with field_04. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_04 value dimension will return values as text regardless of the data type |
Field 05 type (Use filter Set field 05) | The type associated with field_05. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_05 value dimension will return values as text regardless of the data type |
Field 06 type (Use filter Set field 06) | The type associated with field_06. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_06 value dimension will return values as text regardless of the data type |
Field 07 type (Use filter Set field 07) | The type associated with field_07. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_07 value dimension will return values as text regardless of the data type |
Field 08 type (Use filter Set field 08) | The type associated with field_08. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_08 value dimension will return values as text regardless of the data type |
Field 09 type (Use filter Set field 09) | The type associated with field_09. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_09 value dimension will return values as text regardless of the data type |
Field 10 type (Use filter Set field 10) | The type associated with field_10. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_10 value dimension will return values as text regardless of the data type |
Field 11 type (Use filter Set field 11) | The type associated with field_11. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_11 value dimension will return values as text regardless of the data type |
Field 12 type (Use filter Set field 12) | The type associated with field_12. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_12 value dimension will return values as text regardless of the data type |
Field 13 type (Use filter Set field 13) | The type associated with field_13. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_13 value dimension will return values as text regardless of the data type |
Field 14 type (Use filter Set field 14) | The type associated with field_14. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_14 value dimension will return values as text regardless of the data type |
Field 15 type (Use filter Set field 15) | The type associated with field_15. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_15 value dimension will return values as text regardless of the data type |
Field 16 type (Use filter Set field 16) | The type associated with field_16. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_16 value dimension will return values as text regardless of the data type |
Field 17 type (Use filter Set field 17) | The type associated with field_17. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_17 value dimension will return values as text regardless of the data type |
Field 18 type (Use filter Set field 18) | The type associated with field_18. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_18 value dimension will return values as text regardless of the data type |
Field 19 type (Use filter Set field 19) | The type associated with field_19. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_19 value dimension will return values as text regardless of the data type |
Field 20 type (Use filter Set field 20) | The type associated with field_20. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_20 value dimension will return values as text regardless of the data type |
Field 21 type (Use filter Set field 21) | The type associated with field_21. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_21 value dimension will return values as text regardless of the data type |
Field 22 type (Use filter Set field 22) | The type associated with field_22. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_22 value dimension will return values as text regardless of the data type |
Field 23 type (Use filter Set field 23) | The type associated with field_23. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_23 value dimension will return values as text regardless of the data type |
Field 24 type (Use filter Set field 24) | The type associated with field_24. The type is used for data investigation to verify that the field can be used as a date or number. Generally, unless there is a specific use case, the field_24 value dimension will return values as text regardless of the data type |
Field01 date (Use filter Set field 01) | The date associated with field_01. To return non-null results, the field_01 type must be date. |
Field02 date (Use filter Set field 02) | The date associated with field_02. To return non-null results, the field_02 type must be date. |
Field03 date (Use filter Set field 03) | The date associated with field_03. To return non-null results, the field_03 type must be date. |
Field04 date (Use filter Set field 04) | The date associated with field_04. To return non-null results, the field_04 type must be date. |
Field05 date (Use filter Set field 05) | The date associated with field_05. To return non-null results, the field_05 type must be date. |
Field06 date (Use filter Set field 06) | The date associated with field_06. To return non-null results, the field_06 type must be date. |
Field07 date (Use filter Set field 07) | The date associated with field_07. To return non-null results, the field_07 type must be date. |
Field08 date (Use filter Set field 08) | The date associated with field_08. To return non-null results, the field_08 type must be date. |
Field09 date (Use filter Set field 09) | The date associated with field_09. To return non-null results, the field_09 type must be date. |
Field10 date (Use filter Set field 10) | The date associated with field_10. To return non-null results, the field_10 type must be date. |
Field11 date (Use filter Set field 11) | The date associated with field_11. To return non-null results, the field_11 type must be date. |
Field12 date (Use filter Set field 12) | The date associated with field_12. To return non-null results, the field_12 type must be date. |
Field13 date (Use filter Set field 13) | The date associated with field_13. To return non-null results, the field_13 type must be date. |
Field14 date (Use filter Set field 14) | The date associated with field_14. To return non-null results, the field_14 type must be date. |
Field15 date (Use filter Set field 15) | The date associated with field_15. To return non-null results, the field_15 type must be date. |
Field16 date (Use filter Set field 16) | The date associated with field_16. To return non-null results, the field_16 type must be date. |
Field17 date (Use filter Set field 17) | The date associated with field_17. To return non-null results, the field_17 type must be date. |
Field18 date (Use filter Set field 18) | The date associated with field_18. To return non-null results, the field_18 type must be date. |
Field19 date (Use filter Set field 19) | The date associated with field_19. To return non-null results, the field_19 type must be date. |
Field20 date (Use filter Set field 20) | The date associated with field_20. To return non-null results, the field_20 type must be date. |
Field21 date (Use filter Set field 21) | The date associated with field_21. To return non-null results, the field_21 type must be date. |
Field22 date (Use filter Set field 22) | The date associated with field_22. To return non-null results, the field_22 type must be date. |
Field23 date (Use filter Set field 23) | The date associated with field_23. To return non-null results, the field_23 type must be date. |
Field24 date (Use filter Set field 24) | The date associated with field_24. To return non-null results, the field_24 type must be date. |
Requisition ID** | The requisition unique identifier. To display fields, the requisition id must be picked |
Requisition fields (1:n) | |
DIMENSIONS | |
Requisition ID** | The requisition unique identifier. To display fields, the requisition id must be picked. This field is a synonym for the vrq__req__requisition_id field. |
Requisition field identifier | Requisition field identifier.. |
Requisition field label | Requisition field label. |
Requisition field value | Requisition field value. |
Period over period analysis | |
FILTER_ONLY FIELDS | |
Period over period date range** | Defines the 'current period' which is used to compare against previous periods. The length of the date range should match 'Compare over' time period. The Period over period date range must be set for period over period analysis to return results. |
Number of previous periods | Apply this filter to add past periods to compare to (from the default of current vs 1 period ago). For instance, to compare this year to the previous two years, set to 2. Add this filter if more than 1 period. |
Compare over** | Typically set to year. To compare this year's time period to last years, set to year. The date range length must match the 'Compare over' value. The Compare over filter must be set for period over period analysis to return results. |
Display period** | Indicates the granularity that will be used for display. If 'compare over' is set to year and 'Display period' is set to quarter, then the quarters within each year will be displayed. The Display period filter must be set for period over period analysis to return results. |
DIMENSIONS | |
Prior Periods (pivot)** | Prior periods must be pivoted for period over period analysis to return understandable results. |
Reference date** | The reference date is required for period over period analysis to return understandable results. |
MEASURES | |
Requisition time to fill (TTF) | |
Requisition created to closed | Requisition time to fill from requisition open date to requisition close date. |
Opportunities archived | All archives including hires. |
Posting opportunities created | Posting opportunities by opportunity create date. |
Posting opportunities hired | Hired posting opportunities by opportunity hire date. |
Date intervals | |
FILTER_ONLY FIELDS | |
Set dynamic date interval ** | Controls the granularity of the date being displayed. This only works on dates that have (interval) in their title.. |
DIMENSIONS | |
Posting opportunities | |
Archived at Dynamic date interval | Opportunity archive date. The date interval (Year, quarter, month, week) as controlled by the dynamic interval filter. If the dynamic interval filter is not set, the interval defaults to month. |
Hired at Dynamic date interval | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) The date interval (Year, quarter, month, week) as controlled by the dynamic interval filter. If the dynamic interval filter is not set, the interval defaults to month. |
Archived at Dynamic date interval (UTC) | Opportunity archive date. The date interval (Year, quarter, month, week) as controlled by the dynamic interval filter. If the dynamic interval filter is not set, the interval defaults to month. |
Hired at Dynamic date interval (UTC) | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) The date interval (Year, quarter, month, week) as controlled by the dynamic interval filter. If the dynamic interval filter is not set, the interval defaults to month. |
Requisitions | |
Requisition created at (dynamic interval) | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) The date interval (Year, quarter, month, week) as controlled by the dynamic interval filter. If the dynamic interval filter is not set, the interval defaults to month. |
Requisition created at (dynamic interval UTC) | The opportunity hire date. (The date the opportunity is archived with the reason of HIRED.) The date interval (Year, quarter, month, week) as controlled by the dynamic interval filter. If the dynamic interval filter is not set, the interval defaults to month. |
Stage events | |
Stage entered Dynamic date interval (1:n) | The stage entry date The date interval (Year, quarter, month, week) as controlled by the dynamic interval filter. If the dynamic interval filter is not set, the interval defaults to month. |
Stage exit Dynamic date interval (1:n) | The stage exit date The date interval (Year, quarter, month, week) as controlled by the dynamic interval filter. If the dynamic interval filter is not set, the interval defaults to month. |
Stage entered Dynamic date interval (UTC) (1:n) | The stage entry date The date interval (Year, quarter, month, week) as controlled by the dynamic interval filter. If the dynamic interval filter is not set, the interval defaults to month. |
Stage exit Dynamic date interval (UTC) (1:n) | The stage exit date The date interval (Year, quarter, month, week) as controlled by the dynamic interval filter. If the dynamic interval filter is not set, the interval defaults to month. |
General | |
FILTER_ONLY FIELDS | |
Standard Date filter | Very handy generic filter for dashboards. On dashboards, associate the filter to date fields to control. The default start date is 1970-01-01. The default end date is tomorrow. Some calculations (such as average time in pipeline) use the filter. The picker label will indicate 'Use Standard filter'. |
DIMENSIONS | |
Now | |
Now date | Now in your local time zone |
Now hhmm | Now in your local time zone |
Now | Now in your local time zone |
Now date (UTC) | Now in UTC time. (Universal Time Coordinated) |
Now hhmm (UTC) | Now in UTC time. (Universal Time Coordinated) |
Now (UTC) | Now in UTC time. (Universal Time Coordinated) |
Local time zone {{ _user_attributes['lever_hire_user_timezone'] }} | Your current time zone in the hire system. |
Standard date filter | |
Standard date filter start | The value the filter used as the end date. If no start date is supplied, 1970-01-01 is used. Typically used only for understanding what values the filter is using. |
Standard date filter end | The value the filter used as the end date. If no end date is supplied, tomorrow is used. Typically used only for understanding what values the filter is using. |
MEASURES | |
Tally (generic count) | A generic count equal to the number of records returned by a query. |