Use this article to limit which records Data Logic evaluates against your Blueprint, so only records with the data your logic depends on are processed.
When you have the input and output mapping set for your template, Step 4. Filter Records is where you configure filters to limit which records Data Logic evaluates. By default, Data Logic evaluates all records of the selected object type in your CRM — filters narrow that scope down to only the records that match your filter criteria.
Getting to Step 4. Filter Records
- Navigate to Data Integrity > Data Logic.
- Complete 1. Pick Blueprint, 2. Input Mapping, and 3. Output Mapping.
- Click 4. Filter Records to expand this step.
How Filtering Works
Filters follow Insycle's standard filtering options—the same filter builder used elsewhere in Insycle's modules.
Using OR Logic to Broaden Filter Criteria
By default, filters in Data Logic use AND logic — a record must meet every condition you add to be evaluated. There are two ways to broaden a filter with OR logic instead, letting Data Logic evaluate records that match any of several conditions rather than all of them.
OR Within a Single Field
To match multiple possible values in the same field, use the pipe | character to separate terms in the Condition's value field. Most text-based Conditions — including Starts With, Contains, Contains Term, Ends With, and Is — support this OR syntax. For example, a filter using Country Contains Term with the value USA|Canada|Mexico would evaluate records where the Country field contains any of the three values.
OR Across Multiple Fields
To match across separate fields — for example, evaluating a record if either its Phone Number OR its Mobile Phone Number field exists — switch to the Advanced tab in Step 4. Filter Records. Fields added on the Filter tab appear here with a "+" preceding each one, indicating AND logic. Deleting the "+" changes that field's logic to OR relative to the others in the filter.
For full instructions and screenshots on switching from AND to OR logic in the Advanced tab, see Filter Records Using an OR Operator.
A common use of Filter Records is limiting evaluation to only the records that have values in every field on which your Blueprint's input columns depend. For example, a Blueprint matching on Country, State, and Industry together might use three filters:
- Country exists
- State exists
- Industry exists
This restricts Data Logic to evaluating only records that already have all three fields populated, so records missing one or more of those values aren't processed against the Blueprint at all.
The image above shows Step 4. Filter Records in the Data Logic module, with three filters configured: Country exists, State exists, and Industry exists.
For a complete breakdown of every filter function by field type, plus guidance on using regular expressions in a filter, see Search and Filter Data Like You Never Imagined Possible.
Next Steps in Configuring Data Logic
With your input mapping, output mapping, and filters in place, the next step is to verify the configuration works as expected before running it against your CRM. Continue to Testing Data Logic with Test Matching and Near-Miss Detection.
This article covers one part of the Data Logic configuration. For details on the other settings available in the module, see these related articles:
- Designing a Blueprint CSV
- Generate a Blueprint with AI
- Picking a Blueprint for Your Data Logic Template
- Configuring Data Logic Input Mapping
- How Blank Cells Are Evaluated in Blueprint Input and Output Columns
- Configuring Data Logic Output Mapping
- Testing Data Logic with Test Matching and Near-Miss Detection
Additional Resources
Frequently Asked Questions
- Check out the Data Logic & Blueprints FAQs to find answers to common questions about creating, editing, and applying Data Logic and Blueprints.
Related Help Articles