## TL;DR

A lookup filter on the field rejects the value. Check the field's lookup filter criteria and pick a value that passes it.

## Error

```text
FIELD_FILTER_VALIDATION_EXCEPTION
```

## Steps

1. Open the field's lookup filter definition Expected: you see the criteria.
2. Check your value against the filter Expected: you find the mismatch.
3. Pick a lookup value that satisfies the filter Expected: it passes.
4. Re-run the operation Expected: it succeeds.

## When to use

- FIELD_FILTER_VALIDATION_EXCEPTION
- A lookup filter rejects the value

## When not to use

- No lookup filter exists (then check validation rules)
- The filter is wrong (then fix the filter, not the data)

## Tool compatibility

- Salesforce lookup filters
- Data loads with lookups

## Variant phrasings

### field filter validation exception

The lookup filter rejects your value. Check its criteria.

### FIELD_FILTER_VALIDATION_EXCEPTION

Same: the value fails the field's lookup filter.

## Why it happens

Lookup filters are invisible in the API; agents see a valid ID and cannot understand why it is rejected.

## Edge cases

- Filters can depend on the source record's field values
- Optional vs required filter behavior differs

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CoPiKgrAKeXWQb6k0LYHrg
