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.

Find more posts tagged with

Accepted answers

All comments

RobertScheitlin__GISP

Allison,

The issue you are having is that the unique value query that populates the dropdown is not currently programed to take the definitionexpression into consideration (an oversite). I will get this fixed in a future release.

RobertScheitlin__GISP

Ashley,

It is important to check if the widgets XML format has changed for certain elements when upgrading versions.

RobertScheitlin__GISP

Allison,

Version 3.6.1 now addresses your issue and the unique value dropdown list is now honoring the defention expression.

AllisonKampbell

Hi Robert: Thank you so much for addressing the definitionexpression and getting it done so fast. Much appreciated!

Allison Kampbell

Erickson_Contract_Surveying_

I am having a similar issue. I search for a line feature, then go to the Spatial Search to select parcels with a given distance, but they are not listed in the drop-down. I have the Parcel layer set to <spatialsearchlayer>true</spatialsearchlayer>. Not sure what the issue is. At first I thought the parcel layer wasn't on or at a visible scale, but that was not the case.

How do I go about getting the dropdown for "Search Entities of:" populated? Right now, I have one layer on the Text Search tab and the user can pick one of the features within that layer from a dropdown populated using "uniquevalsfromfield". Then, I want them to be able to use the Spatial Search tab to be able to specify a buffer and choose a different layer (from a choice of two) and select any entities of that chosen layer that are within the buffer. Ideally, they would have the option to select "all" so that either of the two layers within the buffer are selected

Select instance of proposed linear project > Buffer linear project a specified distance > Select buildings, observation points, or both

Here is the code I have now that successfully creates the Text Search tab for proposed linear projects, and creates the Spatial Search tab but with only the proposed linear projects layer in the "Search Entities of" dropdown.

Thanks for any help you can provide.

        <layer>
            <token/>
            <definitionexpression/>
            <enableexport>true</enableexport>
            <name>Proposed Project Search</name>
            <url>http://152.1.13.55/arcgis/rest/services/NERI/GIS550_Midterm_FeatureService_V1/MapServer/2</url>
            <expressions>
                <expression alias="Proposed Project Search" isvaluerequired="true">
                    <values>
                        <value prompt="Choose a Project - Example: test1" uniquevalsfromfield="project_name" isvaluerequired="true" autosubmit="false" operator="AND">project_name = '[value]'</value>

                    </values>
                </expression>
            </expressions>
            <graphicalsearchlabel>Use one of the graphical search tools to select Proposed Project</graphicalsearchlabel>
            <spatialsearchlayer>true</spatialsearchlayer>
            <titlefield>Proposed_Project</titlefield>
            <fields all="false">
    <field name="project_name" alias="PROJECT NAME" visible="true"/>
   </fields>
            <links/>
            <zoomscale usegeometry="true" zoompercent="1.2"/>
            <autoopendatagrid>true</autoopendatagrid>
            <queryattachments>false</queryattachments>
            <relates/>
            <symbology>
                <picturemarkersymbol url="assets/images/i_target.png" height="18" width="18" xoffset="0" yoffset="0"/>
            </symbology>
        </layer>

RobertScheitlin__GISP

Derek,

What version are you talking about? Can you post your eSearchWidget.xml?

Erickson_Contract_Surveying_

3.5.3

attached xml

Derek,

What version are you talking about? Can you post your eSearchWidget.xml?

eSearchWidget_Whi.txt.zip

RobertScheitlin__GISP

Derek,

It is just one of those small gotchas of Flex... Case Sensitivity. All the tags/elements and attributes in the eSearchWidget.xml are lower case.

<spatialSearchlayer>true</spatialSearchlayer>

Erickson_Contract_Surveying_

Gotcha. Thanks.

Question though: Has your code been changed since 3.5.3? I did not change your source code to <spatialSearchlayer>true</spatialSearchlayer> from <spatialsearchlayer>true</spatialsearchlayer>

Derek,

It is just one of those small gotchas of Flex... Case Sensitivity. All the tags/elements and attributes in the eSearchWidget.xml are lower case.
<spatialSearchlayer>true</spatialSearchlayer>

RobertScheitlin__GISP

Derek,

Nope. It has been that way for MANY versions. Maybe you are just now noticing it.

EricGardecki

Robert,

This is more of an FYI for the future, as I'm sure this certainly isn't much of a priority since it's a browser-related issue.

I found that when using the datagrid print function (glad this was added btw, quite helpful) in Chrome, it seems to not cooperate when switching to landscape. The data shown in the datagrid in my app extends more than the width of a portrait 8.5x11 and therfore creates a 2nd page. If I change the print settings to landscape, all it does it rotate the data to match. I found no way for this to print "correctly" in Chrome. However, in IE it works great.

RobertScheitlin__GISP

Eric,

When you say

If I change the print settings to landscape

How are you doing that as the print preview dialog shold not present you with that option? If I set the printers preferences in Windows to do landscape all the time and then print the datagrid it works fine in Chrome though.

