# GraphQL API: Filter by entity description field?

**URL:** <https://community.fibery.io/t/graphql-api-filter-by-entity-description-field/5072>\
**Category:** API & Programming\
**Created:** [September 4, 2023, 2:13pm UTC](https://community.fibery.io/t/graphql-api-filter-by-entity-description-field/5072 "2023-09-04T14:13:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dimitri\_S](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/dimitri_s/32/1683_2.png) [@Dimitri\_S](https://community.fibery.io/u/Dimitri_S)\
**Post date:** [September 4, 2023, 2:13pm UTC](https://community.fibery.io/t/graphql-api-filter-by-entity-description-field/5072/1 "2023-09-04T14:13:39Z")

</div>

I’m struggling to filter entities based on the ‘description’ field with the GraphQL API. The ‘description’ is not appearing as a selectable field in the GraphQL API explorer, but it does auto-complete, which is confusing.

In my example “Cat Tracker” test database, I get the description text when I select the description and specify markdown format (via `description {md}`), but I can’t filter on ‘description’ or getting an `Unknown argument "description" on field "Query.findCatTrackers"` error.

Even simpler, is it possible to filter entities based on the presence (or absence) of a description?

Here is an example query that I tried:

```auto
query {  
  findCatTrackers (description: {md: {isNot: ""}}) {
    publicId
    name
    description {
      md
    }
  }
}

```

Here is a video showing what I am trying to do:

---

<div class="post-metadata">

**Author:** ![Oleg](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oleg/32/1887_2.png) [@Oleg](https://community.fibery.io/u/Oleg)\
**Post date:** [September 5, 2023, 7:10am UTC](https://community.fibery.io/t/graphql-api-filter-by-entity-description-field/5072/2 "2023-09-05T07:10:29Z")

</div>

Hi, @Dimitri_S

Thanks for feedback. Indeed the rich text field is not available as search criterion for now. Can’t say when it will be possible. As workaround the automations which set an additional primitive entity fields can be used as workaround. Sorry for inconvenience.