Search Field in the UI has a maximum

[Daniel]

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

[abdullah-khalid]

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?

We truly appreciate your input and ongoing support!

Sincerely,

Your DataGerry Team

[Daniel]

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

[abdullah-khalid]

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.

Sincerely,

Your DataGerry Team

[Daniel]

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”]}}}}},{“$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

[Daniel]

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?

[abdullah-khalid]

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