Utilizing Hybrid Capability

To utilize this hybrid capability, when building your custom SQL query click Edit Properties, and select the Hybrid Base on which you wish to filter, and Save. The Hybrid Base chosen should match on the primary table of the query.

If you are seeking to filter by prospect- or person-scoped information, for example, you would select Prospects.

A "Hybrid Filters" section will appear below the query. While the setting makes the filters available, adding hybrid filters do not alone filter your custom SQL.

Example

For example, consider the following simple query:

select p.[first], p.[last], p.[email], r.[name] as [round]
from [application] a
inner join [person] p on (p.[id] = a.[person])
inner join [lookup.round] r on (r.[id] = a.[round])
where (p.[first] = 'John')

This query will pull all applicants who have the first name "John". If we want the additional hybrid filters to apply to the predefined query, we can update our custom SQL to include the following addition to the where clause:

select p.[first], p.[last], p.[email], r.[name] as [round]
from [application] a
inner join [person] p on (p.[id] = a.[person])
inner join [lookup.round] r on (r.[id] = a.[round])
where (p.[first] = 'John') and (p.[id] in (select [id] from @ids))

The @ids is a temporary table that consists of a single column containing unique identifiers based on the Hybrid Base selected (e.g. Applications: a.[id]; Prospects: p.[id], etc.) and the hybrid filters selected by the user.