topic Re: eSearch Question in ArcGIS Viewer for Flex Questions

eSearch Question

MattPohl — Thu, 07 Feb 2013 16:39:03 GMT

Robert-

Forgive me if this can be found in the documentation; I search but found nothing regarding it. Prior to versions 3.1.x if i included "All" at the beginning of a userlist the drop-down would auto-populate with "All" when the widget was launched. In the 3.1.x version no matter what I do I can not get the drop-down to auto-populate with any list item. Does this functionality still exist? I have attached a couple of screen shoots showing what I am talking about. Thanks for any help.

Matt

Re: eSearch Question

RobertScheitlin__GISP — Thu, 07 Feb 2013 16:55:35 GMT

Matt,

It use to function that way because I always set the selected index of the dropdown to the first item in the list. I no longer do this if the is value required is set to true.

Re: eSearch Question

Anonymous User — Thu, 07 Feb 2013 17:28:32 GMT

Original User: teamworksintl

Robert,

So are you saying that if the isvaluerequired is set to "false" that it should auto-populate?

Re: eSearch Question

RobertScheitlin__GISP — Thu, 07 Feb 2013 17:37:37 GMT

Matt,

Yes with the first value in the list.

Re: eSearch Question

Anonymous User — Thu, 07 Feb 2013 17:47:29 GMT

Original User: teamworksintl

Robert,

I have isvaluerequired is set to "false" on all values but still getting an un-populated drop-down. Partial code attached.

Re: eSearch Question

RobertScheitlin__GISP — Thu, 07 Feb 2013 18:35:30 GMT

Matt,

I will have to look into that.

Re: eSearch Question

Anonymous User — Thu, 07 Feb 2013 18:55:14 GMT

Original User: teamworksintl

Thanks Robert... your help is always appreciated

Matt

Re: eSearch Question

MattShetzer — Thu, 28 Feb 2013 16:08:41 GMT

Robert,
I am seeing something similar with the latest version of the esearch widget, and hopefully this will help.

When I use this code, the auto populating field works just fine.

<value prompt="Lease ID: [Ex: 2]" isvaluerequired = "false"   operator="AND">LEASEID = [value]</value>

<value prompt="Lease Status: [ Auto Populate ]"   isvaluerequired = "false" uniquevalsfromfield="LeaseStatu" operator="AND">LeaseStatu = '[value]'</value>

When I just use this, the field does not populate at all.
<value prompt="Lease Status: [ Auto Populate ]"   isvaluerequired = "false" uniquevalsfromfield="LeaseStatu" operator="AND">LeaseStatu = '[value]'</value>

Or when I stack two auto-populated together, the second auto-populated field (in this example, Landman) does not populate.

<value prompt="Well Name (Wildcards)" isvaluerequired = "false"   operator="AND">upper(F_NAME) LIKE upper('%[value]%')</value>
<value prompt="API:" isvaluerequired="false" operator="AND">API = '[value]'</value>
<value prompt="Status [ Auto Populate ]" isvaluerequired="false" uniquevalsfromfield="WellStatus" operator="AND">WellStatus = '[value]'</value>
<value prompt="Landman: [ Auto Populate ]" isvaluerequired="false" uniquevalsfromfield="Landman" operator="AND">Landman = '[value]'</value>

Please let me know if I'm just doing something incorrect, or if you need any more clarification.

Thanks for such a GREAT Widget.
Matt Shetzer

Re: eSearch Question

Anonymous User — Thu, 28 Feb 2013 16:59:07 GMT

Original User: rscheitlin

Matt,

Are you saying

When I just use this, the field does not populate at all.
<value prompt="Lease Status: [ Auto Populate ]" isvaluerequired = "false" uniquevalsfromfield="LeaseStatu" operator="AND">LeaseStatu = '[value]'</value>

You have no other value tags in this expression? If you do not then you should not be using the operator="AND"

By latest you mean 3.1.10 right?

Re: eSearch Question

