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: true Valves http://valhalla:6080/arcgis/rest/services/WebMap/MapServer/9 FACILITYID = '[value]' Use one of the graphical search tools to select Valves true FACILITYID 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.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Esearch - Error 1009

Scott_Russell

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.

Encontre mais publicações marcadas com

Accepted answers

RobertScheitlin__GISP

Scott,

As mentioned in the couple of post above there is a bug when not specifying a dateformat in the eSearchWidget.xml and because you choose to use fields all = "true" you ended up encountering this error. I will have this fixed in version 3.0.8 along with some other great little additions. So make sure you stay current with the releases of this widget.

Don't forget to click the Mark as answer check on this post and to click the top arrow (promote).
Follow the steps as shown in the below graphic:

All comments

Gyeong_MinRoh

Robert,

I also had the same error #1009 and already solved it as you explained above.
Thank you.

rzufelt

Robert, I wondered if the all="true" had something to do with it, so I tested as much as I could with that (with services that have and do not have a date field).

Could not make it give me that error using FGDB FC with server 10.0 and using the uncompiled version.

Not sure if this only happens in app builder or not as I do not use app builder myself.

In case this might help you "fix" it,

R_

RobertScheitlin__GISP

Scott_Russell

Scott,

Here you go replace all your xml for the eSearch Widget with what you copy from the attachment and see if that fixes it.

Robert,

I copy/pasted the contents of that XML into the eSearch widget. When I enter a value and click search there is no following action. There is no error, it just seems as if the function does not respond.

Scott

EDIT: ROBERT!! IT WORKED!!! I replaced the existing REST URL with our own, and everything is functional!! I'm stoked! Thank you so much for putting so much time into this, it must have taken you a while to type out all of these fields. Thank you VERY much!!

What do you think was wrong?

RobertScheitlin__GISP

Cory,

I gave him a complete eSearchWidget.xml configured for his layer and he should be good to go with that.

CoryHines

Will do Robert. I need to add quite a few "helper" items before I push this out.

As for Scott's issue. Maybe attempt to specify just one field for the return results?

Good luck.

RobertScheitlin__GISP

Cory,

No worries. I just wanted be sure not to get off helping with your issue when Scott's issue had not be resolved. I did find the dateformat issue a little after you had posted your issue so you posting did help. I will have the dateformat bug trapped in the next version. BTW I take care of this in the code but the new spark date format is "MM/dd/yyyy". This is actually the reason for the bug in the 3.0.7 as I was attempting to fix the dateformat and there were some that were not specifying it like you and all those people that are using all fields. But in the next version this will not be an issue. As I mentioned earlier you my want to make this correction to your xml so that the user will have an example of a subdivision to use:

            <expressions>
                <expression alias="Subdivision Name" textsearchlabel="Search Subdivision Name">
                    <values>
                        <value prompt="Example: BOYSON ROAD 1ST">SUBDIVISIONNAME LIKE '[value]%'</value>
                    </values>
                </expression>
            </expressions>

CoryHines

My apologies guys.

I just noticed that I had the same issue going on. I did discover what the problem was. I had a date field being returned, but didn't add the data format tag in the xml. I don't know if this is the same issue you are having Scott since you are returning all fields without specifying them individually.

<field name="DATE_" alias="Date Recorded" dateformat="MM/DD/YYYY"/>

Again, my apologies for posting in the incorrect post.

Thanks guys.

RobertScheitlin__GISP

Scott,

Here you go replace all your xml for the eSearch Widget with what you copy from the attachment and see if that fixes it.

eSearchWidget.zip

rzufelt

Well, not sure what else I can do to help as I avoid SDE like the plague and am only running server 10.0 so can't really test much.

If the new column doesn't work, if it were me, I'd export the data to a FGDB feature class, make a new service from that, then try to search again. Would also try to search other fields in the same service.

Sometimes it is easier to try to find something that does work, then try to figure it from there (or just move on ) 🙂

R_

RobertScheitlin__GISP

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.

RobertScheitlin__GISP

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.

CoryHines

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>

Scott_Russell

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.

rzufelt

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_

Scott_Russell

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!!

Scott_Russell

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

flexviewerforum.zip

rzufelt

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_

RobertScheitlin__GISP

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

Scott_Russell

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

flexviewerforum.JPG

RobertScheitlin__GISP

Scott,

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

Scott_Russell

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

SearchWidget.zip

RobertScheitlin__GISP

Scott,

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

Scott_Russell

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

eSearch.zip

rzufelt

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_

RobertScheitlin__GISP

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.

Scott_Russell

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.

Scott_Russell

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

RobertScheitlin__GISP

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.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.