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; } } }

Enhanced Search Widget for FlexViewer 2.1

RobertScheitlin__GISP

All Here is my next widget in the FlexViewer 2.1 series

Special thanks to Erwan Caradec for contributing to this code.

The Enhanced Search Widget extends the standard search widget with a floating data grid and a new spatial query w/buffering.

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

Encontre mais publicações marcadas com

Accepted answers

All comments

RobertScheitlin__GISP

Nestor,

I just downloaded it and added the uncompiled src to a clean flex viewer 2.2 and I got no errors...
Are you using the compiled version? If so which one?

NestorNavarro

I'm using the uncompiled version.
All I did was replace the old folder with the new version folder, recompile, clear the cache and that was it, started getting the error. Then I tried it with my xml including your changes such as the enable export true elements and I get the same error. What is that error anyway?

I will replace it with the old version again (2.2.3) and see if it works normally again.

Nestor.

RobertScheitlin__GISP

Nestor,

Are you copying the whole eSearch folder? The addition of an assets folder was made in between version 2.2.3 and 2.2.7.

The 2124 error means: #2124: Loaded file is an unknown type.

LisaArnold

All,

New version is available.

Version 2.2.7 - 02/04/2011

* Added ability to define a simple marker symbol for point or the current picture marker symbol.

Hi Robert,

Thanks for adding in the ability to have a simple marker symbol for point data. I have implemented 2.2.7 and commented out my picturesymbol code. I am seeing something odd in my results though. I have point data symbolized in different colors, for all but one of the colors the simple marker symbol appears on top of the point. For all my points which are grey, its like I am only seeing the outline of the simple marker symbol and can still see my colored grey point in it. I attached a screen shot and put my code lines below. As a not, I switched my style to circle instead of square, but the same thing happens with the square. Any ideas on what might be happening here?

<simplemarkersymbol style="circle" size="12" color="0x00ffff" alpha="0.5" xoffset="0" yoffset="0" angle="0">
      <outline style="solid" color="0x00ffff" alpha="1" width="1"/>
     </simplemarkersymbol>
     <!--<picturemarkersymbol url="assets/images/tick.png" height="16" width="16" xoffset="0" yoffset="0" />-->

2011-02-07_gpd.png

RobertScheitlin__GISP

Lisa,

Must be a something simple. I did a search for 2003 using your map service and zoom to the same area and don't have that issue.

Lisa.jpg

RobertScheitlin__GISP

I'm using the uncompiled version.
All I did was replace the old folder with the new version folder, recompile, clear the cache and that was it, started getting the error. Then I tried it with my xml including your changes such as the enable export true elements and I get the same error. What is that error anyway?

I will replace it with the old version again (2.2.3) and see if it works normally again.

Nestor.

Nestor,
There was an issue with 2.2.7 I have it fixed in 2.2.7f

NestorNavarro

Nestor,
There was an issue with 2.2.7 I have it fixed in 2.2.7f

Hey Robert.

I have not loaded 2.2.7f yet but the problem was resolved once I put the following line in from the 2.2.3 xml:

<info>widgets/InfoTemplates/InfoPopupWidget.swf</info>

No more errors after that.

I will check out 2.2.7f. Thanks !!

Nestor.

NestorNavarro

Looked at 2.2.7f and I see we are on the same page. Was that the only change from 2.2.7?
If so, I am leaving it alone until the next upgrade.

Thanks ..

Nestor.

RobertScheitlin__GISP

Nestor,

There was another things fixed but since you has version 2.2.3 installed at one point it is not an issue for you so I would say you can wait for the next version (although I am not sure what else could be added to this widget at this point).

NestorNavarro

Thanks Robert !!

It is a great widget and the resizing is a nice touch.
Only thing I need is for the API to handle one to many relationships and everyone would be happy.

Nestor.

CynthiaMatney

I have the newest Enhanced Serach Widget downloaded 2.2.7f - One of my layers I want to be able to search is my zoning layer. It works fine until I try to use the domain "usedomain="true'... I run my viewer and when I open the search window it shows up as it should - shows my domain values of my zoning layer in a dropdown box. However, when I click on one to search (ie: "R-1A") - it returns no values. If I take out the line "usedomain" then type in "R-1A" myself - then values are returned. Any ideas?
Thanks!

RobertScheitlin__GISP

Cynthia,

Can you go to your REST Service Directory and copy some of the lines like this and paste them for me to review:

Fields:

    * OBJECTID (Type: esriFieldTypeOID, Alias: OBJECTID)
    * Local_ID (Type: esriFieldTypeString, Alias: Local ID, Length: 10 )
    * Bin (Type: esriFieldTypeInteger, Alias: Bin)
    * Length_ (Type: esriFieldTypeDouble, Alias: Length)
    * B_Road_W (Type: esriFieldTypeDouble, Alias: Bridge Roadway Width (Curb to Curb))
    * Deck_W (Type: esriFieldTypeDouble, Alias: Deck Width (Out to Out))
    * Approach_R_W (Type: esriFieldTypeDouble, Alias: Approach Roadway Width)
    * Span_Num (Type: esriFieldTypeSmallInteger, Alias: Number of Spans)
    * M_Span_L (Type: esriFieldTypeDouble, Alias: Max Span Length)
    * Deck_Cond_C (Type: esriFieldTypeString, Alias: Deck Condition Code, Length: 5, Domain: Coded Values: , [9: 9 - Superior to present desirable criteria], [8: 8 - Equal to present desirable criteria], ...8 more... )

I am interested in seeing the fields that have domains.

CynthiaMatney

