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 Part III

RobertScheitlin__GISP

All,

Here is a new thread to post questions and discuss the Enhanched Search Widget. The old thread was getting too long.

タグ付きの投稿をもっと見る

Accepted answers

All comments

ElizabethB

Hi Robert-

Yes, my sql syntax is correct. I should have mentioned I was masking the url to our server. Sorry about that! I am using fully qualified field names since the layer is joined to a view.

RobertScheitlin__GISP

Elizabeth,

So you have tested the Query at the REST End point just like I said in my last post (not just in ArcMap)?...
I actually have never tested a SDE View Join in my widget so it might be an issue there...

ElizabethB

Elizabeth,

So you have tested the Query at the REST End point just like I said in my last post (not just in ArcMap)?...
I actually have never tested a SDE View Join in my widget so it might be an issue there...

Robert-
Yes, I was able to query the REST end point successfully. Is there a problem w/joining a layer to a table for querying in the flex viewer? I see that as a basic need of end users, but nothing in the out-of-the-box widgets seem to allow for a user defined query. I am looking for a way to allow users to find parcels based on attributes of a CAMA table. This CAMA table is not really an sde view, it's actually a standalone table in our sde. (It has a legacy name of 'view' but it's not really a view).

Sorry I seem to be confusing the issue! Thanks for your help. If you don't think your widget is appropriate for my task do you happen to know one that would be?

RobertScheitlin__GISP

Elizabeth,

Querying a layer that has a join to a standalone table in SDE is absolutely supported and has been thoroughly test in this widget. There is even a running example of this on the widget live preview site. So it is just a matter of your configuration then. So what you have currently setup in the eSearchWidget.xml... Does it error out or give no results or what?

One of the immediate thing I saw was you had the operator attribute in the value tag and that is only needed when you have multiple value tags for using more than one field in the SQL Expression.

<value prompt="Example: Owner: " isvaluerequired="true" operator="AND">upper(santarosagis.GISADMIN.QS36F_SRVIEW1.OWNER_NAME) LIKE upper('%[value]%')</value>

If you take you eSearchWidget.xml file and zip it you will be able to attach the whole thing. You dont have to worry about masking the IP address as that IP is only an internal IP for your network and not something anyone could ping.

ElizabethB

Here's my zip file, Robert. I removed the part of your code that searches by Sub list (although I know we will want that later on down the line). So all I need this tool to do now is just search by owner name. I also removed the metric distance searches.. I left my mistake w/the operator syntax for you to look at. When I run the tool I get a error #1009.

Thanks again for your help!

configuration.zip

RobertScheitlin__GISP

Elizabeth,

What you sent is the zip is not the eSearchWidget.xml...

ElizabethB

Elizabeth,

What you sent is the zip is not the eSearchWidget.xml...

Hmm, am not seeming to have a good week! Ok, where exactly do I find said widget xml file? I copied the xml that shows up in the flex builder when I click 'modify' on the widget tab. That is the file that I have been editing, is that the problem? I know I really need a flex builder class. Unfortunately this project is fast tracked & has to come before any training.

Thanks for helping!

RobertScheitlin__GISP

Elizabeth,

If you are on a windows machine then the files would be located at:
C:\inetpub\wwwroot\flexviewers\YOUR APPLICATION NAME\widgets\eSearch

ElizabethB

Ok, here it is then! Thanks-

eSearch.7z.zip

RobertScheitlin__GISP

Elizabeth,

