# Search-UI RoadMap?

**URL:** <https://discuss.elastic.co/t/search-ui-roadmap/326769>\
**Category:** Elastic Search\
**Tags:** elastic-app-search\
**Created:** [March 1, 2023, 2:05pm UTC](https://discuss.elastic.co/t/search-ui-roadmap/326769 "2023-03-01T14:05:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndrewSharp](https://avatars.discourse-cdn.com/v4/letter/a/f0a364/32.png) [@AndrewSharp](https://discuss.elastic.co/u/AndrewSharp)\
**Post date:** [March 1, 2023, 2:05pm UTC](https://discuss.elastic.co/t/search-ui-roadmap/326769/1 "2023-03-01T14:05:56Z")

</div>

Hi,

I'm trying to integrate the search-UI into our webpage, but there are 2 bugs holding us back and I was wondering if there was an ETA on them or a RoadMap somewhere. The two issues are:

> <https://github.com/elastic/search-ui/issues/888>
>
> \*\*Describe the bug\*\*
> 
> \- Once you add a field to search\_fields object in search…Query, that is of type 'keyword', a server error occurs and nothing is returned (empty object). 
> \- Searching for fields of type 'text' works fine
> \- Note that the autocomplete doesn't exactly have the same issue. The autocomplete gives me the responseState correctly, just with 0 suggestions
> \- Note that I wanted to see if I could get any other type of error by simply removing the index and the same error is thrown. We really need better error handling. 
> 
> 
> 
> \*\*The server error (nextJS serverside) \*\*
> \`\`\`
> error - TypeError: Cannot convert undefined or null to object
> at Function.keys (\<anonymous\>)
> at Object.getFacetsFromResponse (/Users/zakaria/Repos/nedap\_portal/portal/node\_modules/@searchkit/sdk/lib/cjs/core/FacetsFns.js:42:36)
> at ElasticSearchResponseTransformer.transformResponse (/Users/zakaria/Repos/nedap\_portal/portal/node\_modules/@searchkit/sdk/lib/cjs/transformers/index.js:61:27)
> at SearchkitRequest.\<anonymous\> (/Users/zakaria/Repos/nedap\_portal/portal/node\_modules/@searchkit/sdk/lib/cjs/index.js:126:37)
> at Generator.next (\<anonymous\>)
> at fulfilled (/Users/zakaria/Repos/nedap\_portal/portal/node\_modules/@searchkit/sdk/lib/cjs/index.js:15:58)
> at runMicrotasks (\<anonymous\>)
> at processTicksAndRejections (node:internal/process/task\_queues:96:5) {
> page: '/api/search'
> }
> \`\`\`
> \*\*To Reproduce\*\*
> Steps to reproduce the behavior:
> 
> 1. Setup with nextJs like this https://docs.elastic.co/search-ui/guides/nextjs-integration
> 2. put an index in elasticSearch like so:
> 
> 
> \`\`\`
> PUT products
> {
> "mappings": {
> "dynamic":"strict",
> "properties": {
> "itemType": {
> "type": "keyword"
> },
> "productId": {
> "type": "keyword"
> },
> "productTitle": {
> "type": "text"
> }
> }
> }
> }
> 
> \`\`\`
> 
> 3. push data in elasticSearch
> 4. setup the serach-ui config like this:
> 
> \`\`\`
> searchQuery: {
> search\_fields: {
> productId: {},
> },
> \`\`\`
> 
> \*\*Expected behavior\*\*
> 
> either:
> \- A search that still works, even though it will only return exact matches. 
> \- if type 'keyword' is not supported, give me a correct error message in the response
> 
> \*\*Screenshots\*\*
> 
> 
> 
> \*\*Which backends and packages are you using:\*\*
> Backend: \[Elastic Search cloud\]
> 
> Using the next.js setup from the docs: 
> 
> \`\`\`
> "@elastic/react-search-ui": "^1.17.1",
> "@elastic/react-search-ui-views": "^1.17.1",
> "@elastic/search-ui": "^1.17.1",
> "@elastic/search-ui-elasticsearch-connector": "^1.17.1",
> \`\`\`

and to a lesser degree: [Nested objects are not rendered when `elasticsearch-connector` is used · Issue #907 · elastic/search-ui · GitHub](https://github.com/elastic/search-ui/issues/907)

Thanks

---

<div class="post-metadata">

**Author:** ![joemcelroy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joemcelroy/32/103757_2.png) [@joemcelroy](https://discuss.elastic.co/u/joemcelroy)\
**Post date:** [March 1, 2023, 3:23pm UTC](https://discuss.elastic.co/t/search-ui-roadmap/326769/2 "2023-03-01T15:23:05Z")

</div>

hey @AndrewSharp,

The first issue i've added a workaround. The second issue we haven't made any progress on.

We dont have a roadmap but would be good to share when we do.

Joe

---

<div class="post-metadata">

**Author:** ![AndrewSharp](https://avatars.discourse-cdn.com/v4/letter/a/f0a364/32.png) [@AndrewSharp](https://discuss.elastic.co/u/AndrewSharp)\
**Post date:** [March 1, 2023, 3:35pm UTC](https://discuss.elastic.co/t/search-ui-roadmap/326769/3 "2023-03-01T15:35:29Z")

</div>

Thanks for the quick response and workaround! I'll try this out now.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 29, 2023, 3:35pm UTC](https://discuss.elastic.co/t/search-ui-roadmap/326769/4 "2023-03-29T15:35:51Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.