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 II

RobertScheitlin__GISP

All,

I am pleased to announce the next release of my eSearch Widget.

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

Version 2.5.1.7 - 4/19/2012
* Added ability to search (flat/standalone/no geometry) tables.
* This time all Zooming uses the same scaling (popup, datagrid, widget results, zoom to all).
* Added Relates icon/button to datagrids so that you can click on it in the datagrid to
open relates choice dialog.
* Move all skins to a skins package for cleaner organization.
* Links that are not associated with a field now work.
* Ability to disable the relates tab in the fixed widget is now configurable.

Find more posts tagged with

Accepted answers

All comments

RobertScheitlin__GISP

All,

Version 3.2.1 is now available.

Version 3.2.1 - 4/1/2013
* Added back the wait cursor that is displayed when a search is executing.
* Added zoom to supports for row clicks in a related table (if the related data
has geometry, both feature to table and table to feature supported).

RobertScheitlin__GISP

Meg,

If I remember correctly I am just using the API's PopUpRendererSkin.mxml. So any changes you make to it should be seen in my widgets popups.

MegPeterson

That's odd. I'm wondering if I missed a 3.0 upgrade to your widget as the mapclick and eSearch popups do not match.

I've copied the PopUpRendererSkin.mxml to a new package (fig 1) and made the edits which dispaly in the mapclick image.
But the eSearch still shows the italics for text.

I'll look back through the posts and see if I missed something, but in general, is this the right process to edit a skin by importing to a new package?

Thanks as always. You're the best tech support out there - Meg

All,

Version 3.2.1 is now available.

Version 3.2.1 - 4/1/2013
* Added back the wait cursor that is displayed when a search is executing.
* Added zoom to supports for row clicks in a related table (if the related data
has geometry, both feature to table and table to feature supported).

If you do a search on a table (no geometry) and want to see the related feature that is linked to (with geometry) on the map, it gives an error message "Invalid or missing input parameters". 😞

It works the other way around though. That is, if you query a layer with a geometry, you can view a related table (without geometry) record for each search result row and you can double click on the related record on the related results datagrid table and it will zoom to the feature. Unfortunately, this does not help in my case 😞

Robert, do you have any plans to look into making the widget work the other way also (i.e. search a non-geometry table and view/zoom to the related selected features). Otherwise I am going to try to convert those non-geometry tables to points and see if that helps to speed up the query and the data load for large counties with 500K parcels.

RobertScheitlin__GISP

Yasar,

Yes I am working on the issue currently and expect to have it fixed soon.

YasarKorkmaz

Yasar,

Yes I am working on the issue currently and expect to have it fixed soon.

That is wonderful 🙂

That encouraged me to ask for another thing about the widget 🙂 Is there a way that we can see all the results' related records in the related results datagrid table instead of viewing one related record at a time from the selection results? Would that perhaps help keeping the original query results intact while still being able to zoom into individual search results from the related results data grid table by double-click?

RobertScheitlin__GISP

Yasar,

You have me pretty confused with that question... Related data is ONLY shown in the datagrid... The only thing that is shown in the widget results is an initial layer or table search results, not relate results.

AndyCowx1

Robert,

I have a numeric field which represents the age of a row (unit is minutes).

Rather than simply displaying the unformatted value, eg 30, 121, 250 is there a way to format the field in the results and in the table such that it would read 00:30, 02:01, 04:10 (HH:MM) ?

Thanks !

Andy

RobertScheitlin__GISP

Andy,

