Global Search in Custom Field?

[ChrisL]

As "normal" we have defined some custom fields in Customer and other entities that have been setup.

Now, in the "Global search field" on the top, you can only look for some pre-defined fields - and yes, you can add some additional one's via the admin panel, but unfortunately not the manual added fields...

in our case for e.g., all contacts are having a "old" customer-number, which is a number field. To actually search for them, we have always to select "add field", select the field, change to "contains/is" and then enter the number, this way we got it.
Obviously it would be way more relaxed, if we can just enter the number in the global search field...

I've found some solution with updating some php files/codes, but it looks like this is not for the actual version (couldn't find the described code that has to be changed in the specific files).



Can someone help in this point, that I have to change, that we can browser for custom fields?

thx

[tanya]

Hello
is it principle to leave "old" customer-number as a number? Number field is calculated, if we talk about old field, it has to be copied from somewhere.
For global search are available fields with type text or varchar. You could change the field type to varchar (custom/Espo/Custom/Resources/metadata/entityDefs/{your_entity}.json)

[ChrisL]

at the moment the field is a "Ganzzahl" - so english I think it should be "integer" - so it is not possible to search for the number containing in this field?

we've also made some new customer IDs, Vehicle IDs etc. which are "Automatisch hochzählen" - so "count up automatically"

obviously, it would make our life way easier, if we can look in the global search for these numbers... because quite often, when a customer is calling, he is telling us his customer number... (actually still the old one, in the future the new one)...

[tanya]

For global search are available only varchar and text field. If you met with MySQL, you know, that a searching for different types works in different way. To search by part of the word uses LIKE function, it is not available for integer type. For global search builds a complex query, so it will take much more time if we separate this process by few others with field type checking.

If you really need to leave field as integer, you could also create a new varchar readonly field. Possibly you need to run sql query once to copy old data. And set in formula the value from your integer field. And then you could add this field to global search.

[olamborelle]

If you really need to leave field as integer, you could also create a new varchar readonly field. Possibly you need to run sql query once to copy old data. And set in formula the value from your integer field. And then you could add this field to global search.

Would a similar solution work if we have a custom field of type multi-enum? We would like the search to look through these without having to add a specific filter.