Field Comparison Filters

introduction the traditional filter interaction follows a paradigm of letting you pick a field or property and then specifying a property value to pull results for for example, filtering for interview stage = onsite would be specifying the value onsite for the field interview stage to match results accordingly this is the way ashby works today, with the additional layer of permitting logical combinations to achieve field comparison filter capabilities this paradigm is defined by selecting one field and specifying one or more values however, there are use cases where what you will not want to evaluate the value of a single field, but whether a field is related to a different field this represents a comparison of two fields, where a value is implicitly specified field comparison filters are available on the plus and enterprise plans true 148,148,148,150left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type a use case example for example, if you wanted to answer the question is the offer’s base salary within the opening’s approved compensation range? in the traditional paradigm of filtering, you select the offer’s base salary field and specific a filter value, say $90k $110k that works, but it does not scale if you have 40 offers in process, connected to 40 distinct openings with varying compensation ranges, you’d have to do a lot of reporting to check these conditions the way this works with field comparison filters is to directly compare the base salary field to the compensation range field and get a logical response yes or no this filter compares a salary field directly against a compensation range without having to specify the exact values the is between operator compares the field’s values under the hood and returns only those that match with that, you can make one filter to compare all records without having to specify the explicit values to compare using field comparison filters to access field comparison filters look for the field selector icon next to the filter value specification when clicking the field selector option you will be able to select a field for comparison in the above example, you may desire reviewing whether the hiring manager is the same as the recruiter, so you could compare them accordingly example use cases a few additional use cases are provided below to motivate your own creative applications you can review the video walkthrough that covers a few of the examples noted below for a quick overview offer and compensation comparisons a popular use case for this functionality is to review ensuring offer details match compensation ranges with this field comparison filter functionality, you can select for in band or out of band offers with ease, without having to specify individual compensation ranges applying a not operation the examples here are mostly shown by way of comparing “field1 = field2”, but many cases benefit from identifying discrepancies, in which case it’s most beneficial to apply a not operator this pattern is possible for all examples shown here, such as “show me records where field1 is not equal to field2” user comparisons generally, hiring team member or general user role comparisons can be of use these comparisons may look like check if hm’s are acting as recruiters recruiter = hiring manager check if an interviewer was also the referrer interviewer = referrer isolate feedback from hms feedback submitted by = hiring manager on job see if credit is due to hiring team member roles credited to = (jc’s hiring team role) data quality comparisons the user role comparison unlock various use cases, one such category being compliance and data quality across different object types ensuring jobs and openings have consistent records hiring manager on the job = hiring manager on the opening ensure offer level matches the job level offer’s job level = job’s level