Adding relationship - Status - Too many matching results

[petednz]

Hey - because we can't see a better way of handling organisations with lots of branches other than putting the branch after a hyphen in Org Name we have some Orgs that have 50+ Org Names (eg OrgX - A Branch; OrgX - B Branch etc)

When I then try to 'add relationship' from the Individual to the Org'n and put "Org X" or even "Org X - A Branch" in the Find Target Contact field, even when the Field shows me the Org/Branch I want, it tells me

status
    Too many matching results. Please narrow your search by entering a more complete target contact name.

I can set up the Relationship from the Org'n but it is a pain in terms of workflow. Any suggestions or can it be fixed if you consider it a bug. cheers

[Dave Greenberg]

I just verified this on demo as well. The problem is that even though an exact matching contact is selected in the Find Target Contact "comboBox" - clicking "Search" does the wrong thing. It should just return the single matching row in this case.

I've posted a bug fix for this for 2.1:
http://issues.civicrm.org/jira/browse/CRM-3150

I suspect this fix will be back-portable by chris ... so might want to have him watch that issue.

[petednz]

Thanks Dave - I'm watching.

[lcdweb]

In unclosed this issue as it's still showing up in v2.1.1
Comments in Jira.

[Kurund Jalmi]

There seems to be a bug, so i have reopened the issue.

thanx

Kurund

[xavier]

Another related problem is that when you search for "OrgX - branch of ZZZ" it will not only find all the OrgX, but also all the organisations that contains "branch" or "-" or "of".

Basically, as soon as you're trying to search a name of organisation that contains a "stopword" like "a" "of" "association"... you're out of luck and flooded with half of the db.

My quick fix (until we got a proper fulltext search)

Code: [Select]

+++ CRM/Contact/BAO/Query.php   (working copy)
@@ -2126,7 +2126,8 @@
                 $name   = substr( $name, 0, -1 );
                 $pieces = array( $name );
             } else {
-                $pieces =  explode( ' ', $name );
+                $pieces = array( $name );


[FatherShawn]

I just ran into this same error message in 2.1.4.  I don't know if it's the same source, but I'm posting here since I found this thread by searching for the error message.  Here's the situation, which I just verified on the Drupal demo.

Task: Add a child relationship to a record.

In previous versions, if both parents were in the db, I could search for surname, such as Roberts and then check both parent's records in the results, and add both relations at the same time.  In the current version, if I take any other action besides waiting for the widget to display the list of possible matches and searching for that exact record, then I get the error message:

Too many matching results. Please narrow your search by entering a more complete target contact name.

This will occur on the demo whether you use roberts or roberts%.  There are currently 9 matches in the demo database, which should not be too many matching results.  This works properly from the Find Contacts screen but not on the New Relationship screen.

[Kurund Jalmi]

I tried on http://drupal.demo.civicrm.org/civicrm/contact/view/rel?cid=105&action=add&reset=1
with Child of relationship, for roberts, it gave me 6 records.

So seems to be working fine..

Kurund

[xavier]

Hi,

The usability issue (beside the obvious problem when you have too many) is that you first narrow down in the autocomplete to one contact and click on that contact, to go to a second step that lists all (often only the one you just clicked on), that you have to select AGAIN to create the relationship.

If you select one contact in the autocomplete, it should skip the list and directly let you create the relationship.

X+

[Dave Greenberg]

The usability issue (beside the obvious problem when you have too many) is that you first narrow down in the autocomplete to one contact and click on that contact, to go to a second step that lists all (often only the one you just clicked on), that you have to select AGAIN to create the relationship.

If you select one contact in the autocomplete, it should skip the list and directly let you create the relationship.

I agree with this - EXCEPT for the fact that the current autocomplete widget doesn't show any identifying details for the selected contact other than the sort name (last, first). For installs w/ larger databases it is quite likely that there may be multiple individuals with the same last, first names (or organization records w/ the same organization name but in different locations). The search result row shows (hopefully) enough additional info (city, state, phone, email...) to confirm that the user has the contact they want.

We could potentially fix this by displaying that info (read-only) next to the autocomplete type-ahead box as records are selected. Would be interested in others thoughts on this.

[FatherShawn]

I tried on http://drupal.demo.civicrm.org/civicrm/contact/view/rel?cid=105&action=add&reset=1
with Child of relationship, for roberts, it gave me 6 records.

So seems to be working fine..

Kurund

I can narrow this down some.  If you type "roberts" and hit return then you will get the error message.  If you type roberts, wait for the autocomplete widget to display the list, click in a vacant area to make the list go away because it is covering the "Search" button and then click the button, you get the multiple results.

Shouldn't one be able to simply type the name and hit return?

[davej]

Our clients still find Add Relationship very problematic in Civi 3.0.1 - the same issue as reported by PeterD in the original post. One client has over 400 organisations with "Bolton" in their name. When trying to add a relationship from an individual to their employer, let's say Bolton XYZ, typing XYZ in the widget finds 3 matching contacts in the drop-down. Clicking on Bolton XYZ in the drop-down and clicking Search results in:

"Too many matching results. Please narrow your search by entering a more complete target contact name."

However clicking on Salford XYZ in the drop-down, then Search, gives a list of 9 candidate contacts, with names matching Salford or XYZ.

So it appears the reason why clicking Bolton XYZ + Search fails is that a search is then done on Bolton or XYZ, which retrieves over 400 orgs. This is clearly incorrect - having selected a single contact, we have the id and no further search should be carried out and certainly not this search.

As a workaround, typing "Bolton XYZ" (with quotes) in the widget retrieves nothing in the drop-down, but clicking Search then retrieves the single matching contact.

Dave J

[Donald Lobo]

created an issue for this:

http://issues.civicrm.org/jira/browse/CRM-5385

lobo

[ngingras]

This issue seems to still be unresolved as of 3.1.3.

http://issues.civicrm.org/jira/browse/CRM-6033


Same error as before

[Donald Lobo]

can you please ask us to reopen an old issue rather than creating a new issue in the future

i've cleaned up the below multiple issues

lobo