searching using 'LIKE' with no case sensitive using Query Task
Hi All,
I am stumble on these 3 issues, that I would like to make it work:
1. How can search using 'LIKE' with no case sensitive for input value, user can entered input either in lowercase/uppercase. The layer's field (Department) has value such as "Mental Health" or "Health & Mental Health". If I build QUERY WHERE CLAUSE expecting input textbox value is "mental', then:
a. "Department like '%" + department.ToUpper.Substring(0,1) + department.length - 1+ '%" ---- this work fine if my input is 'mental' and only 1 word allow.
b. I am thinking converting layer's field value to UpperCase, and my input to uppercase then user can enter more than one word such 'mental health', but how can I build QUERY WHERE CLAUSE.
2. I created workflow using "Display Form' with one textbox and Search button, I would like "Display Form" displays in "DataRegion" but it is display as a popup modal. I know it has to do with REGION="DATAREGION", but don't know where is that section or need to insert the codes.
3. The results display on the 'Result Panel' (left section), the InfoBox is popup when selected data; but the "Detail' tab show nothing eventhough I configured to use "Feature Long Description", however the 'Detail' tab displays data when using "Identify Tool"
Any help would be appreciated.
-
Hi Kim,
1) you want to use SQL's UPPER function and convert both the attribute from the layer and the search value to uppercase so that you're comparing apples to apples. So your where clause would look like this :
UPPER (Department) like UPPER('%" + department +"%')"
This change will avoid having to convert attributes in your MXD.
2) Insert a "ConfigureWorkflowContainer" activity at the start of the workflow and set the "Workflow Container Name". Insert this name into the property into the DisplayForm activity. The region name property has become obsolete. See the "Search for Schools" example in the code gallery - http://support.geocortex.com/find-parcels-near-schools-workflow-from-html5-viewer-webinar
3) You want to set the "Feature Description" and not the long description for the results pane.
regards,
Edmond
Latitude Support
0 -
Thank you very much Edmond, I have implemented your solution and it's work for steps 1 & 2.
Step 3) Yes, I need to set "Feature Description" in order to display details information on the results panel and only work if I used "Tool Identify" and selected the dot on the map, but didn't work on the results from workflow in step #1. The results panel displays the results from the workflow (without the information that I have set in "Feature Description"), when mouse over the data on the results panel, the "InfoBox" displays; however, the "Details' tab shows "None Available" and the "Attributes" tab shows all the attributes value from the layer. It's seem the results from workflow is not displayed the same information as I configure "Site" map. Do I have to write codes to handle the results from the workflow?
Thanks,
0 -
Hi Kim
just a quick thought. What fields are you returning from any queries that occur in your workflow?
Regards
Ralph Price
0 -
Hi Kim,
Usually if the feature description and feature long description aren't showing up in the results when the features are selected using workflow, it means that the Select Features activity in your workflow is referencing the wrong map service and/or layer. Make sure that you are going to the Rest Endpoint for your Geocortex Site (found on the Site Info page in Rest Manager), choose Map, and check that you are using the map service id and layer id found in brackets beside the correct map service and layer..
*Note that the attributes still show up correctly even if you aren't selecting the correct map service or layer ids because you are supplying these attributes in the feature set that was returned from your query.
-Victoria
0 -
I'm having a similar issue as Kim, but i'm positive my map IDs and layer IDs are correct.
I'm getting the map ID from the REST site, and the layer ID from the geocortex site?0 -
Victoria, I took your suggestion and it works now. Details tab is display 'feature long description' and Attributes tab is display the 'Display Name' for the features return from workflow.
Thank you very much.
Kim
0 -
Hi Victoria,
I'm still having issues with this, is there another possible solution?
Thanks.0 -
Is there a way to convert the input string in an AutoComplete Box? For example, my user enters 'n' but the autocomplete does not return anything because my data is all upper case ('NIKE' 'NEIMAN MARCUS')
0 -
Please use the technique detailed above to convert both your user input and database values to uppercase within the autocomplete WHERE clause. It should look something like this:
UPPER (QueryField) like UPPER('%{0}%')
This will have the effect of creating a case insensitive autocomplete box.
0 -
Thank you Jonathan.
We discovered this issue when switching from using an ArcGIS Rest Services that hit an SDE database to using a REST Service using a file geodatabase in a workflow (but same data).
With the SDE database, you didn't have to use UPPER with the Like statement (try it on the REST service you will see). For example ST_LABEL Like 'mai%' would return anything starting with mai whether or not the data in the table is upper or lower case.
But, if the file geodatabase is all uppercase, the above query will not return anything.
By the way - all the query tasks had to be adjusted also as they wouldn't work the same! crazy!
Carmen
0
Please sign in to leave a comment.
Comments
10 comments