An issue I found in vFire 9.2 is that Person Search fields don’t work if you use “SURNAME, FIRST_NAME" or "FIRST_NAME SURNAME" and then click Search. You have to instead populate the QD field with a single entity.
Short version: You can resolve this (v9.2.0) by:
1. Backing up your existing search-sql-common.xsl
2. Replacing it with the attached search-sql-common.xsl
3. Recycling your IIS Pool.
Long version:
Scenario: Say you have the following Customers:
Smith, John;
Smith, Jane; and
Smith, Jackson
In the Call Search if you type "Smith, J" as the Customer, then click the Search button, you will see no results. In VSM & Infra, the search would have returned Calls for the above Customers.
Root cause: In search-sql-common.xsl, the SURNAME and FIRST_NAME Parameters that include a % wildcard have their parameter end tag on an indented new line, which in turn passes the trailing whitespace to the where clause of the query (e.g. "Smith, J" becomes FIRST_NAME LIKE 'J%' AND SURNAME LIKE 'Smith% '. This won't return any results due to the trailing whitespace.
Resolution: In search-sql-common.xsl, if you find all the occurrences of SURNAME and FIRST_NAME that are followed by a % wildcard, make sure the closing parameter tag immediately follows the % (on the same line, with no spaces between the % and the closing tag).
I've attached search-sql-common.xsl for 9.2.0.
Hope that helps someone
Cheers,
Al.