topic Re: Esearch - Error 1009 in ArcGIS Viewer for Flex Questions

Esearch - Error 1009

Scott_Russell — Tue, 28 Aug 2012 14:18:22 GMT

Hello,

I posted a question similar to this in the Flex API forum yesterday. I am attempting to perform a SQL query for a TEXT field that is in our Valves feature class. The field is an ID number field but also contains letters. I'd like the user to have the ability to type in a valve number and successfully select it. Here is what I have so far:

<configuration>
    <layers>
        <layer>
            <definitionexpression/>
            <enableexport>true</enableexport>
            <name>Valves</name>
            <url>http://valhalla:6080/arcgis/rest/services/WebMap/MapServer/9</url>
            <expressions>
                <expression alias="Valve ID Search" textsearchlabel="Search Valve ID:">
                    <values>
                        <value prompt="Example:100">FACILITYID = '[value]'</value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Valves</graphicalsearchlabel>
            <spatialsearchlayer>true</spatialsearchlayer>
            <titlefield>FACILITYID</titlefield>
            <fields all="true"/>
            <links/>
            <zoomscale usegeometry="true" zoompercent="2"/>
        </layer>

Keep in mind that although this is a field used for IDs and most values are numeric, the field is a TEXT field which contains letters in some cases.

When I attempt to perform the above action I receive Error #1009. What am I doing wrong? I have confirmed that FACILITYID is the field alias within the table. I determined the URL by clicking on the Valves layer link in the REST services URL in ArcGIS Server.

Thanks,
Scott

EDIT: I'd like to point out that FACILITID = '[value]' yields results in the default Search widget in the Flex Viewer.

Re: Esearch - Error 1009

RobertScheitlin__GISP — Tue, 28 Aug 2012 14:59:23 GMT

Scott,

What version of the eSearch are you using? If you are at Flex Viewer 3.0 than you need to be using the latest eSearch Widget Version 3.0.7. To check which version of eSearch you are using launch the viewer and the eSearch widget and hold the alt key and click on the "Enhanced Search" widget title.

Re: Esearch - Error 1009

Scott_Russell — Tue, 28 Aug 2012 15:17:21 GMT

Scott,

What version of the eSearch are you using? If you are at Flex Viewer 3.0 than you need to be using the latest eSearch Widget Version 3.0.7. To check which version of eSearch you are using launch the viewer and the eSearch widget and hold the alt key and click on the "Enhanced Search" widget title.

Looks like I am using version 3.0.6. Well, this turned out to be embarrassing!!

Thank you very much for your speedy reply and great widgets that you have available!!

Thanks,
Scott

Re: Esearch - Error 1009

Scott_Russell — Tue, 28 Aug 2012 18:07:42 GMT

Hello Robert,

I removed the Widget from the 3.0 Flex Viewer. I re-downloaded the eSearch widget from the following location:

http://www.arcgis.com/home/item.html?id=5d4995ccdb99429185dfd8d8fb2a513e

After implementing eSearch again, I verified the version and it still says 3.0.6, Build date 8/15/2012. Is the download link pointing to the wrong file? I am still having the same problem with error #1009. I apologize for the mix-up, I should have replied earlier and tested this right away.

Any ideas? In the 'Manage Customer Widgets' interface, the eSearch widget is listed as version 3.0.7.

Re: Esearch - Error 1009

RobertScheitlin__GISP — Tue, 28 Aug 2012 18:36:06 GMT

Scott,

I just downloaded form that link and get 3.0.7... The fact that the widget reports as 3.0.7 in App Builder leads me to believe you are good. Can you attach your eSearchWidget.xml file? Maybe you deleted something that you should not have.

Re: Esearch - Error 1009

RhettZufelt — Tue, 28 Aug 2012 19:18:44 GMT

Hello,

I posted a question similar to this in the Flex API forum yesterday. I am attempting to perform a SQL query for a TEXT field that is in our Valves feature class. The field is an ID number field but also contains letters. I'd like the user to have the ability to type in a valve number and successfully select it. Here is what I have so far:

<values>
<value prompt="Example:100"> FACILITYID = '[value]'</value>
</values>

EDIT: I'd like to point out that FACILITID = '[value]' yields results in the default Search widget in the Flex Viewer.