EricGardecki

I had to use the "print using system dialog".

I suppose changing the default to landscape prior to printing each time would work but that isn't something an end user would think to do.

RobertScheitlin__GISP

Eric,

I dont think "print using system dialog" is something most endusers will know how to do either. I will look into it some more and see if there is a work around.

Erickson_Contract_Surveying_

Robert,

I have a LINE feature class that participates in a relationship class with a table called FILE_TABLE. Within the file table are record that contain PATH field values (images associated with the line) that point to a virtual directory within the Flexviewer. I created the relationship because joins aren't sufficing for us. A given line may have multiple files associated with it. We have been using a join to the file table, but the join as you know, only returns the first match.

I am trying to enable the hyperlink (for the PATH field) in related records returned by the search (by adding hyperlinkgridfield to the field tag), but when I click on it it says invalid argument.

I may be going about this completely wrong?

Derek Hunter

Is there a way to enable

Casey,

I don't know what else to tell you as I have now setup a Featureclass, a table, and a relationship Class in an Enterprise Geodatabase and tested a link to a pdf from a field in the related table and it works fine....

RobertScheitlin__GISP

Derek,

I can not tell you much of anything without seeing your layers XML configuration in the eSearchWidget.xml.

Erickson_Contract_Surveying_

<layer>
   <definitionexpression></definitionexpression>
   <enableexport>true</enableexport>
   <name>Pipeline</name>
   <url>http://ecs-gis.com/arcgis/rest/services/Search/MapServer/3</url>
   <expressions>
    <expression alias="Segment Name" textSearchlabel="Search by Segment Name...">
     <values>
      <value prompt="Example: johnston">FEATURE_NAME LIKE '%[value]%'</value>
     </values>
    </expression>
   </expressions>
   <graphicalsearchlabel>Use one of the graphical Search tools to select Centerline Corridors</graphicalsearchlabel>
   <spatialsearchlayer>true</spatialsearchlayer>
   <titlefield>FEATURE_NAME</titlefield>
   <fields all="false">
    <field name="ANC" alias="ANC" visible="true" gridfield="true"/>
    <field name="FEATURE_NAME" alias="Name" visible="true" gridfield="true" />
    <field name="LAYER" alias="Layer" visible="true" gridfield="true"/>
    <field name="CLASS" alias="Class" visible="true" gridfield="true"/>
    <field name="COMMODITY" alias="Commodity" visible="true" gridfield="true"/>
    <field name="DIAMETER" alias="Diameter" visible="true" gridfield="true"/>
    <field name="PL_STATUS" alias="Status" visible="true" gridfield="true"/>
    <field name="PATH" alias="Files" visible="true" hyperlinkgridfield="true"/>
    <field name="URL" alias="Videos" visible="true" hyperlinkgridfield="true"/>
    <field name="GIS_LENGTH" alias="Line Length" numberformat="0||" visible="true" gridfield="true"/>
    <field name="HORIZONTAL_LENGTH" alias="Length" numberformat="0||" visible="true" gridfield="true"/>
    <field name="ROFILE_LENGTH" alias="Profile Length" numberformat="0||" visible="true" gridfield="true"/>
   </fields>
   <links/>
   <zoomscale usegeometry="true" zoompercent="1.1"/>
   <autoopendatagrid>true</autoopendatagrid>
   <queryattachments>false</queryattachments>
   <relates>
    <relate id="0" label="File" enableprintgrid="true" icon="assets/images/i_hydro.png" printtitle="Related Files">
     <fields all="true" />
     <zoomscale usegeometry="true" zoompercent="1.2" />
    </relate>
   </relates>
   <symbology>
    <simplefillsymbol color="0x0000ff" alpha="0.5">
     <outline color="0x00ffff" alpha="0.8" width="2" />
    </simplefillsymbol>
   </symbology>
</layer>

Derek,

I can not tell you much of anything without seeing your layers XML configuration in the eSearchWidget.xml.

RobertScheitlin__GISP

Derek,

How exactly are you defining a hyperlink field for the relate when you are just using fields all = true?

<relate id="0" label="File" enableprintgrid="true" icon="assets/images/i_hydro.png" printtitle="Related Files">
    <fields all="true" />
    <zoomscale usegeometry="true" zoompercent="1.2" />
</relate>

If you want a hyperlink in the related data then you have to tell it which field is going to be the hyerlinkfield.

Like this:

                <relate id="3" label="Signs" enableexport="false" enableprintgrid="true" icon="assets/images/i_lego.png">
                    <fields all="false">
                        <field name="Type" />
                        <field name="Road_ID" />
                        <field name="Condition" />
                        <field name="P_Hyper" />
                        <field name="Image_" hyperlinkgridfield="true" hyperlinkgridicon="assets/images/i_lego.png"
                            hyperlinkaliastext="Get Sign Image" linkprefix="" linksuffix="" />
                        <field name="post" />
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>

Erickson_Contract_Surveying_