Fields:
OBJECTID (Type: esriFieldTypeOID, Alias: OBJECTID)
ZONECLASS (Type: esriFieldTypeString, Alias: Zoning Classification, Length: 10, Domain: Coded Values: [Agriculture District: A], [Suburban Residential District: R-1A], [Low-Density Single-Family Residential District: R-1B], ...29 more... )
ZONEDESC (Type: esriFieldTypeString, Alias: Zoning Description, Length: 100, Domain: Coded Values: , [R-1A: Surburban Residential District], [R-1B: Low-Density Single-Family Residential District], ...29 more... )
ACRES (Type: esriFieldTypeDouble, Alias: ACRES)
SHAPE (Type: esriFieldTypeGeometry, Alias: SHAPE)
URL (Type: esriFieldTypeString, Alias: URL, Length: 200 )
ZONE_OFF (Type: esriFieldTypeString, Alias: Official Zoning, Length: 20 )
SHAPE.area (Type: esriFieldTypeDouble, Alias: SHAPE.area)
SHAPE.len (Type: esriFieldTypeDouble, Alias: SHAPE.len)

RobertScheitlin__GISP

Cynthia,

Now can I see your SearchWidget.xml

CynthiaMatney

This is the only part I have changed on the xml.

<layer>
<enableexport>true</enableexport>
            <name>Zoning</name>
            <url>http://maps/ArcGIS/rest/services/Layers/Zoning/MapServer/0</url>
            <expressions>
             <expression alias="Zoning Code"
              textsearchlabel="Search Zoning Code [ Example: R-1A ]:"
              field="ZONECLASS" usedomain="true">upper(ZONECLASS) = upper('[value]')</expression>
             <expression alias="Zoning Name"
              textsearchlabel="Search Zoning Name [ Example: SUBURBAN RESIDENTIAL DISTRICT ]:"
              field="ZONEDESC" usedomain="true">upper(ZONEDESC) = upper('[value]')</expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Zoning</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>ZONECLASS</titlefield>
            <linkfield linkprefix="" linksuffix="">URL</linkfield>
   <icon isfield="true" iconprefix="" iconsuffix=""></icon>
            <fields all="false">
                <field name="ZONECLASS" alias="Zoning Code"/>
                <field name="ZONEDESC" alias="Zoning Name"/>
                <field name="ACRES" alias="Acres"/>
                <field name="URL" alias="URL"/>
            </fields>
        </layer>

RobertScheitlin__GISP

Cynthia,

Hmm... I was actually refering to the one that you are attempting to use the domain for. I need to see how you are setting that expression up.

CynthiaMatney

Cynthia,

Hmm... I was actually refering to the one that you are attempting to use the domain for. I need to see how you are setting that expression up.

Sorry - I changed it above.

philippschnetzer

Is it possible to query on two fields from the same layer in one expression? I have obviously had no luck in my attempts...

I am trying to get something like this:

PID LIKE '[value]%' AND AAN LIKE '[value]%'</expression>

to work...currently they are working as separate search expressions (PID LIKE '[value]%') and (AAN LIKE '[value]%').

Is this even possible with the eSearch Widget?

RobertScheitlin__GISP

philipp,

It is (sort of)... You can have any valid SQL expression run by this widget if you set the expression to:

<expression alias="Advanced Query" 
textsearchlabel="Enter any Valid SQL Expression"
field="" usedomain="false">[value]</expression>

This will force the user to be responsible for typing a valid SQL expression in the input text box.

This is the only way you can do it, as this widget does not and probably never will support multiple fields and values (that what the Query Builder widget is for).

KarlWilson

Hi Robert,

Is it possible to remove the bottom half of the Spatial search window if no <spatialrelationships> are defined?

I want to retain the search distance buffer functionality, but remove the other spatial relationship searches. Currently when I comment out the <spatialrelationship> tags I still have the "Search entities of:" etc remaining, (see screenshot).

Sorry if a similar question has already been answered - I didn't have time to go through all the 293 replies in this topic!

Cheers,
Karl

eSearch.png

RobertScheitlin__GISP

Karl,

Version 2.2.8 addresses this issue and another. Which is available now.

KarlWilson

Thanks Robert.

The download link on the code gallery page still points to the 2.2.7f release, rather than 2.2.8.
http://www.arcgis.com/home/item.html?id=5d4995ccdb99429185dfd8d8fb2a513e

Karl

RobertScheitlin__GISP

Karl,

Some how the upload must have failed... Anyway it uploaded again and downloaded to ensure.

KarlWilson

Thanks Robert.

I have now downloaded 2.2.8 and re-compiled my project, but the original problem persists. I'm still seeing the combo box and label after commenting out all the <spatialrelationship> tags.

Regards,
Karl

RobertScheitlin__GISP

Karl,

Hav you cleared your browsers cache to ensure you are using the changed xml file and not a cached one? I just tested this again and it works fine.

KarlWilson

OK thanks Robert.

I cleared the cache and re-compiled the project several times and it still didn't work, ...and then suddenly it did. I'm not sure what happened, but nevermind it works now.

JeffLegato

Robert, as always thank you for all your work on this. I installed the latest eSearch 2.2.8 and noticed that the export to csv is no longer there. We really enjoyed that feature. Can you bring it back?

Thanks!

Jeff Legato

RobertScheitlin__GISP

Jeff,

You need to read the documentation carefully. That option is not removed, you now have the ability to disable the export on a layer by layer basis and that is controlled by the SearchWidget.xml. It sounds like you are missing the new

<enableexport>true</enableexport>

in your layer element.

JeffLegato

You need to read the documentation carefully.

My bad!:o Sorry for that. It's working perfectly! Thanks so much! 😄

NathanEnge

Robert, is there any possibility to either specify coded values as dropdown in the config.xml to show in the text search?

or search through the recordset for unique values at the mxml level and populate a dropdown box in the text search?

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.