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.

Encontre mais publicações marcadas com

Accepted answers

All comments

BenScott1

Thanks Robert - I have discovered the problem - I was capitalising the V and R in isValueRequired. In the downloaded example eSearchWidget.xml the config item is written that way but when I make it all lower case as per the text you sent it works fine.

Thanks for your quick reply.

Cheers,
Ben

AngieAllison

Hello,
I am using the latest compiled eSearch version widget 3.3.1 in a new ArcGIS API 3.3 for Flex site and I am experiencing different results with my searches than when using the previous eSearch version 3.0.4 in an ArcGIS API 3.0 for Flex site. When I search for a polygon or point feature that returns enough points to zoom out to a scale threshold that the feature is not displayed at, the selected features are not showing up on my map. The search results window or the data grid will display the attributes of the features found and you can mouse thru the data and the tooltip window will move around on the map, but not until you zoom in to the scale threshold of the feature you searched on will they be displayed.
Is there something that I missed in upgrading my site and widget to the latest version? In version 3.0.4, when you would search for these same features they would be displayed on the map at any scale beyond the scale threshold that was set on the feature and I am looking for that same functionality so users will see the results immediately without having to zoom in to the scale dependency of that feature. Thanks, and any help would be appreciated.

I am having this same issue. Did you find a solution?

AngieAllison

Robert, do i need to set <geometryservice>http://tasks.arcgisonline.com/ArcGIS/rest/services/Geometry/GeometryServer</geometryservice> to my own Geometry service or can i use this one?
Also do i need to set this <spatialreference>102003</spatialreference> to my own wkid which is 3418??

RobertScheitlin__GISP

Marie,

Yes you should always use your own geometry service as esris gets a lot of traffic. Changing the spatialreference will depend on what spatialreference your basemaps are in. If you are using esris basemaps then NO. If you are using all of your own basemaps and they are in WKID 3418 then yes.

RobertScheitlin__GISP

Ben,

Thanks for letting me know. I will fix the example eSearchWidget.xml in the download ASAP.

RobertScheitlin__GISP

Patrick,

That is a side affect of the new version using a FeatureLayer and not a graphics layer as the results of as it inheriets the scale dependency of the layer from the server. I will look at make the scale dependency configurable in the next version.

RobertScheitlin__GISP

All,

New Version available

Version 3.3.2 - 5/15/2013
* Added textqualifier tag for defining the character that will be used in the export datagrid to signify that the
field contents are a string to programs like Excel®.
* Added removeserchlayersminmaxscale tag that specifies whether or not to remove the
MinScale and MaxScale of the layer that is set on the particular layer from ArcGIS Server.

PatrickWalker

Robert,
I have implemented your new eSearch version 3.3.2 update and it has taken care of allowing the display of the returned search results at any scale. Thank you for the quick update to this widget, and as always, your awesome support for all of us. Great job.

AngieAllison

Marie,

Yes you should always use your own geometry service as esris gets a lot of traffic. Changing the spatialreference will depend on what spatialreference your basemaps are in. If you are using esris basemaps then NO. If you are using all of your own basemaps and they are in WKID 3418 then yes.

Thanks for the info. I am up and running now. Aside from the zoom to layer as Patrick talked about. Thanks for this wonderfull widget. The end users will love being able to create there own "reports".

RobertScheitlin__GISP

Marie,

If you notice post #68 That issue is fixed in version 3.3.2.

CaseyMcMillin

Robert,

