# Search Field in the UI has a maximum

**URL:** <https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791>\
**Category:** Report a Bug\
**Created:** [September 11, 2025, 11:47am UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791 "2025-09-11T11:47:50Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@Daniel](https://community.datagerry.com/u/Daniel)\
**Post date:** [September 11, 2025, 11:47am UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791/1 "2025-09-11T11:47:50Z")

</div>

Hello Datagerry Team,

I’m experiencing an issue in the Datagerry UI when searching within an object list. It seems that names containing multiple dots cannot be filtered properly.

For example, searching for `test.asset.test` results in a **400 HTTP Error Code** stating that the request line is too large. In the backend, the system appears to search for `test\\.asset\\.test`  
And the same is for (-)hyphens

Since I have many assets with names in this format, being able to search for them correctly is essential for our workflow. Could you please advise if this behavior is intended or if there is a fix/workaround?

Thank you for your support.

Best regards,  
Daniel

---

<div class="post-metadata">

**Author:** ![abdullah-khalid](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/abdullah-khalid/32/860_2.png) [@abdullah-khalid](https://community.datagerry.com/u/abdullah-khalid)\
**Post date:** [September 11, 2025, 12:35pm UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791/2 "2025-09-11T12:35:00Z")

</div>

Hi @Daniel,

Thanks for your input 🙂

As you can see in the screenshot, it’s working fine on my end. Could you give me the steps you took leading up to the issue so I can try to regenerate it on my side?

 ![Screenshot 2025-09-11 at 14.31.53](https://europe1.discourse-cdn.com/flex013/uploads/datagerry/original/1X/d05618bdd8c264c090c05f93365b26b7f5fd69c2.png)

We truly appreciate your input and ongoing support!

**Sincerely,**

Your DataGerry Team

---

<div class="post-metadata">

**Author:** ![Daniel](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@Daniel](https://community.datagerry.com/u/Daniel)\
**Post date:** [September 11, 2025, 12:42pm UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791/3 "2025-09-11T12:42:57Z")

</div>

Hey @abdullah-khalid  
can you try adding another .test after your so you searching for test.asset.test.test

Then it crashes on my System with Error 400

---

<div class="post-metadata">

**Author:** ![abdullah-khalid](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/abdullah-khalid/32/860_2.png) [@abdullah-khalid](https://community.datagerry.com/u/abdullah-khalid)\
**Post date:** [September 11, 2025, 12:56pm UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791/4 "2025-09-11T12:56:26Z")

</div>

Hi @Daniel,

I just tested using both a hyphen _and_ a dot (in two separate screenshots), and both are working fine for me. 🤔 It’s strange it doesn’t work on your side.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/datagerry/original/1X/4abfe749a4facd76b982bfd90f2b7f569b2063aa.png)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/datagerry/original/1X/c5256594c89eb8e08aca00f6b4bd27f134b3ee9a.png)

**Sincerely,**

Your DataGerry Team

---

<div class="post-metadata">

**Author:** ![Daniel](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@Daniel](https://community.datagerry.com/u/Daniel)\
**Post date:** [September 11, 2025, 1:14pm UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791/5 "2025-09-11T13:14:03Z")

</div>

You are right, i created a blank type with not so many fields inside it and it also works for me.

Seems like i have to many fields. Have a look on my request i get a http 400 error:

GET [http://localhost:4000/rest/objects/?filter=[{“$lookup”:{“from”:“framework.objects”,“localField”:“fields.value”,“foreignField”:“public\_id”,“as”:“data”}},{“$project”:{“\_id”:1,“public\_id”:1,“type\_id”:1,“active”:1,“author\_id”:1,“creation\_time”:1,“last\_edit\_time”:1,“fields”:1,“simple”:{“$reduce”:{“input”:“$data.fields”,“initialValue”:[],“in”:{“$setUnion”:[“$$value”,“$$this”]}](http://localhost:4000/rest/objects/?filter=%5B%7B%22$lookup%22:%7B%22from%22:%22framework.objects%22,%22localField%22:%22fields.value%22,%22foreignField%22:%22public_id%22,%22as%22:%22data%22%7D%7D,%7B%22$project%22:%7B%22_id%22:1,%22public_id%22:1,%22type_id%22:1,%22active%22:1,%22author_id%22:1,%22creation_time%22:1,%22last_edit_time%22:1,%22fields%22:1,%22simple%22:%7B%22$reduce%22:%7B%22input%22:%22$data.fields%22,%22initialValue%22:%5B%5D,%22in%22:%7B%22$setUnion%22:%5B%22$$value%22,%22$$this%22%5D%7D)}}}},{“$group”:{“\_id”:“$\_id”,“public\_id”:{“$first”:“$public\_id”},“type\_id”:{“$first”:“$type\_id”},“active”:{“$first”:“$active”},“author\_id”:{“$first”:“$author\_id”},“creation\_time”:{“$first”:“$creation\_time”},“last\_edit\_time”:{“$first”:“$last\_edit\_time”},“fields”:{“$first”:“$fields”},“simple”:{“$first”:“$simple”}}},{“$project”:{“\_id”:“$\_id”,“public\_id”:1,“type\_id”:1,“active”:1,“author\_id”:1,“creation\_time”:1,“last\_edit\_time”:1,“fields”:1,“references”:{“$setUnion”:[“$fields”,“$simple”]}}},{“$addFields”:{“public\_id”:{“$toString”:“$public\_id”}}},{“$addFields”:{“creationString”:{“$dateToString”:{“format”:“%Y-%m-%dT%H:%M:%S.%LZ”,“date”:“$creation\_time”}}}},{“$addFields”:{“editString”:{“$dateToString”:{“format”:“%Y-%m-%dT%H:%M:%S.%LZ”,“date”:“$last\_edit\_time”}}}},{“$match”:{“type\_id”:1}},{“$match”:{“$or”:[{“public\_id”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.hostname”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.lifecycle”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.dns-external”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.crown-jewel”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.asset-type”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.asset-criticality”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.profile-name-id”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.pear-device-id”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.pear-hostname”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.os-version”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.mac-address”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.host-groups”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.ref-company”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.ref-location”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“fields.ref-division”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}},{“public\_id”:{“$elemMatch”:{“value”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ismx”}}}},{“references”:{“$elemMatch”:{“value”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ism”}}}},{“creationString”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ims”}},{“editString”:{“$regex”:“test\\-test\\.test\\.test\\.asset”,“$options”:“ims”}}]}}]&limit=25&sort=public\_id&order=-1&page=1&view=render&onlyActiveObjCookie=true

---

<div class="post-metadata">

**Author:** ![Daniel](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@Daniel](https://community.datagerry.com/u/Daniel)\
**Post date:** [September 11, 2025, 1:17pm UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791/6 "2025-09-11T13:17:38Z")

</div>

It appears that HTTP requests have a maximum limit of 2048 characters. My current request exceeds this, with over 3000 characters. Would it be possible to adjust or refactor the search functionality to accommodate longer requests without overflowing?

---

<div class="post-metadata">

**Author:** ![abdullah-khalid](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/abdullah-khalid/32/860_2.png) [@abdullah-khalid](https://community.datagerry.com/u/abdullah-khalid)\
**Post date:** [September 11, 2025, 1:47pm UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791/7 "2025-09-11T13:47:56Z")

</div>

Thanks for sharing. I’ll need to dig deeper into this from my side to debug properly. I’ll get back to you once I’ve done so.

**Sincerely,**

Your DataGerry Team

---

<div class="post-metadata">

**Author:** ![Daniel](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@Daniel](https://community.datagerry.com/u/Daniel)\
**Post date:** [November 25, 2025, 9:45am UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791/8 "2025-11-25T09:45:41Z")

</div>

Hey @abdullah-khalid  
do you have any new Information about this topic? Or any new upcomming releases?

Kind Regards  
Daniel

---

<div class="post-metadata">

**Author:** ![abdullah-khalid](https://dub1.discourse-cdn.com/flex013/user_avatar/community.datagerry.com/abdullah-khalid/32/860_2.png) [@abdullah-khalid](https://community.datagerry.com/u/abdullah-khalid)\
**Post date:** [December 1, 2025, 12:53pm UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791/9 "2025-12-01T12:53:58Z")

</div>

Hi,

Thanks for the follow-up. We’ve already added this issue to our backlog. I’ll update you here as soon as we have news or a fix ready. Thanks for your patience!

Sincerely,

Your DataGerry Team

---

<div class="post-metadata">

**Author:** ![Daniel](https://avatars.discourse-cdn.com/v4/letter/d/3ec8ea/32.png) [@Daniel](https://community.datagerry.com/u/Daniel)\
**Post date:** [August 31, 2026, 7:12am UTC](https://community.datagerry.com/t/search-field-in-the-ui-has-a-maximum/791/10 "2026-08-31T07:12:41Z")

</div>

Hello Support,

do you have any new Update on this Topic. I don’t see a change in the latest Version 3.1

Kind Regards  
Daniel
