I've found that SEARCH() in filterByFormula handles escaped double quotes differently depending on the field type. Backslash-escaped quotes work correctly on text fields but silently return no results on linked record fields.
Setup:
- Table "Registrations" has a linked record field {Rider} pointing to table "Riders"
- One of the records in the Riders table has the primary field value: Aubrey "Aub" Holland
- A Registrations record links to that Rider
- Table "Registrations" also has a plain text field {Direct name} where one of the values is Joe "Biggie" Smalls
When searching the Registration table I get different results with a very similar search depending on which field I search:
What Works (text field):
SEARCH("Joe \"Biggie\" Smalls", {Direct name}) != ""
Returns the matching record correctly.
What Fails (linked record field):
SEARCH("Aubrey \"Aub\" Holland", {Rider}) != ""
Returns zero results — no error, just an empty response. The formula is accepted as valid but doesn't match. This does work fine if I search for a rider by name where that name does not include quotes.
Environment: Using the POST /v0/{baseId}/{tableId}/listRecords endpoint with filterByFormula in the JSON body.
A not-great workaround I’ve found: Split the search value on the double-quote characters and AND together separate SEARCH conditions for each fragment:
AND(SEARCH("Aubrey ", {Rider}) != "", SEARCH("Aub", {Rider}) != "", SEARCH(" Holland", {Rider}) != "")
This matches correctly.
Is there a supported way to include double quotes in a SEARCH on a linked record field?