Well that is a pretty unique formatting need. I currently do not have anything that supports that (and likely won't in the future). For the datagrid this is something that could be handled with a label function on a GridColumn. Not sure if you are working with source code or not.

AndyCowx1

Andy,

Well that is a pretty unique formatting need. I currently do not have anything that supports that (and likely won't in the future). For the datagrid this is something that could be handled with a label function on a GridColumn. Not sure if you are working with source code or not.

Robert,

Thanks, I thought it might be a long shot. I'm not working with source so I'll have to stick with the unformatted field.

Andy

YasarKorkmaz

Yasar,

You have me pretty confused with that question... Related data is ONLY shown in the datagrid... The only thing that is shown in the widget results is an initial layer or table search results, not relate results.

I know 🙂 i was trying to catch your attention with a quick response but I immediately noticed that what I sadi did not make any sense. Here is what I was trying to say (within an example):

- A query (a search for all the parcels that are valued more than $10m) on a table that has information about parcels (no geometry) returns 118 results.
- This table is related to a parcel polygon feature layer
- The Search Results shows all the 118 selected records
- To see the related feature for each individual search result record we need to click on the relate icon next to each search result record and only that record's related feature is shown in the relate results datagrid/table (not all 118 related features)

My question was if there was a way to see all the related search results (118 records) on the relate results data grid at once.

Also a way to highlight all the related features on the map just like the search results highlights all the selected records when a feature layer (with geometry) is queried.

I am still not sure if I am explaining it well :-). The overall problem I am having is the excessive amount of information for each parcel that takes forever to load if I join them to the parcel polygon feature and create a new layer with all that attribute info to serve in the web map application. That is why I am trying to serve only parcel polygons without any attribute info (other than the PARCELID that links these records to a table) and serve the table table separately in the map service. This way the idea is to have all the sql queries run on the table but still be able to highlight them on the map.

Another major issue that this relate function can solve is the display issue of condominiums with a single parcel polygon. Think about Miami with all those high rises which has hundreds of condominiums on one parcel. The only way these condominium records can be visualized on a map is mostly via one-to-many relate table between the parcel records and the parcel polygons. That is another main reason I would like to use this tool in this way.

RobertScheitlin__GISP

Yasar,

I think I understand what you are explaining. The bad thing is that this sounds like a programing nightmare for me and how to implement that type of flow with still supporting many to one and one to many relates for both tables and layers... It is making my head hurt just thinking of the logic that would be required.

RobertScheitlin__GISP

All,

Version 3.2.2 - 4/3/2013
* Fixed bug where selection layer would sometimes show in the layer list/Map switcher widgets with some generic name.
* Fixed issue with table to related features relate datagrid row click or other errors.
* Added support for relates to have a zoomscale or zoompercent just like layers.

CharmaleeSandanayake

I am creating a parcel notification app and wondering if there is a way to eliminate some options from the interface, just to make it simpler for less tech savvy users to read. The only layer that a user can search is a parcel layer.

Can I take out the 'Add search tolerance to point selection' option from the menu? I can't seem to make it disappear with the coding.

Also a few options are greyed out but I would like to remove them completely. These include the 'include text query in selection criteria' text as well the first 2 graphical search buttons.

Another thing is that on the Graphical Search tab, the first line of text gets cut off a bit. Not sure how to modify this with the coding.

Please see the attached screenshot for exactly what I mean.

Thanks for any help.

SpatialSearchMenu.jpg

GraphicSearchMenu.jpg

RobertScheitlin__GISP

Charmalee,

Q: Can I take out the 'Add search tolerance to point selection' option from the menu?
A: Currently this is not configurable.

Statement: These include the 'include text query in selection criteria' text as well the first 2 graphical search buttons.
A1: Currently removing the 'include text query in selection criteria' is not configurable.
A2: removing the fist two (now 3 in the latest version) IS configurable:

    <enabledrawgraphicbutton>false</enabledrawgraphicbutton>
    <enablebuffergraphicbutton>false</enablebuffergraphicbutton>
    <enablelocategraphicbutton>false</enablelocategraphicbutton>

Statement: Another thing is that on the Graphical Search tab, the first line of text gets cut off a bit.
Response: I don't see that in your screen shots.

If you are using the source code than all you have to do is add:

 includeInLayout="false" visible="false"

to what ever UI components you don't want to see.

CharmaleeSandanayake

Thanks Robert, that really helps.
I meant the Spatial Search the first line of text, so the top part of the word buffer, gets cut off a very slight bit.

RobertScheitlin__GISP

Charmalee,

OK I see the top of the ff getting cut off in your widget but it is not in mine... Strange.

[ATTACH=CONFIG]23235[/ATTACH]

BTW. I have been considering adding tags to the eSearchWidget.xml for removing more things from the UI, so you can expect to see that change in the future.

Preview.jpg

CharmaleeSandanayake

Thanks for looking into it Robert. I am not very familiar with using the source code, so having the option to remove things from the UI through the esearch tool xml would be a great option.

JayHalligan

Robert, it seems that no matter what, the autosubmit="false" will always immediately display results if you have all other fields set to isvaluerequired="false". How can I create a search that has includes dropdown information and text without auto submitting?

        <expression alias="Database" textsearchlabel="Search Projects:" isvaluerequired="true">
          <values>
            <value prompt="Project Name" isvaluerequired="false">upper(Project_Name) LIKE upper('%[value]%')</value>
            <value prompt="Project Number" isvaluerequired="false">Contract_Number LIKE '%[value]%'</value>
            <value prompt="Detailed Job Type" isvaluerequired="false" userlist="Administration,Geosciences,Geostructural,all" operator="AND" autosubmit="false">Department = '[value]'</value>
          </values>
        </expression>

RobertScheitlin__GISP

Jay,

If you are going to have multiple value tags for one particular expression parent than you need to think of them as you would any SQL statement in ArcMap. For example you first value needs an operator like AND, also each subsequent value needs an operator except for the last value in your values parent.

        <expression alias="Database" textsearchlabel="Search Projects:" isvaluerequired="true">
            <values>
                <value prompt="Project Name" isvaluerequired="false" operator="AND" autosubmit="false">upper(Project_Name) LIKE upper('%[value]%')</value>
                <value prompt="Project Number" isvaluerequired="false" operator="AND" autosubmit="false">Contract_Number LIKE '%[value]%'</value>
                <value prompt="Detailed Job Type" isvaluerequired="false" userlist="Administration,Geosciences,Geostructural,all" autosubmit="false">Department = '[value]'</value>
            </values>
        </expression>

JayHalligan

        <expression alias="Database" textsearchlabel="Search Projects:" isvaluerequired="true">
            <values>
                <value prompt="Project Name" isvaluerequired="false" operator="AND" autosubmit="false">upper(Project_Name) LIKE upper('%[value]%')</value>
                <value prompt="Project Number" isvaluerequired="false" operator="AND" autosubmit="false">Contract_Number LIKE '%[value]%'</value>
                <value prompt="Detailed Job Type" isvaluerequired="false" userlist="Administration,Geosciences,Geostructural,all" autosubmit="false">Department = '[value]'</value>
            </values>
        </expression>

Thanks Robert, but it still seems to autosubmit if I choose from the dropdown list. Is there any way to only submit when the search button is clicked?

RobertScheitlin__GISP

Jay,

are you sure you are using a version that supports the autosubmit attribute? It was introduced in Version 3.1.8 - 2/5/2013.

JayHalligan

Jay,

are you sure you are using a version that supports the autosubmit attribute? It was introduced in Version 3.1.8 - 2/5/2013.

Well what do you know! I never copied the updated version into the project folder. It was driving me nuts! Thanks

SuelyCarrião

Suely,

Searching a related table is supported but it is not currently supported to select the related features in the map for the table that is searched. This enhancement is being looked at though.

Robert! Thanks for your answer , it took me a while to find it back as there are so many posts!
First thanks for the great job with eSearch widget! It does a lot, and helps a lot. It was not the aswer I was looking for but it is an answer ...
Our team will be looking forward to see a new version with this improovement come true!!

Thanks for now

Suely

RobertScheitlin__GISP

Suely,

Actually since I responded to your post I have released a newer version that supports selecting related features on the map from a table.

MikeSmith7

Great Tool, thanks for sharing it. I am trying to select a point in my layer. The url parameter passes fine and the result window pops up and points to the identified result. Is there a way to change the symbology or highlight the selected feature without the need of showing the results window. Sorry if this is already in one of the posts. I have searched for this but have not found it.

Thanks,
Mike

RobertScheitlin__GISP

Mike,

There no real configuration setting for that unless you never what to see the results in the widget then you can disable the result button/view. What you are wanting is not the intent or design of this widget.

MikeVolz

Robert:

The ability to configure the eSearch widget, as Mike above posted, was a user desired requirement for an application that my organization is building. The fact that you can disable the display of the results window is very useful as the results can also be provided from an Identify pop-up window that does not take up as much real estate on the screeen as the results window. As such, thank you for the ability to disable the results window from the config file. Just an excellent widget.

SuelyCarrião

Suely,

Actually since I responded to your post I have released a newer version that supports selecting related features on the map from a table.

That is the answer I was looking for!!!! 😉 rsrs. I saw the new version yesterday and downloaded but could not try the new version yet.

Next week we will receive a consultant on flex programming from "Imagem" (ESRI representative partner in Brazil) to team up with one of our own to convert an application we have build with Flex 3.0, to 3.2 using exclusively Arcgis viewer for flex and widgets available at web. (Having applications version /code dependent are driving us crazy! )

One of the main tools of this application is an "Attribute Search" (over feature's attribute tables and related tables ) highlighting the features (point/polygons) at the map. I would appreciate a lot if you could help us in case of any struggle with this new version, or need to modified some piece of the code. In this case, we would be more than happy to upload the results to be shared with all Flex Viewer community.

Once more thanks a lot!

Suely

RobertHarris1

Robert, thanks for the great esearch widget.
How do you search on a text field that has a - in the middle of it? for example: I am trying to search a text field called VALVEID for valve numbers that are all formatted as follows: xyz-xyz.
Below is a sample that keeps returning a 400 fault code.
<value prompt="Example: 15-015" isvaluerequired="false">upper(VALVEID) LIKE '%[value]%'</value>
<value prompt="Select from the following" uniquevalsfromfield="VALVEID" isvaluerequired="true" autosubmit="true">VALVEID LIKE '%[value]%'</value>

the uniquevalsfromfield displays a list of valve id's, but when I pick one to zoom to I get the 400 fault code.

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.