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.

[MichaelVolz]

Would it be possible to move your app to FlexViewer v3.3 and see if the relate works properly there?

[BoCastillo]

Robert,

One final question from and then I think I'm finished customizing and testing the eSearch widget for us!

Is it possible to change the the "Hyperlink" text in the fixed datagrid to be a different color, bold, etc.?

Thanks,
Bo

[Corbinde_Bruin]

I think I figured out my issue. When I relate to a table from a feature class, clicking on the highlighted record of the related table results in the datagrid gives me a "Missing or Invalid Parameters" error. My guess is, clicking on related records in the datagrid attempts to zoom to the record. Table records have no shape fields and cannot be zoomed to. Can I get any confirmation that this may be an issue?
Is there a way around this. Am I going about my 'FeatureClass to Table' relate all wrong?

I see this error message in versions 3.2.1, 3.2.2, & 3.3.3 of eSearch, and the respective viewer versions.

Thank you for your time,
Corbin de Bruin

[MichaelVolz]

I have a related table setup with a feature class in my flexviewer, but nothing occurs if I click on the related record in the datagrid.  I thought this was expected behavior and the flexviewer app does not zoom to related records.  I thought you could only zoom to records selected in the main datagrid.  Someone please correct me if I am wrong.

[daveespinosa-aguilar]

Dave,

   Are the shape and objectid fields visible in your data or do you have them hidden when you published the service? I honestly have no experience with database views working in my widget so you might be the first...(and it might not work with them).

the shape and objectid fields are not visible and are hidden. if it doesn't work with database views it is still a very useful and powerful tool for us. thanks so much for taking time to develop it.

[PatrickMcGarry]

I have an issue with eSearchWidget that I can't seem to resolve. I am running the latest version of the widget 3.3.3,
the latest source code for flexviewer 3.3.

Recently some data sources in my organisation were upgraded from shapefiles to feature classes. With the feature classes, fields for Shape_Length and Shape_Area are created by default.

I want to display these length and area fields in the results of a text search, however they don't appear in the results despite inclusion in the fields block (example below). All other defined fields appear as expected.

<fields all="false">
                <field name="Shape_Length" alias="Perimeter" />
                <field name="Shape_Area" alias="Area sq m" />
</fields>


I have defined these fields in the identify widget (using identical field tags), where they successfully returned the length and area values,  indicating there isn't an issue with the service returning the information.

All of my fields are on and aliases are off on this service, so it's not an issue of the geometry being hidden.

There seems to be some handling of the Shape Length and Area fields in the eSearchWidget mxml around line 3604. Though
to my knowledge this seems to deal with the case when the fieldName.toUpperCase function isn't equal to Shape_Length or Shape_Area.

Any advice would be greatly appreicated.  

Thanks,

Damien Robinson
(i'm using my boss's esri account)

[MicahVan_Maanen]

I have a minor issue with version 3.1.12 of this widget.  My REALLY old version would highlight the search results on the map and I can't seem to find the configuration setting to enable this functionality on the newer version.

If you go here:
http://pol.siouxcounty.org/flex/ and then do a name search for Jong it will show the results in red on the map.

If you go here:
http://pol.siouxcounty.org/flex3/ and do the same search it doesn't show in red on the map.

Thanks for any assistance.

[RhettZufelt]

I noticed that in your newer app, that when you click on a result, and it zooms to it, it also highlights it red. 

In the older widget, it would automatically zoom to the results, the new one, that is a setting that you have set to false  <autozoomtoresults>.

Not sure, but perhaps if you have it zoom to the results, it would hightlight them all as it does when you click/zoom to individual results?

Just a thought,

R_

[MicahVan_Maanen]

Thanks for the reply.  The issue that I am having is that on the old version it shows all of the results in red before clicking any of the results.

[RhettZufelt]

Of course, your crossdomain doesn't let me search against your layer to see if there are issues with it, but I have set mine up similar and have no issues.

however, I am running one verison newer than you are, I am running 3.1.13 and is working just like the "old" one.  IOW, it highlights all returned results, regardless of being sent to the float or fixed.

Also, disregard my previous post, as this setting seems to have no effect on that.  Still highlights all of the returned result if true or false, just doesn't soom to the extent of selected results if false.

R_

Just further info.  I removed the 3.1.13 and loaded 3.1.12 and still seems to be selecting all returned results....  Have you made any customizations to the FV3 app?