topic Re: Problem using multiple expressions in eSearch 3.1 in ArcGIS Viewer for Flex Questions

Problem using multiple expressions in eSearch 3.1

JustinFultz — Mon, 28 Jan 2013 14:09:19 GMT

I am trying to upgrade my flex application to 3.1 and am having problems with the eSearch widget. I have a multiple expression search that worked fine at 2.5. When I upgraded to 3.1 and the newest eSearch widget the multiple expression automatically runs when I fill in the first value and I never have the oppurtunity to select the second value. I have tried all different combinations of isvaluerequired, all with the same result. Below is the config for this particular expression. Any help would be appreciated.

<expression alias="Tie Lines" textsearchlabel="Select TO's to display tie lines..." isvaluerequired="true">      <values>       <value prompt="Select Area..." isvaluerequired="true" userlist="AECI,AEPW,AMMO,CLEC,EES,EMDE,GMO,GRDA,INDN,KACY,KCPL,LAFA,LAGN,LEPA,LES,MEC,MIDW,NPPD,OKGE,OMPA,OPPD,SPRM,SPS,SUNC,SWPA,WAPA,WERE,WFEC"> UPPER(SDE.SPP_TIE_LINES.TIE_NAM) LIKE UPPER('%[value]%')</value>       <value prompt="Select Area..." isvaluerequired="true" userlist="AECI,AEPW,AMMO,CLEC,EES,EMDE,GMO,GRDA,INDN,KACY,KCPL,LAFA,LAGN,LEPA,LES,MEC,MIDW,NPPD,OKGE,OMPA,OPPD,SPRM,SPS,SUNC,SWPA,WAPA,WERE,WFEC" operator="AND"> UPPER(SDE.SPP_TIE_LINES.TIE_NAM) LIKE UPPER('%[value]%')</value>      </values>      </expression>

Re: Problem using multiple expressions in eSearch 3.1

RhettZufelt — Mon, 28 Jan 2013 19:23:08 GMT

Justin,

Could you clarify a little? What do you mean by not having the opportunity to fill in the second value? Are you saying that as soon as you "click" in the second box it is executing the search?

Of course, in your example the "AND" expression is the same thing as the first one so it is redundant. basically, the way I read it is says if a=b AND a=b, then..... Possibly doing an AND on the same criteria is confusing it?

R_

Re: Problem using multiple expressions in eSearch 3.1

RobertScheitlin__GISP — Mon, 28 Jan 2013 19:47:09 GMT

Justin,

Just to add to what Rhett has already said. You also do not need to use a like SQL expression (actually better not to) if you are using a userlist.
Your SQL should be:

SDE.SPP_TIE_LINES.TIE_NAM = '[value]'

Re: Problem using multiple expressions in eSearch 3.1

JustinFultz — Tue, 29 Jan 2013 12:53:33 GMT

So let me explain a the situation a little better and maybe you can provide alternates for performing this operation.

First, the query is performed as soon as I select a value in the first dropdown list. I never have the oppurtunity to have any interaction with the tool or keyboard after that.

The reason the queries are the same and use "LIKE" is because the field is a concatenated field from the owner fields. In the table there is OWNER_1, OWNER_2, and TIE_NAM which is the concatenation of the two owner fields. TIE_NAM could have a value of AEPOGE or OGEAEP, either of which is a tie line between AEP and OGE. The only way to pull either combination is using "LIKE".

Also, I now tested by performing a similar operation using different expressions with an = sign and still get the same behavior so I don't think it is necessarily related to the way the expressions are designed. However, I am open to any suggestions.

Thanks for your help!!!

Additional infromation from further testing:

This only occurs when using a dropdown selection, regardless of if I define the values or if it uses unique values from a field. Immediately after selecting a value in either dropdown, the query runs. The tool functions properly when user is forced to enter values.

Re: Problem using multiple expressions in eSearch 3.1

AnthonyGiles — Tue, 29 Jan 2013 15:26:51 GMT

Robert,

I am having the same issue. Basically if you have more than one field set up to search against using drop down lists as soon as you change the value in one list the query executes. You then have to go back to the text search window to select a value in the second list, and so on if you have many fields.

The desired effect that is required is that if there are multiple drop downs is that the query doesn't execute until you click the search button.

I have looked at your sample site and you do not have any queries set up this way, so you may not have noticed the issue.

Hope that makes sense

Regards

Anthony

Re: Problem using multiple expressions in eSearch 3.1

RobertScheitlin__GISP — Wed, 30 Jan 2013 15:53:10 GMT

Guys,

Thanks for reporting. As I have begun to use GitHub more (and esri has too), it would help me if you log issues/bugs there in the future for the eSearch Widget. https://github.com/rscheitlin/eSearch

This issue will be addressed in Version 3.1.7

Re: Problem using multiple expressions in eSearch 3.1

RhettZufelt — Wed, 30 Jan 2013 16:05:51 GMT

Robert,

I have no problem using GitHub (in fact I just did ), but won't that make it difficult for us to give you your check marks for answering?