I was able to narrow it down to having multiple relates on one layer. Your corrections fixed the test environment I sent you and if I remove the second relate in my production environment it fixes that as well. With two relates on the same layer, I am still having the same issue. Here is the layer config with two relates:

  <layer>
            <token/>
            <definitionexpression/>
            <enableexport>true</enableexport>
            <name>Sanitary Main</name>
            <url>http://GIS01.lebanon.local:6080/arcgis/rest/services/OperationalLayers/Utilities/MapServer/3</url&gt;
            <expressions>
                <expression alias="Facility ID" textsearchlabel="Search Specific Main:" isvaluerequired="false">
                    <values>
                        <value prompt="Example: 1032" isvaluerequired="false">FACILITYID = [value]</value>
                    </values>
                </expression>
    <expression alias="Attributes" textsearchlabel="Search Mains:" isvaluerequired="false">
                    <values>
                        <value prompt="Type:" isvaluerequired="false" uniquevalsfromfield="TYPE" autosubmit="false" operator="AND">TYPE = '[value]'</value>
      <value prompt="Diameter:" isvaluerequired="false" uniquevalsfromfield="DIAMETER" autosubmit="false" operator="AND">DIAMETER = [value]</value>
      <value prompt="Material:" isvaluerequired="false" uniquevalsfromfield="MATERIAL" autosubmit="false" operator="AND">MATERIAL = '[value]'</value>
                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Main</graphicalsearchlabel>
            <spatialsearchlayer>true</spatialsearchlayer>
            <titlefield>Sanitary Main</titlefield>
            <fields all="false">
                <field name="FACILITYID" gridfield="true"/>
                <field name="TYPE" gridfield="true"/>
                <field name="DIAMETER" gridfield="true"/>
                <field name="MATERIAL" gridfield="true"/>
                <field name="YEARBUILT" gridfield="true"/>
                <field name="EDITDATE" gridfield="true"/>
                <field name="INSPECTIONDATE" gridfield="true"/>
            </fields>
            <links/>
   <zoomscale usegeometry="true" zoompercent="2"/>
            <autoopendatagrid>false</autoopendatagrid>
            <queryattachments>false</queryattachments>
            <relates>
    <relate id="0" label="Asbuilts" enableprintgrid="false">
     <fields all="false">
      <field name="ASBUILTID" gridfieldonly="true"/>
      <field name="FILEPATH" alias="View Asbuilt" gridfieldonly="true" hyperlinkgridfield="true" hyperlinkaliastext="View Asbuilt" linkprefix="http://GIS01/Asbuilts/" linksuffix=".pdf"/>
     </fields>
     <zoomscale usegeometry="true" zoompercent="1.6" />
    </relate>
    <relate id="1" label="TV Projects" enableprintgrid="false">
     <fields all="false">
      <field name="TVPROJECT" gridfieldonly="true" hyperlinkgridfield="true" hyperlinkaliastext="View TV Project" linkprefix="http://GIS01/TVProjects/"/>
     </fields>
     <zoomscale usegeometry="true" zoompercent="1.6" />
    </relate>
   </relates>
            <symbology>
                <simplelinesymbol color="0xff0000" alpha="0.8" width="2"/>                
            </symbology>
        </layer>

Thanks again for all the help and corrections.

Casey,

I was able to debug using the data you provided and narrow it down to the two main issues I told you about in my last post. The zoom scale I provided in red and removing the polygon symbology tags or better yet changing them to the proper polyline symbology:
            <symbology>
                <simplelinesymbol color="0x00ff00" alpha="0.8" width="2" />
            </symbology>
Fixed the issues for me. Can you try publishing the same data you sent me and configure it and see if you can get the same positive results I am getting? That way we can narrow things down more.

RobertScheitlin__GISP

Casey,

I am unable to test using the data you sent earlier as the second relate is not there. Can you sent all the data for the new test case?

KarenHolt

Hi Rob,

I have two questions.

1. I noticed that when my client ported their data into SQL ArcGIS 10.11 that my eSearch stopped working. I have spend the past few days upgrading to 3.3 and trying to get things to work. I have now narrowed down the problem to REST but wanted to know if you had any insight. I have full URL's below.

The query works fine when I use the following SQL statement:
(DATE_ >= '01/01/2008') AND (DATE_ <= '01/01/2009') AND (LABEL like 'COLORADO')

When I switch the order of the SQL statement I get an error - "The specified URL can't be found"
(LABEL like 'COLORADO') AND (DATE_ >= '01/01/2008') AND (DATE_ <= '01/01/2009')

