Search is not working with large number of fields in object

[amos]

Hello,

I’m using on-prem DataGerry 3.0.0

I have around 40 fields in my object. When trying to search an object the UI hangs and realized that there is an error when calling the API

Are you familiar with this ? should be any limitation for the number of fields in object ? maybe you should perform the filter in POST instead of GET…

Will it be fixed in the upcoming release (Q1, 2026) ?

[adnan.smajic]

Hi @amos ,

thanks for the feedback. We will have a look at this issue and will let you know about any updates here. This issue will be added to our bugreports.

Sincerly,

Your DataGerry-Team

[Daniel]

Hey @adnan.smajic
I wanted to clarify your message that says “will be added to our bugreports”. I already opened a thread about this back in September and received an update that your team was working on it. I just want to ask if it’s still on your bug tracker and hasn’t been overlooked, so we don’t end up with a duplicate report

Search Field in the UI has a maximum

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 e…

[adnan.smajic]

Hi @Daniel ,

yeah it was so to say merged into it. We already have internal Plans to refactor and optimize Search queries in DataGerry and the issue you reported will be part of this refactoring. But due to other higher priority tasks we do not have a concrete date yet when the implementation will happen.

Sincerly,

Your DataGerry-Team