Skip to main content

Data Connection for Search Table not Working in Global Search

Permanently deleted user

Hi All,

I have made a data connection to my SQL database in Geocortex Essentials 3.8 in order to add a search table in my test site. I tested it yesterday and it worked great. But today for no apparent reason when I made the same data connection & created the same search table in my production site the data was not searchable in the global search and returned zero results. What am I missing? Has anyone else had this experience and found a solution?

Stephanie

0

Comments

10 comments

Date Votes
  • Permanently deleted user

    I just got mine working did you configure the search in both the table menu and the layer which you setup the data link for? I found out that I did not do that originally once I did that my searches started working properly.

    0
  • Permanently deleted user

    First I set up the Data Connection which seems to be working, then I configured the search table, which also appears to be working as well, as no errors are being thrown. But when I open my application and search no search results are returned.

     

    Stephanie

    0
  • Permanently deleted user

    Stephanie-

    Did you ever get this to work?

    I've got a similar issue in that I have a functioning Data Link and a function Search Table, but when I try to marry the two and use the global search to find records in the table, I don't get any results.

    Thanks,

    Peter

    0
  • Permanently deleted user

    Peter,

    I never did get it resolved.

    Stephanie

    0
  • Permanently deleted user

    I have the same problem. Someone from Latitude can you suggest anything??

    0
  • Permanently deleted user

    Hi Folks,

    Our first suggestion is to review the feature video that goes through all of the components of searching with Global Search via search tables:

    http://support.geocortex.com/data-link-search

    If everything appears to be configured properly (Search Table is associated with a Data Link on a layer), then use the REST endpoint to test the search table.  The Search table test should return results that contain both the field you were searching for and the field that's used to associate the results with the feature layer.

    Case sensitivity may be an issue - if you don't get the expected results, try typing the search query exactly as the data appears in the source table.  If the query is case sensitive, you can relax it by using the UPPER() or UCASE() function in your data query to make both the parameter and the data field upper case.  You can also use a LIKE query with wildcards (% or *) to search for substrings.

    I haven't verified this yet, but the column types for the link column may have to match.  If the data table's link column is a number but the feature class uses a string - ZIP codes are a classic example of this - then Essentials may not be able to find a match.  I'll check on that to see if it is the case.

    Regards,

    -Malcolm

    0
  • Permanently deleted user

    Thanks for the response Malcolm.

    I have followed all of the steps in the video and my problem is just no records returned. The search in the REST endpoint continually returns 0 results, however it does list the fields correctly which I assume means it is accessing the table successfully. I have tried every combination imaginable of for my string input e.g. wildcards % and *, capitals, proper case, ", ' etc with no results. My query is looking for LIKE. My keys linking the child and parent are also identical fields - both strings, and with the same field name (TITLENAME). I had set up datalinks and added the search tables to them as well before testing in the REST endpoint.

    My parent layer is a feature class in SDE and my child tables are also in the same SDE  database. I have successfully created relationships between these datasets with the attributes appearing by Identify in the silverlight viewer.

    Any further tests or suggestions would be most welcome. The ability to search on child tables is a major restriction in the development of several Geocortex applications in my organisation. Many teams are not interested if they can't interact with their tabular data.

    Jane

    0
  • Permanently deleted user

    Hi Jane

    one suggestion that may or may not help is to make use of the SQL related Activities in Workflow. This would help remove some of the configuration mysteries that you are currently facing.

    It would also give you a chance to allow further refinement of results prior to displaying results on the map.

    Regards

    Ralph Price

    0
  • Permanently deleted user

    Thanks to our embedded consultant from the distributor AAM Australia, my problem is solved.

    The parameter defined for your Search Table MUST have the same name as the parameter defined for your Data Link. Even though my Search Table parameter is searching a differnet field than my Data Link parameter as long as the parameters names are set to be the same I get results returned from the child table. It does not make any sense though!

     

    0
  • David Major

    Does the global search on a data link work in an HTML5 viewer? I have it working in a Silverlight Viewer but not HTML5.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post