Override search.yml – Search with more parameters

To explain best what I would like to do, it’s actually the same thing that Contact Bundle here is doing but for Account Bundle.

So, whenever we have an autocomplete dropdown of contact bundle (example, when you are creating a case), you can select contact by searching with different properties like namesuffix, lastname, skype etc. I would like to do the same thing for Account bundle. I got the other properties displaying by putting them in services.yml like:

PHP

orocrm_account.form.autocomplete.account.search_handler: parent: oro_form.autocomplete.search_handler arguments: - %orocrm_account.account.entity.class% - ["name", "email", "phone"] tags: - { name: oro_form.autocomplete.search_handler, alias: accounts, acl_resource: orocrm_account_view }

1 2 3 4 5 6 7

orocrm_account.form.autocomplete.account.search_handler:         parent: oro_form.autocomplete.search_handler         arguments:             - %orocrm_account.account.entity.class%             - ["name", "email", "phone"]         tags:             - { name: oro_form.autocomplete.search_handler, alias: accounts, acl_resource: orocrm_account_view }

And then in my search.yml I have this:

PHP

Custom\Bundle\AccountBundle\Entity\Account: alias: orocrm_account label: orocrm.account.entity_plural_label title_fields: [name, email, phone] route: name: orocrm_account_view parameters: id: id search_template: CustomAccountBundle:Account:searchResult.html.twig fields: - name: name target_type: text target_fields: [name] - name: email target_type: text target_fields: [email] - name: phone target_type: text target_fields: [phone] - name: defaultContact relation_type: one-to-one relation_fields: - name: emails relation_type: one-to-many relation_fields: - name: email target_type: text target_fields: [email]

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

Custom\Bundle\AccountBundle\Entity\Account:     alias: orocrm_account     label: orocrm.account.entity_plural_label     title_fields: [name, email, phone]     route:         name: orocrm_account_view         parameters:             id: id     search_template: CustomAccountBundle:Account:searchResult.html.twig     fields:         -             name: name             target_type: text             target_fields: [name]         -             name: email             target_type: text             target_fields: [email]         -             name: phone             target_type: text             target_fields: [phone]         -             name: defaultContact             relation_type: one-to-one             relation_fields:                 -                     name: emails                     relation_type: one-to-many                     relation_fields:                         -                             name: email                             target_type: text                             target_fields: [email]

But in my account autocomplete dropdown, I cannot search for an account using their email or phone although they appear in the list. Is my search.yml not being recognized? Do I need to load it somewhere explicitly rather than just overriding?

Topic

[oro_newbieParticipant]

Bump. I hope somebody’s read this and can help.

[Mike KudelyaParticipant]

Hi,

By default, an account doesn’t contain email and phone fields, but if you created them in your custom entity, just run this command to reindex search.

Shell

app/console oro:search:reindex

1	app/console oro:search:reindex

[oro_newbieParticipant]

Thank you Mike.

I ran that command and added extra parameter OroCRMAccountBundle:Account and I see that the table ‘oro_search_item’ is getting updated with all my account records. Right now it’s creating individual record for names but later I think it will create for email and phone. Is that what’s supposed to happen? My allowed memory size has currently exhausted while running the command. Do I need to give a timeout option? (–timeout=0 does not work)

[oro_newbieParticipant]

I realized what I was missing. Even though I had ‘Custom\Bundle\AccountBundle\Entity\Account:’ declared in my search.yml, the actual Entity\Account file did not exist. So I override it and ran the command:

PHP

php app/console oro:search:reindex CustomBundleAccount:Account

1	php app/console oro:search:reindex CustomBundleAccount:Account

and with this the fields from my search.yml started indexing in tables oro_search_item & oro_search_index_text. I guess that’s one good way to check if your search indexed the right fields.

Though I still get the “Allowed memory size exhausted of … bytes exhausted” error. I guess the only workaround for now is to run the command with offset and limit parameters like:

PHP

php app/console oro:search:reindex CustomBundleAccount:Account 1 20000

1	php app/console oro:search:reindex CustomBundleAccount:Account 1 20000

which means start from record ID 1 and get 20000 rows and then next

PHP

php app/console oro:search:reindex CustomBundleAccount:Account 20000 20000

1	php app/console oro:search:reindex CustomBundleAccount:Account 20000 20000

start from record ID 20000 and get 20000 rows etc.

Can probably be useful for someone in future.

[Mike KudelyaParticipant]

Try to increase ‘memory_limit’ php directive

[oro_newbieParticipant]

Thank you Mike. Will try that the next time I’m running the command.

[Author]

Replies