Skip to main content

Filtering List Fields with Has Entry

Match one exact item inside a comma-separated field, without the false matches Contains gives you.

Written by Dan Sugarman

Has Entry finds SKUs where a field holds your value as one whole item in a comma-separated list. Use it on fields that hold a list, such as a set of colors or a set of error codes.

Has Entry vs Contains

Contains matches your text anywhere in the field, so it also returns SKUs where your text is only part of a longer word. Has Entry matches a whole list item and nothing else.

Say two SKUs have these Colors:

  • SKU Aredwood

  • SKU Bred, blue

Filtering Colors with Contains red returns both SKUs. Filtering with Has Entry red returns only SKU B.

What Counts as a Match

  • Capitals are ignored. Has Entry Red matches red, blue.

  • Spaces around the commas are ignored. Has Entry blue matches red , blue.

  • The whole item has to match. Has Entry forest does not match forest green.

  • An empty field never matches.

  • Leaving the value box empty returns no rows. It does not return everything.

When Not to Use It

Has Entry is for fields that hold a list. On a free-text field it can surprise you, because Zentail splits on every comma it finds.

A Title of Red, White and Blue Shirt is read as two items: Red and White and Blue Shirt. Has Entry Red matches that SKU, and Has Entry White does not. On Title, Description and other prose fields, use Contains instead.

Did this answer your question?