# Bug with displaying a NULL value in dense\_vector field in elasticsearch web UI

**URL:** <https://discuss.elastic.co/t/bug-with-displaying-a-null-value-in-dense-vector-field-in-elasticsearch-web-ui/374593>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring, vector-search\
**Created:** [February 16, 2025, 2:20am UTC](https://discuss.elastic.co/t/bug-with-displaying-a-null-value-in-dense-vector-field-in-elasticsearch-web-ui/374593 "2025-02-16T02:20:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gennadii](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gennadii/32/119721_2.png) [@gennadii](https://discuss.elastic.co/u/gennadii)\
**Post date:** [February 16, 2025, 2:20am UTC](https://discuss.elastic.co/t/bug-with-displaying-a-null-value-in-dense-vector-field-in-elasticsearch-web-ui/374593/1 "2025-02-16T02:20:21Z")

</div>

Hello!

I noticed something that looks like a bug in elasticsearch web UI.

When creating a document with dense\_vector field set to null, I cannot expand the document details at elasticsearch web UI documents page (vector field is not shown in a collapsed view of the document in my case). When trying to expand, the page turns blank and I receive an error log in the browser console:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/7/271aabb23be61689c111aabadd2287e11ccf7271.png)

I tried excluding the vector field instead of giving it a NULL value and the problem disappeared.

Steps to reproduce:

1. Create a new elasticsearch index with dense\_vector field in the mapping.
2. Save a document with dense\_vector field with a NULL value.
3. Go to the `<deployment>/app/enterprise_search/content/search_indices/<your_index>/documents` and try to expand the document:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/c/2c21958c1bf60c380f33ccb8e53464125c916e87.png)

P.S.: I haven't checked how it works if the vector field is shown in a collapsed view, in my case it is trimmed and I have to expand the document, but I assume the problem is there for both variants.

Thank you!