2. Also, how do I display the date in a readable format in the grid?

Thanks,
Karen

This Works:
http://gis.fws.gov/arcgis/rest/services/FWS_FishIdentify/MapServer/0/query?where=%28DATE_+%3E%3D+%2701%2F01%2F2008%27%29+AND+%28DATE_+%3C%3D+%2701%2F01%2F2009%27%29+AND+%28LABEL+like+%27COLORADO%27%29&text=&objectIds=&time=&geometry=&geometryType=esriGeometryEnvelope&inSR=&spatialRel=esriSpatialRelIntersects&relationParam=&outFields=DATE_&returnGeometry=true&maxAllowableOffset=&geometryPrecision=&outSR=&returnIdsOnly=false&returnCountOnly=false&orderByFields=&groupByFieldsForStatistics=&outStatistics=&returnZ=false&returnM=false&gdbVersion=&returnDistinctValues=false&f=html

This does NOT work:
http://gis.fws.gov/arcgis/rest/services/FWS_FishIdentify/MapServer/0/query?where=%28LABEL+like+%27COLORADO%27%29+AND+%28DATE_+%3E%3D+%2701%2F01%2F2008%27%29+AND+%28DATE_+%3C%3D+%2701%2F01%2F2009%27%29&text=&objectIds=&time=&geometry=&geometryType=esriGeometryEnvelope&inSR=&spatialRel=esriSpatialRelIntersects&relationParam=&outFields=DATE_&returnGeometry=true&maxAllowableOffset=&geometryPrecision=&outSR=&returnIdsOnly=false&returnCountOnly=false&orderByFields=&groupByFieldsForStatistics=&outStatistics=&returnZ=false&returnM=false&gdbVersion=&returnDistinctValues=false&f=html

RobertScheitlin__GISP

Karen,

Sorry I don't have a clue why the label portion of the query being in front case the error (sounds like a call to tech support). As far as the datagrid and date you just need to specify the dateformat for the gridfield.

<field name="INSPECTIONDATE" gridfield="true" dateformat="MM/DD/YYYY" useutc="true" />

CaseyMcMillin

Casey,

I am unable to test using the data you sent earlier as the second relate is not there. Can you sent all the data for the new test case?

Robert,

Here is the data with the second relationship. I also included the eSearch config in case I have something horribly wrong in there. The second hyperlink needs to a folder rather than a document.

Thanks again,
Casey

RelationshipTest.zip

RobertScheitlin__GISP

Casey,

I do seem to have some sort of issue where you can not only specify on field in the relate if it is a hyperlink field. This is what worked for me:

            <relates>
                <relate id="0" label="Asbuilts" enableprintgrid="false">
                    <fields all="false">
                        <field name="ASBUILTID" gridfieldonly="true"/>
                        <field name="FILEPATH" alias="View Asbuilt" gridfieldonly="true" hyperlinkgridfield="true" hyperlinkaliastext="View Asbuilt" linkprefix="http://GIS01/Asbuilts/" linksuffix=".pdf"/>
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>
                <relate id="1" label="TV Projects" enableprintgrid="false">
                    <fields all="false">
                        <field name="FILEPATH" gridfieldonly="true"/>
                        <field name="TVPROJECT" gridfieldonly="true" hyperlinkgridfield="true" hyperlinkaliastext="View TV Project" linkprefix="http://GIS01/TVProjects/"/>
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>
            </relates>

Seems how you second relate is not a file but just a directory, do you have directory browsing enabled on your IIS virtual directory?

CaseyMcMillin

Casey,

