Calculated Fields

this document reviews the calculated fields feature and the two different types of fields you can create if you are looking to create fields to house custom information for a candidate, job, project or offer, please check out docid\ qpgklrscmzgwc 7krbwds calculated fields are available on the plus, enterprise and legacy plans foundations legacy plus plus enterprise ❌ ✅ ✅ ✅ introduction calculated fields are an advanced feature that allow you to remap ats data for reporting purposes for example, you can take all sources from your ats and group them into a custom set of buckets when you create a new calculated field, you will give it a custom name and define the new field values once created, you can refer to that calculated field in all ashby reporting for filtering and grouping create a calculated field navigate to admin > data mapping > calculated fields click new in the upper right hand corner you can then select the object type on which you’d like your new field to exist, add a title, and select the calculated field type when creating a new calculated field you will have the choice of two types of field filter bucket field create multiple buckets and a filter for each bucket that defines which objects will be put into the bucket grouping field group values by selecting values that belong in a specific group add new buckets with custom names the names you select here will be the field values you can select or group by in reporting select each bucket’s field values the other bucket will contain all values that don't fall into any of the previous buckets and can't be edited grouping fields grouping fields allow you to define a set of buckets with custom values, and then map all existing values from your ats field of choice into the new categorization a classic example is taking a list of departments and mapping them into your organizations unique functional divisions calculated grouping fields are useful for mapping a known set of fixed values into a new set of custom buckets calculated grouping fields are useful for mapping a known set of fixed values into a new set of custom buckets the video below provides a quick introduction to calculated grouping fields please note that grouping calculated fields can only be done by fields of the following type a field that allows you to select multiple values from a finite set of selectable values a field that prompts you to select one value from a finite set of values a field that involves you selecting all/any that apply you can find more information on field types and the icons representing field types in our docid 7m9i sk7b8suzz0otx0nc filter bucket fields sometimes you do not have a fixed set of values that easily map into new categories but rather a dynamic set of complex logic that defines whether or not a value should fall into one category or another in such a situation, you will want to define the conditions of what should fall into a bucket, and we provide this via filter bucket fields an example might be categorization all jobs with “senior” or “director” in their titles to a “leadership” bucket, and all jobs with “new grad” into a “new grad” bucket to easily collate a large and diverse set of jobs into broad categories filter fields take a unique filter condition as a definition for each bucket to automate categorization filter fields take a unique filter condition as a definition for each bucket to automate categorization the following short video reviews creating filter bucket fields faq can i create buckets for my calculated fields that filter based on other calculated fields? you can, yes! when clicking + add field to match to configure the criteria for your bucket, you can select other calculated fields and their buckets to filter with this is helpful for creating sophisticated logical combinations and customizations