# Not analyzed attribute in nest 7.17

**URL:** <https://discuss.elastic.co/t/not-analyzed-attribute-in-nest-7-17/328600>\
**Category:** Elasticsearch\
**Tags:** language-clients\
**Created:** [March 27, 2023, 10:05am UTC](https://discuss.elastic.co/t/not-analyzed-attribute-in-nest-7-17/328600 "2023-03-27T10:05:58Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [March 27, 2023, 1:23pm UTC](https://discuss.elastic.co/t/not-analyzed-attribute-in-nest-7-17/328600/4 "2023-03-27T13:23:13Z")

</div>

Hi @reza_setareh,

Which version of the client where you using before? By `not_analyzed` are you referring to the old strong `analyzed` and `not_analyzed` behaviour as referenced in this [old topic](https://discuss.elastic.co/t/index-not-analyzed/126606) and [blog post](https://www.elastic.co/blog/strings-are-dead-long-live-strings)?

If so I think you're looking to make use of the `keyword` type that replaced `not_analyzed`. If you're using the [automapping feature of the client](https://www.elastic.co/guide/en/elasticsearch/client/net-api/7.17/auto-map.html#auto-map) it should infer the type to give text with a keyword subfield for String, or keyword for a couple of other types as per the [documentation](https://www.elastic.co/guide/en/elasticsearch/client/net-api/7.17/auto-map.html#inferred-dotnet-type-mapping). Or alternatively you can map manually [similar to the example in the documentation](https://www.elastic.co/guide/en/elasticsearch/client/net-api/7.17/fluent-mapping.html#_manual_mapping).

Do let me know if that is what you're not trying to do. Hope that helps!

---

_[View the full topic](https://discuss.elastic.co/t/not-analyzed-attribute-in-nest-7-17/328600)._