I do seem to have some sort of issue where you can not only specify on field in the relate if it is a hyperlink field. This is what worked for me:

            <relates>
                <relate id="0" label="Asbuilts" enableprintgrid="false">
                    <fields all="false">
                        <field name="ASBUILTID" gridfieldonly="true"/>
                        <field name="FILEPATH" alias="View Asbuilt" gridfieldonly="true" hyperlinkgridfield="true" hyperlinkaliastext="View Asbuilt" linkprefix="http://GIS01/Asbuilts/" linksuffix=".pdf"/>
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>
                <relate id="1" label="TV Projects" enableprintgrid="false">
                    <fields all="false">
                        <field name="FILEPATH" gridfieldonly="true"/>
                        <field name="TVPROJECT" gridfieldonly="true" hyperlinkgridfield="true" hyperlinkaliastext="View TV Project" linkprefix="http://GIS01/TVProjects/"/>
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>
            </relates>

Seems how you second relate is not a file but just a directory, do you have directory browsing enabled on your IIS virtual directory?

Robert,
That does not resolve the error for me in the test or production environments. I do have directory browsing enabled in the virtual directory and the links work for both relates, but they both still cause the map to error. I am thinking I may just have to duplicate that layer with one relate per layer as a work around.
Thanks,
Casey

RobertScheitlin__GISP

Casey,

In my test environment using your data it works fine... When you say it errors what exactly do you mean (screenshots help)? Is there a particular Facility ID that is erroring? I have been using 143 and 1032 for testing.

CaseyMcMillin

Casey,

In my test environment using your data it works fine... When you say it errors what exactly do you mean (screenshots help)? Is there a particular Facility ID that is erroring? I have been using 143 and 1032 for testing.

Robert,
The error occurs any time I interact with the fixed datagrid (even clicking on the field that is not the hyperlink causes the error) regardless of Facility ID.
Thanks,
Casey

PreLink.jpg

PostLink.jpg

AngieAllison

Marie,

If you notice post #68 That issue is fixed in version 3.3.2.

yes i ran accross that today !! Thank you for the quick response on those changes !! I am totally up and running and i am positive the end users are going to love this. So much easier to use than the old query widget. Thanks again for your help. We are goin gto use this as well as a way to PRINT data. So i careted some searches that are by a facility id and coupied it out 10 or 12 times and then they can enter different facility id's, do the search and get the DATA into excel !!! awesome !! we have wanted to print data for a long time.

RobertScheitlin__GISP

Casey,

Remind me are you using the compiled or source code for this widget? If you are using the compiled are you sure that you have replaced the SearchWidgetFixedDG.swf with the latest from the download?

RobertScheitlin__GISP

Casey,

Did you upgrade to 3.3.1 or 3.3.2?

ShawnSimpson

Hi all - I hope I haven't overlooked the answer; however, I am having issues querying a field that participates in a table join. From what I can tell, it seems to be supported considering the user guides speak about using the full join field name? I could be wrong...

My code is similar to what is shown below below:

<expression alias="Valve ID" textsearchlabel="Search Valves by ID">
  <values>
    <value prompt="Example: 40361 (use % for wildcard)">wStreetValve.ValveID like '[value]'</value>
  </values>
</expression>

All fields are referenced using their full joined name. Is this not supported?

Thanks!
I appreciate any help that is offered.

I should add that the web app is built using Flex Viewer 2.5 and we are using version 2.9.0 for the Enhanced Search Widget.

RobertScheitlin__GISP

Shawn,

I tested Version 2.9.0.1 - 6-8-2012 using a joined map service and it worked fine.

CaseyMcMillin

Casey,

Did you upgrade to 3.3.1 or 3.3.2?

Robert,
I am using the compiled version. I upgraded to 3.3.2. I hadn't copied the swf from the upgrade, but just did and it did not make a difference.
More information in the interest of narrowing down the issue, everything works fine in the preview pane of the application builder, but not in an actual browser.

ShawnSimpson

Shawn,

I tested Version 2.9.0.1 - 6-8-2012 using a joined map service and it worked fine.

I've been combing through the XML file trying to see if I missed a syntax error and I have also been trying different combinations of things to see if there is two or more parameters not jiving with another. In doing this I have found that if I leave the fields tag set to show all, it works just fine. However, if I list the fields I want shown in the result display, the tool fails. Have you encountered this before?

To recap...

If I use the following code - all works:

