BlueConfetti

Guides / Flint Table Filter

FLINT TABLE FILTER · HOW-TO

Combine AND/OR filters for questions a simple dropdown cannot answer

Column filters answer “this and that.” Some questions need “this and (that or the other).” Advanced groups let you write that expression directly, nest it, and publish it as the page’s starting view.

What you will end with: Engineering AND (Blocked OR due this week) returning 5 of 24 tasks, a nested version that adds an estimate threshold and returns 4, and the expression published as the table’s default.

Why separate column filters fall short

In the column filters, several values chosen for one column match any of them, and filters on different columns must all match. Choosing Team Engineering, Status Blocked and Due This week therefore asks for Engineering tasks that are blocked and due this week. In the sample tracker, none are. The question is really Engineering AND (Blocked OR due this week).

Sample tracker: project-tracker.csv · 24 rows, 7 columns, fictional data.

First 4 rows
Task IDTaskTeamOwnerStatusDueEstimate
PRJ-101Checkout API timeout fixEngineeringPriya ShahBlocked2026-11-063
PRJ-102Billing page redesignDesignMateo RuizIn progress2026-11-125
PRJ-103Release notes draftDocsHana SatoTo do2026-11-132
PRJ-104Search index migrationEngineeringLiam O'NeillIn progress2026-11-108
Show all 24 rows
Task IDTaskTeamOwnerStatusDueEstimate
PRJ-101Checkout API timeout fixEngineeringPriya ShahBlocked2026-11-063
PRJ-102Billing page redesignDesignMateo RuizIn progress2026-11-125
PRJ-103Release notes draftDocsHana SatoTo do2026-11-132
PRJ-104Search index migrationEngineeringLiam O'NeillIn progress2026-11-108
PRJ-105Help center screenshotsDocsHana SatoDone2026-11-041
PRJ-106Support macro updateSupportAma MensahIn review2026-11-111
PRJ-107Launch email copyMarketingJonas BergIn progress2026-11-202
PRJ-108Accessibility fixesDesignMateo RuizBlocked2026-11-184
PRJ-109Rate limit alertsEngineeringPriya ShahTo do2026-11-143
PRJ-110Escalation runbookSupportAma MensahIn progress2026-11-272
PRJ-111Pricing FAQDocsLena FischerIn review2026-11-091
PRJ-112Webhook retry policyEngineeringLiam O'NeillBlocked2026-11-245
PRJ-113Customer webinar planMarketingJonas BergTo do2026-12-023
PRJ-114Status page wordingSupportAma MensahDone2026-11-051
PRJ-115Mobile layout reviewDesignNoor HaddadTo do2026-11-152
PRJ-116Data export test planEngineeringPriya ShahIn review2026-11-122
PRJ-117Partner briefing deckMarketingJonas BergBlocked2026-11-132
PRJ-118API changelogDocsLena FischerTo do2026-11-191
PRJ-119Trial onboarding emailsMarketingSofia CostaIn progress2026-11-163
PRJ-120Dependency upgradesEngineeringLiam O'NeillTo do2026-11-235
PRJ-121Ticket tag cleanupSupportTomás SilvaTo do2026-11-171
PRJ-122Icon refreshDesignNoor HaddadDone2026-11-022
PRJ-123Backup restore drillEngineeringPriya ShahTo do2026-11-303
PRJ-124Glossary updateDocsHana SatoIn progress2026-11-261

The worked examples use Monday 9 November 2026 as today. Relative date presets follow each reader’s device calendar, so on another day the same rule matches different rows. Where it matters, a fixed date range that reproduces the published result is included.

How advanced groups combine