are you sure you have the item spelled correctly? In your two examples, one that works, one that doesn't, you have different spelling. not sure if that is just a typo in the email or in your expression as well.

R_

Re: Esearch - Error 1009

Scott_Russell — Wed, 29 Aug 2012 11:52:46 GMT

are you sure you have the item spelled correctly? In your two examples, one that works, one that doesn't, you have different spelling. not sure if that is just a typo in the email or in your expression as well.

R_

Yikes!! Thanks for pointing that out, but it was a typo on my end when I was quickly editing my post. I double checked and the value is the same on my end. Thank you for that!!

Scott,

I just downloaded form that link and get 3.0.7... The fact that the widget reports as 3.0.7 in App Builder leads me to believe you are good. Can you attach your eSearchWidget.xml file? Maybe you deleted something that you should not have.

OK Robert, attaching .xml file to this post. I attached the eSearch.zip that I am pointing to from the Flex Viewer. Let me know if you need me to extract and send only the .xml. Thank you!!

Scott

Re: Esearch - Error 1009

RobertScheitlin__GISP — Wed, 29 Aug 2012 12:05:17 GMT

Scott,

No I need the eSearchWidget.xml where you have changed it to point to your data.

Re: Esearch - Error 1009

Scott_Russell — Wed, 29 Aug 2012 13:10:54 GMT

Scott,

No I need the eSearchWidget.xml where you have changed it to point to your data.

I only edited one small section at the beginning. I copy/pasted the xml code into Notepad++ to work with it. I saved that file, it is attached to this post. I had to zip it to get it under the size requirement. I left the default settings for most of the functionality, since I'm not sure exactly what I'll do with it yet.

Thanks,
Scott

Re: Esearch - Error 1009

RobertScheitlin__GISP — Wed, 29 Aug 2012 14:42:37 GMT

Scott,

Do you happen to have the ObjectID and/or Shape fields hidden for this layer in the MXD?

Re: Esearch - Error 1009

Scott_Russell — Wed, 29 Aug 2012 19:31:19 GMT

I do not. I attached a small screenshot of the attribute table and FACILITYID field properties from that MXD in case it is useful.

Thanks,
Scott

Re: Esearch - Error 1009

RobertScheitlin__GISP — Wed, 29 Aug 2012 19:53:59 GMT

Scott,

I am running out of ideas here, but lets try one more thing.

Paste this in your browsers addressbar and then copy all the results to a text file and attach it for me to review.

http://valhalla:6080/arcgis/rest/services/WebMap/MapServer/9?f=pjson

Re: Esearch - Error 1009

RhettZufelt — Wed, 29 Aug 2012 20:23:10 GMT

What happens if you try this?

<value prompt="Example:100">UPPER(FACILITYID) LIKE UPPER('%[value]%')</value>

I know this isn't what you are after, but if this gets results, there are some hidden spaces/characters in your attributes.

I've had issues like that before, then a LTrim(),RTrim() on the attribute column fixed it up.

Just a thought,

R_

Re: Esearch - Error 1009

Scott_Russell — Wed, 29 Aug 2012 20:27:43 GMT

Thank you very much for all of the time you're spending to help me. It is very appreciated.

I attached the .txt file for you.

Thanks,
Scott

Re: Esearch - Error 1009

Scott_Russell — Wed, 29 Aug 2012 20:28:43 GMT

What happens if you try this?
<value prompt="Example:100">UPPER(FACILITYID) LIKE UPPER('%[value]%')</value>
I know this isn't what you are after, but if this gets results, there are some hidden spaces/characters in your attributes.

I've had issues like that before, then a LTrim(),RTrim() on the attribute column fixed it up.

Just a thought,

R_

Strangely enough, this yielded error 1009 again. Thanks for the insight!!

Re: Esearch - Error 1009

RhettZufelt — Wed, 29 Aug 2012 22:31:59 GMT

What is the base data format? FGBD, PGDB, shapefile?

Also, have you tried making a new field and calculating it from the FACILITYID field and tried the search on that?

 [NEWFIELD] = Ltrim(Rtrim(FACILITYID))

<value prompt="Example:100">NEWFIELD = '[value]'</value>

In the past I have resolved some issues this way. Never found the problem, but "fixed" it.