<fields all="true"/>

If; however, I use the code below, the tool does not work:

<fields all="false">
 <field name="wStreetValve.SubtypeCode" alias="Type" gridfield="true" />  
 <field name="wStreetValve.ValveID" alias="ValveID" gridfield="true"/>
 <field name="wStreetValve.CMMSOrg" alias="Operating District" gridfield="true"/>
 <field name="wStreetValve.WaterType" alias="Water Type" gridfield="true"/>
 <field name="wStreetValve.Diameter" alias="Diameter" gridfield="true"/>
 <field name="wStreetValve.NormalPosition" alias="Normal Position" gridfield="true"/>
 <field name="IA_SVLV_Dimensions.Dimension_1" alias="Dimension 1" gridfield="true"/>
 <field name="IA_SVLV_Dimensions.Dimension_2" alias="Dimension 2" gridfield="true"/>
 <field name="IA_SVLV_Dimensions.Dimension_3" alias="Dimension 3" gridfield="true"/>
</fields>

In any event - At least it works 🙂

But - if you can think of or see anything I am doing wrong, I'd be most grateful. I'd rather limit the fields returned, if possible.

Thanks!

RobertScheitlin__GISP

Shawn,

The fact that it works with field all="true" tells me that you have an issue in your field names when you specify them. Flex is a case sensitive language. I would suggest triple checking you field names and case and eliminate fields one by one to diagnose the issue. Another thing is you can use a tool like fiddler to check the http traffic and see the response from ArcGIS Server.

ShawnSimpson

Shawn,

The fact that it works with field all="true" tells me that you have an issue in your field names when you specify them. Flex is a case sensitive language. I would suggest triple checking you field names and case and eliminate fields one by one to diagnose the issue. Another thing is you can use a tool like fiddler to check the http traffic and see the response from ArcGIS Server.

Ahh - I was not aware that Flex was case sensitive. That is excellent to know! I'll follow your suggestion and run through my field names with a fine-tooth comb.

As an aside - Thank you for this excellent tool! It is much, much better than the one the viewer comes with.

RobertScheitlin__GISP

Casey,

I am not sure that you have the latest version in your testing environment. Can you hold down the Alt key and click on the eSearch widgets title bar and check the dialog that pops up says 3.3.2?
Also can you try switching the eSearchWidget.xml floatorfixed to float

<floatorfixed>float</floatorfixed><!-- possible values are fixed and float -->

and test again?
MAKE SURE you clearing your browsers cache.

The reason for my asking this is I HAVE been able to duplicate you blank map situation with the popup in the upper left corner, but only when the relate is not getting the:

<zoomscale usegeometry="true" zoompercent="1.6" />

and in version 3.3.1 I added a change to the SearchWidgetFixedDG.swf to hard code a value if one is not found in the xml.

ShawnSimpson

Shawn,

The fact that it works with field all="true" tells me that you have an issue in your field names when you specify them. Flex is a case sensitive language. I would suggest triple checking you field names and case and eliminate fields one by one to diagnose the issue. Another thing is you can use a tool like fiddler to check the http traffic and see the response from ArcGIS Server.

Robert,

I've ran through the configuration file and there are no case issues between how I specify my field names and how they are within the feature class. The only way I can get the tool to work within a join is if I let it display all fields in the popup. I even tried just adding a single field element within the fields parent element and as soon as I start restricting fields, the tool errors out. I also tried turning fields off within the MXD and doing that causes the tool to error as well.

Could the period within the full join name be causing the issue? Are there any additional attributes that I need to set within the field element? Considering that the query works, I'm wondering if the tool is having a hard time generating the popup?

Also - if it turns out that I have to run with <fields all="true">, how do I configure a datagrid?

Thanks for any help you can provide! It is most appreciated. 🙂

Not sure if this helps, but I should add that the popups (e.g., Identify) work just fine when simply clicking any feature. And within the popup XML for the feature class in question, the fields and field elements are specified the same way as I have been trying to do in the 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.