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.

[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.

[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.

[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>