Simplified search setup in Architect

ideas
1

Now when I want to include fields of a custom entity in search I have to create Search Data Source for each of them and that takes a lot of time.

What about do it the following way where each field has properties like for example:

  • VisibleInSearch: true / false (default: false)
  • NameInSearch: lookup
  • DescriptionInSearch: lookup

This or any better solution will determine all fields included in search in a fast and comprehensible way.

3

At the moment the search is not a commonly used function. The usual usage is to search by one field, e. g. reservation code or invoice number. I don’t think there was requirement to search by more fields ever.

The suggested solution means change in meta model and we prefer to search for other solution before touching it.

4

OK, understand, avoid meta model changes. But there is any better solution needed as now it takes absurdly long time to add new fields to search when a new entity is created. Let’s discuss that please.

6

It’s not like that meta model changes are tabu, but it’s better to explore other options before introducing them.

8

My proposed solution would be an action that generates the search data source from an entity field. It should ask for:

  • an existing filter (it can propose one by naming convention, e.g. GetByFieldName)
  • an existing lookup with an existing menu binding (it can propose one by naming convention, e.g. LookupEntity where Entity is the name of the current entity)

If the filter would not exist, it could create the equal filter with a parameter. The lookup has to always be specified by the user as most probably it does not exist so it would have to be modelled first.

Then the action would create:

  • optionally the filter
  • a data structure
  • a filter set
  • a search data source
1 Like
9

That is why we make it easier – so it would be commonly used :slight_smile:

There were requirements for a full-text search for example on multiple fields.