Can you paste your search url into your browser (http://192.1.1.163:6080/arcgis/rest/services/MyMapService/MapServer/5) and hit enter, this will take you to the Rest Service endpoint and there it will list all the fields and other details of your map service layer and if you have the ability to pint that page to a pdf or just take some screen captures of that info so I can take a look.

ElizabethB

Does this help any? Screenshot of the main services page of this service, and some of the SRView1 showing most of the fields. I didn't want to bombard you so if I haven't sent enough just let me know. Thanks!

Screenshot1.jpg

Screenshot1bottomhalf.jpg

SRView.jpg

SRVIewFieldNames.jpg

DavidColey

Hi Robert-
I aplogize for potentially being in the wrong thread. I was wondering if you had any difficulites in displaying coded values in either the primary feature class or related table when using the Enhanched Search Widget:

Version: 3.2.1
Build Date: 4/1/2013

I seem to be having difficulty displaying domain descriptions in fields that use coded value domains when I am also utililizing the usesubtype="true" setting. Any insight is appreciated and btw nice meeting you at the Dev Conference in March this year

thanks
David Coley
Sarasota County GIS
Sarasota County, FL

RobertScheitlin__GISP

Elizabeth,

As layer 5 is a Table and not a layer with geometry it has to be added to the tables and not the layers:

    <layers/>
    <tables>
        <table>
            <token/>
            <definitionexpression/>
            <enableexport>true</enableexport>
            <enableprintgrid title="Selected Owners">true</enableprintgrid>
            <name>Owner Name Search</name>
            <url>http://192.1.1.163:6080/arcgis/rest/services/MyMapService/MapServer/5</url&gt;
            <expressions>
                <expression alias="Owner_Name" textsearchlabel="Search Owner Last Name:" isvaluerequired="true">
                    <values>
                        <value prompt="Example: Owner: " isvaluerequired="true" >upper(OWNER_NAME) LIKE upper('%[value]%')</value>
                    </values>
                </expression>
            </expressions>
            <titlefield>OWNER_NAME</titlefield>
            <fields all="true"/>
            <links/>
            <queryattachments>false</queryattachments>
            <relates/>
            </relates>
        </table>
    </tables>

RobertScheitlin__GISP

David,

Yes there has been some issue with Subtype and how ArcGIS Server is returning field names in the wrong CaSe and with flex being a case sensitive language this is an issue but I though I have applied a work around in the code... Can you provide a screen shot(s) of your WHOLE Rest Service directory page for that layer and your eSearchWidget.xml (that is if your services and viewer are not public)?

DavidColey

Hey Robert, sure thing. I am going to go ahead and un-secure this service:

https://ags2.scgov.net/arcgis/rest/services/ScOperational/SCDataAgol/MapServer
and then let's work with the Parks layer at:
https://ags2.scgov.net/arcgis/rest/services/ScOperational/SCDataAgol/MapServer/25
If that's ok with you. I can leave it unsecure throughout the day oon 7/11/2013

The subtype field is 'ParkType', the 'PublicAccess' field has the coded domain values. I am not utilizing the coded domain field as as a search, but am returning its values. Perhaps it is the fact that these domain values are inherited?
Thanks, looking forward to your reply--

Here is my full layer xml section for this layer:

<layer>
     <token/>
<useproxy>false</useproxy>
<definitionexpression></definitionexpression>
<enableprintgrid title="Selected Parks">true</enableprintgrid>
<enableexport>true</enableexport>
        <name>Sarasota County Parks</name>
<url>https://ags2.scgov.net/arcgis/rest/services/ScOperational/SCDataAgol/MapServer/25</url>
<expressions>
   <expression alias="Park Type" textsearchlabel="Search by Park Type:" isvaluerequired="false">
    <values>
     <value prompt="Example: Natural Area Park" field="ParkType" usesubtype="true">ParkType = [value]</value>
    </values>
   </expression>
   <expression alias="Park Name" textsearchlabel="Search by Park Name:" isvaluerequired="true">
    <values>
     <value prompt="Example: Nathen Benderson Park" uniquevalsfromfield="ParkName">ParkName = '[value]'</value>
    </values>
   </expression>
</expressions>
   <graphicalsearchlabel>Use one of the graphical search tools to select Parks</graphicalsearchlabel>
   <spatialsearchlayer>false</spatialsearchlayer>
   <titlefield>ParkType</titlefield>
   <fields all="false">
    <field name="ParkType" alias="Park Type" gridfield="true" />
    <field name="ParkName" alias="Park Name" gridfield="true" />
    <field name="Address" alias="Address" gridfield="true" />
    <field name="Phone" alias="Phone Number" gridfield="true" />
    <field name="PublicAccess" alias="Public Access" gridfield="true"/>
   </fields>
   
   <zoomscale usegeometry="true" zoompercent="1.6" />
   <autoopendatagrid>true</autoopendatagrid>
   <relates>
    <relate id="2" label="Parks Information" enableexport="true" icon="assets/images/i_table.png">
     <fields all="false">
      <field name="ADA_Access" alias="Is ADA Accessible" />
      <field name="Concession" alias="Has Concesssions" />
      <field name="Restrooms" alias="Has Restrooms" />
      <field name="Showers" alias="Has Showers" />
      <field name="Playgrounds" alias="Has Playgrounds" />
      <field name="AthleticCourts" alias="Has Courts" />
      <field name="AthleticFields" alias="Has Ball Fields" />
      <filed name="CanoeKayakLaunch" alias="Has Kayak Launch" />
      <field name="BoatAccess" alias="Has Boat Access" />
      <field name="PicnicArea" alias="Has Picnic Areas" />
      <field name="CampingArea" alias="Has Camping" />
     </fields>
    </relate>
   </relates>
</layer>

RobertScheitlin__GISP

David,

Are you using the source code version of the widget? I have found the issue causing the coded values to not appear when the layer has a sub type, but as version 3.2 is now two versions old I don't update older version of the widget.

DavidColey

Hi Robert-
Thanks for the reply. Yeah, For us here in southwest Florida, hurricane season preparations tends to backlog my update frequency. Yes I am using the source code version if I understand you correctly, although I typically download from the eSearch.zip Code Attachement download section, and not from github. I'll be updating to 3.4 very shortly, and so wasn't going to spend alot of time on this, unless you had something already forked on github for this version, or had could direct me to a particular function in the mxml.

RobertScheitlin__GISP

David,

The changes are not hard and are limited to two files the main eSearchWidget.mxml and the SearchWidgetFixedDG.mxml

So here are the code changes:

eSearchWidget.mxml > function createSearchResults > sub function inside of createSearchResults called displayFields:
Just replace this similar if block (main Changes in Red).

                            if(layerDetails && field){
                                var typeID:String = null;
                                if (layerDetails.typeIdField && fieldName.toUpperCase() == layerDetails.typeIdField.toUpperCase()){
                                    typeID = layerDetails.typeIdField ? graphic.attributes[fieldName] : null;
                                    // replace value with feature type name
                                    var featureType:FeatureType = getFeatureType(typeID);
                                    if (featureType && featureType.name){
                                        value = featureType.name;
                                    }
                                }else{
                                    // replace value with coded value name if one exists
                                    var codedValue:CodedValue = getCodedValue(fieldName, value, typeID);
                                    if (codedValue){
                                        value = codedValue.name;
                                    }
                                }
                            }

SearchWidgetFixedDG.mxml > function dProvider
Just replace this similar portion of the for block (main Changes in Red).

                        for each (fld in _layerDetails.fields){
                            var typeID:String = null;
                            if (_layerDetails.typeIdField && fld.name.toUpperCase() == _layerDetails.typeIdField.toUpperCase()){
                                typeID = _layerDetails.typeIdField ? attributes[fld.name] : null;
                                // replace value with feature type name
                                var featureType:FeatureType = getFeatureType(typeID,_layerDetails);
                                if (featureType && featureType.name){
                                    attributes[fld.name] = featureType.name;
                                }
                            }else{

SearchWidgetFixedDG.mxml > function rdProvider
Just replace this similar portion of the for block (main Changes in Red).

                        for each (fld in _rlayerDetails.fields){
                            var typeID:String = null;
                            if (fld.name == _rlayerDetails.typeIdField){
                                typeID = _rlayerDetails.typeIdField ? String(attributes[_rlayerDetails.typeIdField]) : null;
                                // replace value with feature type name
                                var featureType:FeatureType = getFeatureType(typeID,_rlayerDetails);
                                if (featureType && featureType.name){
                                    attributes[fld.name] = featureType.name;
                                }
                            }else{

DavidColey

Thanks Robert, works like a charm. Let's see, if I'm following the programming logic correctly, the original variable typeID string in the layerDetails if block is set to return the attributes of any given field and when employed on a subtype field or codedDomain field the reutrn will be descriptions as designed. But when both subtypes and coded val domains descriptis are to be returned, the typeID has to essentially be cleared first, then set to return the decripts and not the codes...

Anyway, hope I haven't embarrased myself to badly here, please feel free to correct me and it's always a pleasure working with you. I'll shoot you a url when I put up a release build--

Thanks Again-
David

RobertScheitlin__GISP

David,

You are pretty well on track there. If the current field is the same as the field for the Sub Type then I need to get the value of that field and send it to the getCodedValues function as the typeID but if the field is not the same as the type id then the typeID should be null so that it actually gets the codedvalue from the field.

DavidColey

Yes, yes, yes, well described . . . and thanks again. I'll let you get back to your 3.4 changes 🙂

JoshWhite

I'm sorry if this has been mentioned before, two many posts to check all of them. I'm using Flex Viewer 3.2 and Version 3.2.3 of your Enchanced Search Widget. I'm trying to use it to notify people in the 200 foot buffer of a parcel. I've got everything set up to do the selection of parcels within this buffer area but I cannot seem to get the fixed datagrid to populate with anything. The autohide and everything works and the datagrid window opens just no data is displayed there. I attached my widget xml file. If there is anything else that would help please let me know.

eSearchWidget_1.txt.zip

RobertScheitlin__GISP

Josh,

Just little attention to detail stuff... You have your fields defined but for some reason put them in the relate section and you did not specify any of them as gridfields.

        <layer>
            <token/>
            <definitionexpression/>
            <enableexport>true</enableexport>
            <name>Parcels</name>
            <url>your url here</url>
            <expressions>
                <expression alias="PIN" textsearchlabel="Search by Parcel ID Number (PIN):" isvaluerequired="true">
                    <values>
                        <value prompt="Example: 3072504001001000" isvaluerequired="true" autosubmit="false">PIN = '[value]'</value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select a Parcel</graphicalsearchlabel>
            <spatialsearchlayer>true</spatialsearchlayer>
            <titlefield>OWNERNAME</titlefield>
            <fields all="false">
                <field name="PIN" alias="Parcel ID" gridfield="true"/>
                <field name="OWNERNAME" alias="Owner" gridfield="true"/>
                <field name="MAILADDR" alias="Mailing Address" gridfield="true"/>
                <field name="LEGALDESC" alias="Legal Description" gridfield="true"/>
                <field name="PropNum" gridfield="true"/>
                <field name="PropDir" gridfield="true"/>
                <field name="PropStrt" gridfield="true"/>
                <field name="COMMENTS" alias="Additional Info" gridfield="true"/>
            </fields>
            <links/>
            <zoomscale usegeometry="true" zoompercent="2"/>
            <autoopendatagrid>true</autoopendatagrid>
            <queryattachments>false</queryattachments>
            <relates />
            <symbology>
                <simplefillsymbol color="0xff0000" alpha="0.5">
                    <outline color="0xff0000" alpha="0.8" width="2"/>
                </simplefillsymbol>
            </symbology>
        </layer>

JoshWhite

Thanks, what I did was miss that whole section. I had it set to be fields all="true" so I just skimmed that section and completely missed the gridfield requirement. Using the relate part was just my attempt to figure it out, to see if I missed something. I appreciate your help. On another note, for some odd reason when I get my parcel layer from the county, the mailing address is included in the file and has carriage returns in it. In ArcMap, it just puts it all on one line and ignores these, but when using this widget, they are not ignored, is there anything I can do to get at the next lines?
An example is where I have one that has an ATTN line and then the address. So for the mailing address line, it just says ATTN: So and So and no actual address. I can manually fix these and obviously this isn't your problem its a data problem but I wondered what your thoughts were.

JoshWhite

I've discovered that for the most part I only use the graphical search when I use this widget. I tried using the <initialview> tag but it didn't have an effect, is this tag enabled in your widget or something similar?

RobertScheitlin__GISP

Josh,

I don't have any real suggestions on your data with carriage returns in it...

As far as the initalview thing the Enhanced Search Widget XML Configuration.pdf tell you the tag for that.

<defaultselectionoption>textInput</defaultselectionoption>

The defaultselectionoption element is a string that specifies which search option (i.e
graphicalInput or textInput
or spatialInput) will be the default search option for the widget.

JoshWhite

Josh,

I don't have any real suggestions on your data with carriage returns in it...

As far as the initalview thing the Enhanced Search Widget XML Configuration.pdf tell you the tag for that.

Thanks, I actually just discovered that in the configuration, sorry about that. I attempted to delete that post before you responded but didn't make it.

DanielBerry

Robert,

Does this widget support the ability to search layers with multipoint geometry?

Respectfully,
Dan

RobertScheitlin__GISP

Dan,

Are you having an issue with multipoints or are you just asking before trying?

DanielBerry

Robert,

I did test it out today. Unfortunately it was not displaying the graphics for any multipoint geometry and it also was only showing results from the multipoint geometry that only had a single point. I did have success with point geometry types. Is there a specific entry I need to add in the <layer> tag? I read through the "Enhanced Search Widget XML Configuration.pdf", but I didn't see anything that dealt with Multipoint geometry.

Respectfully,
Dan

Tested using Flex Viewer (ArcGIS API for Flex 3.3)

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

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