R_

Re: Problem using multiple expressions in eSearch 3.1

RobertScheitlin__GISP — Wed, 30 Jan 2013 16:29:48 GMT

Rhett,

You are correct it may eliminate some MVP points I would have gotten, but it will definitely help me to track issues better. So may be people can do both.

Re: Problem using multiple expressions in eSearch 3.1

RobertScheitlin__GISP — Wed, 30 Jan 2013 17:34:23 GMT

Guys,

Version 3.1.7 - 1/30/2013
* Fixed issue with required fields and dropdownlist executing search before all required fields are completed.
* Re-use a map layer token from the identify manager if the same layer is configured for a search.
* Honor gridfield and gridhyperlinkfield order set in the eSearchWidget.xml (add in order specified).

Re: Problem using multiple expressions in eSearch 3.1

JustinFultz — Thu, 31 Jan 2013 19:16:31 GMT

Thanks Robert! Seems to work perfect now.

Re: Problem using multiple expressions in eSearch 3.1

AnthonyGiles — Fri, 01 Feb 2013 14:41:38 GMT

Robert,

The fix you supplied works if you have more than one field set as required, but the problem still exists if the fields are not set to be required. In my case all fields are optional as I want the user to be able to search on what fields they would like to search on (this may be a single field or a combination). But the query still fires on change of a field if they are all set to not required.

What I have done is disabled the automatic query on change of drop down value, but in cases where there is only one field the automatic search would be good. So what I think the solution needs to be is either check if more than one drop down is set up for the search and then disable the automatic search or have a setting to each layer in the config that allows you to specify automatic search true or false.

Regards

Anthony

Re: Problem using multiple expressions in eSearch 3.1

RobertScheitlin__GISP — Fri, 01 Feb 2013 14:57:02 GMT

Anthony,

I hear what you are saying and did consider that route, but decided that if a textbox or dropdown is Not required and all required fields have a value then the search will be executed when the user selects a value in the dropdown. It is hard to make this work for everyone's desires and situation as you want it one way and someone else is asking for something else. I do like the idea of a flag for autoexecuteonselection for all dropdowns. I will consider that approach in the next version if you think that will work.

Re: Problem using multiple expressions in eSearch 3.1

AnthonyGiles — Fri, 01 Feb 2013 15:04:45 GMT

Robert,

Not sure if you would need a flag for autoexecuteonselection on each drop down or just one set for the whole expression. Either way would work but the later maybe easier to implement.

Look forward to your solution if it makes the enhancement cut.

Many thanks again for all your effort,

Regards

Anthony

Re: Problem using multiple expressions in eSearch 3.1

RobertScheitlin__GISP — Fri, 01 Feb 2013 15:31:22 GMT

Anthony and Others,

There is code in the widget that follows this workflow:

Every expression value in the eSarchWidget.xml gets either a textbox or a dropdownlist created in the widgets GUI

If it is a textbox an event is added to it looking for the enter key to be pressed and then fires the AutoSubmitSearch

The AutoSubmitSearch fires off and a check is done to see if there is only one entry item (i.e. one textbox or one dropdownlist) and if true then the search is automatically submitted.

If there is more than one field in the GUI then it checks if the search button is enabled and if it is then the search is automatically submitted.

Now the search button is disabled if all required fields do not have a valid value.

If the expression requires a dropdownbox then it is give a change event listener and it fires the AutoSubmitSearch

Step 3 thru 5 are repeated.

So if you follow the workflow above it currently does not matter if it is a textbox and you click enter or a dropdown and you choose a value if the search button is enabled because all the required fields have valid values the search will be executed.

So I guess I explain all of this looking for input... If I add an autoexecute flag with true or false on the whole expression then that would control all the textboxes and the dropdowns in that expression and AutoSubmitSearch would or would not get fired based on that flag. Or I could put an optional autoexecute flag on each expression value so that you would have tighter control over each expression value and whether it individually fires the AutoSubmitSearch.

And do you think the autoexecute should default to true or false is not provided in the xml?

Re: Problem using multiple expressions in eSearch 3.1

AnthonyGiles — Fri, 01 Feb 2013 15:37:20 GMT

Robert,

My personal preference would be the second option if it gives you tighter control. I always think it is better to have the most control you can.

Regards

Anthony

Re: Problem using multiple expressions in eSearch 3.1

RhettZufelt — Mon, 04 Feb 2013 16:38:33 GMT

I would second the second option.

preference would be default to true. would make it an obvious feature, but one could disable if not desired.

R_

Re: Problem using multiple expressions in eSearch 3.1

RobertScheitlin__GISP — Tue, 05 Feb 2013 20:40:22 GMT

Guys,

Version 3.1.8 - 2/5/2013
* Fixed Localization issue with export2csvoptionlabel and export2txtoptionlabel
* Added autosubmit to expression values to allow control over whether a dropdown list
automatically fires the search upon selection and textbox when the enter key is pressed.
The default is true if this attribute is not used.