RobertScheitlin__GISP — Thu, 28 Feb 2013 19:11:50 GMT

Matt,

In Version 3.1.9 it was reverted back to the way it was prior to 3.1.7. Meaning if the isvaluerequired attribute is set to true than the first item in the list will be selected automatically. If the isvaluerequired is set to false a blank value will always be added to the list and selected automatically.

Re: eSearch Question

Anonymous User — Thu, 28 Feb 2013 19:12:17 GMT

Original User: mshetzer

Robert,
I am running Version 3.1.10 - 2/26/2013

Thanks for the catch on the AND on the single value.

I removed the "AND" operator, but I am still struggling with the auto populate. I thought I had figured out the issue I was having, but it seems random. Sometimes it works as expected and populates the field, and on the next load of the SFV it doesn't populate the fields. Reload again, and it works.

Matt Shetzer

Re: eSearch Question

RobertScheitlin__GISP — Thu, 28 Feb 2013 19:26:01 GMT

Matt,

Is the service in question public? I have not seen what you are talking about using my services or esri public ones.

Re: eSearch Question

Anonymous User — Thu, 28 Feb 2013 20:31:36 GMT

Original User: mshetzer

Robert,
It is currently public, but not for long.

I'd like to email you the xml which points to the services.
Can you drop me an email to:

Matt.Shetzer@AmericanMappingSolutions.com

and I can forward the xml

Thanks,
Matt

Matt,

Is the service in question public? I have not seen what you are talking about using my services or esri public ones.

Re: eSearch Question

RobertScheitlin__GISP — Fri, 01 Mar 2013 17:09:36 GMT

Matt,

By "auto populate" do you mean having the drop down automatically selecting the first value or are you saying it does not populate the drop down list at all?

In version 3.1.9 and greater if you have isvaluerequired = "false" then a blank entry will be added to the drop down list as the first value and that will be automatically selected.

Re: eSearch Question

Anonymous User — Mon, 04 Mar 2013 16:36:13 GMT

Original User: mshetzer

Robert,
Thanks for your quick reply.

When I say auto-populate, the drop down selection box is populated with values that are contained in that field. It seems that the issue is intermittent as it works sometimes, but other times nothing is populated in the box and it is blank.

Here is an example of it working. Permitted, Producing, Proposed are all be populated from a Geodatabase.
[ATTACH=CONFIG]22351[/ATTACH]

Next time I run the SFV, I might just get blanks.

Thank you,
Matt

Re: eSearch Question

MichaelMiller2 — Mon, 04 Mar 2013 17:34:05 GMT

Robert,
Thanks for your quick reply.

When I say auto-populate, the drop down selection box is populated with values that are contained in that field. It seems that the issue is intermittent as it works sometimes, but other times nothing is populated in the box and it is blank.

Here is an example of it working. Permitted, Producing, Proposed are all be populated from a Geodatabase.
[ATTACH=CONFIG]22351[/ATTACH]

Next time I run the SFV, I might just get blanks.

Thank you,
Matt

I thought you had to use

uniquevalsfromfield=

to force values to appear in a dropdown?

Re: eSearch Question

Anonymous User — Mon, 04 Mar 2013 18:02:45 GMT

Original User: mshetzer

Correct, you need to use the uniquevalsfromfield=

This is the current statement that I am using. Sometimes it works, sometimes it doesn't.

<value prompt="Status [ Auto Populate ]" isvaluerequired="false" uniquevalsfromfield="WellStatus" autosubmit="false" operator="AND">WellStatus = '[value]'</value>

Matt

Re: eSearch Question

RhettZufelt — Mon, 04 Mar 2013 18:16:43 GMT

Matt,

Have you tried with Fiddler2 open to capture the web results?

Curious if you are getting the 200's on the MapServer/#/querys or if they are 404ing on you.

No matter what I've tried, I can't reproduce.

Also, can you reproduce the issue using a different service as your uniquvaluesfromfield layer?

R_