Sorry...meant to say all I used was hyperlinkgridfield="true".

I attached a screenshot of the results which is now showing relates, however, the record height is very small. Have you seen that?

[ATTACH=CONFIG]30290[/ATTACH]

Derek,

How exactly are you defining a hyperlink field for the relate when you are just using fields all = true?

<relate id="0" label="File" enableprintgrid="true" icon="assets/images/i_hydro.png" printtitle="Related Files">
    <fields all="true" />
    <zoomscale usegeometry="true" zoompercent="1.2" />
</relate>

If you want a hyperlink in the related data then you have to tell it which field is going to be the hyerlinkfield.

Like this:

                <relate id="3" label="Signs" enableexport="false" enableprintgrid="true" icon="assets/images/i_lego.png">
                    <fields all="false">
                        <field name="Type" />
                        <field name="Road_ID" />
                        <field name="Condition" />
                        <field name="P_Hyper" />
                        <field name="Image_" hyperlinkgridfield="true" hyperlinkgridicon="assets/images/i_lego.png"
                            hyperlinkaliastext="Get Sign Image" linkprefix="" linksuffix="" />
                        <field name="post" />
                    </fields>
                    <zoomscale usegeometry="true" zoompercent="1.6" />
                </relate>

relate.jpg

RobertScheitlin__GISP

Derek,

I don't think I have ever had anyone just try to use one field as it also be a hyperlink... Try adding an field as well as the hypelink field.

Erickson_Contract_Surveying_

It was because I did not have the i_relate.png in the Search asset\images folder.

Can you tell me if this same ability for relates is available for the Identify tool? Not seeing it in 3.5

Thank for you help!

Sorry...meant to say all I used was hyperlinkgridfield="true".

I attached a screenshot of the results which is now showing relates, however, the record height is very small. Have you seen that?

[ATTACH=CONFIG]30290[/ATTACH]

RobertScheitlin__GISP

Derek,

Nope, the Identify Widget does not support relates.

KevinHigh

Hi Robert,

First of all - thank you so much for all your help over the years. You are an invaluable asset to the GIS community.

I'm having an issue with the enhanced search widget. Every time I switch <fields all=" from "true" to "false", I get an error when I search on that layer that says

[RPC Fault faultString="Invalid or missing input parameters." faultCode="400" faultDetail=""]

It works fine when I change it back to <fields all="true">. I want to use "false" because I would like to use the results in the data grid.

Attached is my eSearchWidget.xml. My layer has a join on it, but I am using the correct field names.

What am I missing?

Thanks,
Kevin

EDIT: viewer version: 3.6, widget version 3.6.1.

eSearchWidget.zip

RobertScheitlin__GISP

Kevin,

If you leave it to true, do all three of your queries work for that layer?

KevinHigh

Yes, all three of them work.

RobertScheitlin__GISP

Kevin,

So I have joined data working fine in eSearch, so I am not sure what issue you are running into. Without access to your map service, all I can tell you is the steps I would take to diagnose the issue yourself.

Limit your fields to one field that same one you use for the titlefield. See if this works.
If #1 works then you likely have an issue in one of the field names you are using.
Check the CaSe of your field names as Flex Language is a CaSe sensitive language.

KevinHigh

I finally got it to work. When I changed the title field to use the full name of the field, everything seemed to sync up and work.

Thanks for your help!
Kevin

JeffmcGuire

Question about Fixed Datagrid Setup

Robert,

First, thank you for all the code!

**Flex viewer 3.6 working with the 3.6.1 version of the search widget.

I am trying to follow the instructions to get the Fixed DG code section into the appropriate part of the configuration.

I don't see a UI elements comment in the code, and I also dont see the overview map widget either. Im using a find tool, and reading a lot. Trying to figure out what I am missing.

Thanks for taking the time to answer an easy one.

RobertScheitlin__GISP

Jeff,

Are you looking in the main config.xml?

    <!-- UI elements -->
    <widget left="0" right="0" bottom="0" url="widgets/eSearch/SearchWidgetFixedDG.swf" config="widgets/eSearch/SearchWidgetFixedDG.xml"/>
    <widget left="10"  top="50"    config="widgets/Navigation/NavigationWidget.xml" url="widgets/Navigation/NavigationWidget.swf"/>
    <widget right="-2" bottom="-2" config="widgets/OverviewMap/OverviewMapWidget.xml" url="widgets/OverviewMap/OverviewMapWidget.swf"/>

ARCGIS.jpg

JeffmcGuire

I was not looking at the main config.

I was confused about how several things were working.

Several hours later and I have a slightly better question. 🙂

Currently have some examples working in the floating box, but I haven't been able to make the fixed datagrid with the tabs appear.

I'm sure I am missing something obvious, but I can't find it at the moment.

Included the search config and the main config. Thanks in advance for helping me out. I'm learning a lot.

Attached the whole thing all put together, the code snippets were too long to post.

eSearch.zip

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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