R_

Re: Esearch - Error 1009

Scott_Russell — Thu, 30 Aug 2012 13:52:34 GMT

What is the base data format? FGBD, PGDB, shapefile?

Also, have you tried making a new field and calculating it from the FACILITYID field and tried the search on that?
 [NEWFIELD] = Ltrim(Rtrim(FACILITYID))
<value prompt="Example:100">NEWFIELD = '[value]'</value>
In the past I have resolved some issues this way. Never found the problem, but "fixed" it.

R_

It is a feature class within a SQL Server Geodatabase. I'll have to wait for after-hours some day to do this, hopefully tomorrow. Thank you, I will give it a shot.

I'm theorizing that something in my code is wrong. The query works great in the Search tool that comes with the Flex Viewer Builder, but failing in the eSearch. I'm flabbergasted.

Re: Esearch - Error 1009

CoryHines — Thu, 30 Aug 2012 14:27:10 GMT

Hi guys,

I too have run into this, but only at flex viewer 3. I have 2 identical queries, one at 2.2 and one at 3. The http requests are slightly different, but essentially the same, yet 2.2 returns a result, but 3 doesn't. It only seems to be an issue on the subdivision search. here are the 2 query specs and the sites you can test. for 2.2 = http://gis.linncounty.org/maps for 3 http://gis.linncounty.org/fv3

I also tried running the query against the TOWN field and get the same error, but I can't see anything that is wrong with the layer. Both sites are hitting the same service.

fv 2.2
<layer>
<name>Subdivisions</name>
            <url>http://gis.linncounty.org/arcgis/rest/services/LandRecords/MapServer/18</url>
            <expressions>
             <expression alias="Name" textsearchlabel="Search by Subdivision Name">SUBDIVISIONNAME LIKE '[value]%'</expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Subdivisions</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>SUBDIVISIONNAME</titlefield>
            <linkfield></linkfield>
   <icon isfield="true" iconprefix="" iconsuffix=""></icon>
   <zoomscale>4800</zoomscale>
            <fields all="false">
                <field name="SUBDIVISIONNAME" alias="Name"/>
    <field name="TOWN" alias="City or Twp"/>
    <field name="VOLUME" alias="Volume"/>
    <field name="PAGE" alias="Page"/>
    <field name="DATE_" alias="Date Recorded"/>
            </fields>
        </layer>

fv 3
<layer>
   <definitionexpression></definitionexpression>
   <enableexport>false</enableexport>
   <name>Subdivisions</name>
   <url>http://gis.linncounty.org/arcgis/rest/services/LandRecords/MapServer/18</url>
   <expressions>
    <expression alias="Subdivision Name" textsearchlabel="Search Subdivision Name">
     <values><value>SUBDIVISIONNAME LIKE '[value]%'</value></values>
    </expression>
   </expressions>
   <graphicalsearchlabel>Use one of the graphical search tools to select Subdivisions</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>SUBDIVISIONNAME</titlefield>
   <links></links>
   <fields all="false">
    <field name="SUBDIVISIONNAME" alias="Name"/>
    <field name="TOWN" alias="City or Twp"/>
    <field name="VOLUME" alias="Volume"/>
    <field name="PAGE" alias="Page"/>
    <field name="DATE_" alias="Date Recorded"/>
   </fields>
   <zoomscale usegeometry="true" zoompercent="1.2"></zoomscale>
</layer>

Re: Esearch - Error 1009

RobertScheitlin__GISP — Thu, 30 Aug 2012 14:35:52 GMT

Scott,

The fact that it works with the OTB SearchWidget would lead me to say you should not worry about creating a new field and the other suggestions of manipulating your data. I agree that it must be a configuration issue. Let me test the application builder package of the eSearch 3.0.7 and see if there is some things wrong with it, maybe something went wrong with the packaging. Also I may ask you to try a eSearchWidget.xml that I provide you.

Re: Esearch - Error 1009

RobertScheitlin__GISP — Thu, 30 Aug 2012 14:39:43 GMT

Cory,

Please start a new post so this one is not hijacked by your issue. When you do start a new thread please provide and example of what one would type in for a subdivision search as you neglected to provide this information to you end users in the widget and I have no familiarity with your data.