Enhanced-Search-Widget-for-FlexViewer Part III

RobertScheitlin__GISP · ‎04-30-2013

All,

Here is a new thread to post questions and discuss the Enhanched Search Widget. The old thread was getting too long.

RobertScheitlin · ‎01-24-2014

Jeremy,

Can you tell me what version of the widget you are using by holding the Alt key down and click on the widget title. I vaguely remember this issue now and believe I have it fixed in latter releases (not sure which one, but 3.6 version does not show this). The other size issue can be resolved by adding a height and width attribute to the eSearch Widget in the main config.xml.

JeremySmith4 · ‎01-24-2014

Hi Robert,
I believe the widget is the most recent version, 3.6.1.
I will alter the height and width to fix the problem.
Thanks again.

DevonHedemark1 · ‎01-29-2014

Hi Robert,

I previously deployed flex viewer 2.5;the compiled version. In the 2.5 version I used the excellent ESearch widget. We have a parcels feature class (with a relationship class) related to a table of multiple addresses per parcel. The parcel layer is also joined to the address table in the MXD and map service. When I configured the esearch widget at 2.5 to search by PIN (parcel number) in flex 2.5 the esearch widget would return ALL the multiple address records related to the parcel feature class.

Now I am using the new 3.6.1 esearch widget. I have it configured in the same way the 2.5 widget was configured but the new version does not return all the related records. Am I missing something or did the behavior change with the new esearch widget. The interesting thing is that I can seach by address and the results will return any address.

I would be happy to share my xml etc. if needed. How might other organizations handle a PIN search and return all addresses on that parcel?

Thanks for any help you can provide.

Devon

AaronKreag · ‎01-29-2014

Robert-

When we open the tool, the Enhanced Search GUI opens up (screen capture included). Along the top ribbon are three sets of binoculars (the .png image files related to those tools), the text that is associated with each can be edited (ie. Graphical Search or Text Search) in the config file.

However, I have users with a decreased visual acuity and a decreased computer knowledge. I would like to use different images here...like a small house for a property search. It would make it more intuitive and easier to see and distinguish.

Can you comment? Can we change this through a config file path or is this something we need a developer to accomplish?

Thank you for all the great widgets and help on the forums!

RobertScheitlin__GISP · ‎01-29-2014

Devon,

From version 2.5 to 3.6 there has been no functionality removed but there was likely MANY configuration changes. There has been to many versions in between for me to tell you what specifically may have changed. All you would need to do is look at the documentation or one of the examples configurations for the proper configuration.

RobertScheitlin__GISP · ‎01-29-2014

Aaron,

There is nothing in the configuration to enable you to change those portions of the GUI. but this does nt mean that you can not make those changes without recompiling the widget though. All you need to do is replace the i_searchgraphical.png, i_searchtext.png, and i_searchspatial.png with what even image you want they only have to be named the exact same name.

DevonHedemark1 · ‎01-30-2014

Devon,

From version 2.5 to 3.6 there has been no functionality removed but there was likely MANY configuration changes. There has been to many versions in between for me to tell you what specifically may have changed. All you would need to do is look at the documentation or one of the examples configurations for the proper configuration.

Thanks for the reply Robert. I realize my post was fairly ambigous. I will certainly review documentation further. One more attempt here and them back to the documentation.

I am searching against a table PIN field. It is interesting that the standard search widget will return multiple records when there are multiple matching PIN values in the table. But, the ESearch widget configured against the same data only returns one record even if there are multiple matches. Here attached are the two configurations (XML's) if you might have a moment to take a quick look.

Regards, Devon

AaronKreag · ‎01-30-2014

Devon,

This may be a dumb question but how did you do the v.2x to v.3.6 migration? I had an older version running and had to spin up a dev VM, install the newest Flex Viewer app, copy all my old projects from wwwroot to the new flexviewer folder under wwwroot on the new VM, then my 3.6 flex viewer application was able to see all the legacy web maps. I then hit upgrade on each one, some of the tools had to be completely replaced with new stuff. Its been a major time suck. Especially with like 45 web apps running. I would look at that if you have time and haven't already.

My second observation is that after downloading the two xml and looking at it in Notepadd++, you are comparing apples to oranges in my opinion. With 15kb worth of additional text, I am sure there can be a half dozen possibilities with regard to whats causing the error.

Good luck man.

DevonHedemark1 · ‎01-30-2014

Devon,

This may be a dumb question but how did you do the v.2x to v.3.6 migration? I had an older version running and had to spin up a dev VM, install the newest Flex Viewer app, copy all my old projects from wwwroot to the new flexviewer folder under wwwroot on the new VM, then my 3.6 flex viewer application was able to see all the legacy web maps. I then hit upgrade on each one, some of the tools had to be completely replaced with new stuff. Its been a major time suck. Especially with like 45 web apps running. I would look at that if you have time and haven't already.

My second observation is that after downloading the two xml and looking at it in Notepadd++, you are comparing apples to oranges in my opinion. With 15kb worth of additional text, I am sure there can be a half dozen possibilities with regard to whats causing the error.

Good luck man.

I am not using the App Builder. I am using the compiled flex viewer and manually configuring the syntax in the XML's. So, I just downloaded the 3.6 version and begun to configure the 3.6 widgets to acheieve the same functionality at my 2.5 version. I currently only have two web map apps though so it is not too bad. I only have a few widgets deployed: esearch, Street View, Identify, and dynamic legend. Maybe I should start using App Builder moving forward to simplify future upgrades. I have just gotten a little comfortable configuring the compiled version (at 2.5).

Yes, I see your point about apples to oranges. I am not using most of the additional text in the ESearch widget XML. Much of that is commented out or default configuration that came with the 3.6 eSearch widget that I have not touched. I see your point though and should probably start by removing unused text from the esearch XML to assure the additional text is not causing my issue.

Thanks again for the reply.

AaronKreag · ‎01-30-2014

I may be wrong but many of the 2.5 widgets wont work right in 3.6 and vise versa. I think there were many changes to the underlying air/flex/flash/shockwave, ESRI API, etc. The way I understand it all, its not plug and play. By that I mean...Take your existing 2.5 environment, copy compiled 3.6 widgets and put in widget folder and then update the main config.XML. Maybe someone can clarify.

I do NOT use the ArcGIS Viewer for Flex in my production setting. I use it for getting the flex web map up to a certain point and then I move into configuring the main config.xml and the xml configs of the widgets. I also used the 3.6 ArcGIS Viewer for Flex to upgrade/migrate all of my existing webmaps. But again, I did this with copies on a test server and not actually on the web maps that were running. It takes a bit more time but I think its cleaner and leaves less room for error and versions not lining up.

Aaron