Step 1: Build Engineering AND (Blocked OR due this week)

  1. Choose Filters, then Advanced groups. Keep Match groups as All groups (AND).
  2. Choose Add group. Set Rule column to Team, Rule condition to Equals and Rule value to Engineering. Choose Save rule. This is group 1.
  3. Choose Add group again. Create Status, Equals, Blocked and save it. This is group 2.
  4. Set Match rules in group 2 to Any rule (OR).
  5. Choose Add rule to group 2. Set Rule column to Due, Rule condition to Relative date and Rule date preset to This week. Save the rule.

The panel shows each group with its match setting and numbered rules. In outline:

Group 1   Match rules in group 1: All rules (AND)
  1.1. Team equals Engineering (Text)
Group 2   Match rules in group 2: Any rule (OR)
  2.1. Status equals Blocked (Text)
  2.2. Due: This week (Date, YYYY-MM-DD)

Choose Done. The count line reads 5 of 24 rows; sorted by Due:

Expected result: 5 of 24 rows, Due ascending
Task IDTaskOwnerStatusDueEstimate
PRJ-101Checkout API timeout fixPriya ShahBlocked2026-11-063
PRJ-104Search index migrationLiam O'NeillIn progress2026-11-108
PRJ-116Data export test planPriya ShahIn review2026-11-122
PRJ-109Rate limit alertsPriya ShahTo do2026-11-143
PRJ-112Webhook retry policyLiam O'NeillBlocked2026-11-245

Switch Match groups to Any group (OR) to see the difference: every Engineering task plus anything blocked or due this week, 14 rows in all. Switch back before continuing.

Step 2: Nest a third level

Suppose the meeting only cares about this week’s work if it is estimated at three days or more: Engineering AND (Blocked OR (due this week AND Estimate at least 3)).

  1. Choose Remove rule 2.2 to remove the plain due-this-week rule.
  2. Choose Add nested group to group 2. Create Due, Relative date, This week and save it. The nested group is group 2.2 and starts as All rules (AND).
  3. Choose Add rule to group 2.2. Set Rule column to Estimate, keep Rule type as Number, set Rule condition to At least and Rule value to 3. Save the rule.
Expected result: 4 of 24 rows
Task IDTaskStatusDueEstimate
PRJ-101Checkout API timeout fixBlocked2026-11-063
PRJ-104Search index migrationIn progress2026-11-108
PRJ-109Rate limit alertsTo do2026-11-143
PRJ-112Webhook retry policyBlocked2026-11-245

PRJ-116 drops out: it is due this week but estimated at 2 days. The blocked tasks stay regardless of estimate.

Step 3: Publish it as the starting view

  1. Choose Copy advanced filter settings. Copy everything in Advanced filter settings.
  2. Edit the page, open the macro settings, choose Column filters and advanced rules and paste into Default advanced filter groups.
  3. Starting view preview counts the matches. For the Step 1 expression it reports 5 of 24 rows match. Choose Save settings and publish.

Only the applied advanced groups are copied; search, column filters, sorting and layout are separate settings. The copied text names columns by header and stores relative presets, not dates:

Show the copied settings for the Step 1 expression
{
  "version": 1,
  "match": "all",
  "groups": [
    {
      "match": "all",
      "rules": [
        {
          "header": "Team",
          "condition": {
            "type": "text",
            "dateFormat": "iso",
            "operator": "equals",
            "value": "Engineering",
            "valueTo": "",
            "preset": ""
          }
        }
      ]
    },
    {
      "match": "any",
      "rules": [
        {
          "header": "Status",
          "condition": {
            "type": "text",
            "dateFormat": "iso",
            "operator": "equals",
            "value": "Blocked",
            "valueTo": "",
            "preset": ""
          }
        },
        {
          "header": "Due",
          "condition": {
            "type": "date",
            "dateFormat": "iso",
            "operator": "relative",
            "value": "",
            "valueTo": "",
            "preset": "thisWeek"
          }
        }
      ]
    }
  ]
}

If a header named in the settings is later renamed, readers see Check the table's default view, and the advanced default is skipped rather than partly applied. Build the rule again and copy fresh settings.

Limits and behavior