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.

Encontre mais publicações marcadas com

Accepted answers

All comments

RobertScheitlin__GISP

Shawn,

So if you are seeing the fixed datagrid then the next question is what is the date modified on the SearchWidgetFixedDG.swf that you are using? If you are using the 3.6.1 version it will have a date modified of 12/19/2013.

Also check to see if when you click a record in the fixed datagrid does is show a sub selection color on the map (i.e. the default is yellow)?

ShawnBowers

Bingo, that was it! I still had the old swfs in that application. I'm now able to select multiple rows but I'm thinking it's not possible to open all related records for the features you have selected. When I hover or click on the related it just opens the related record for that particular feature instead of all of the features I have selected.

I'll have to come up with another solution for that but thanks a lot for the crazy fast help getting me this far!

JeremySmith4

Robert, I am posting photos of the "butter" message along with some other screen shots that I believe are also related to the sizing of the widget box and placement of elements within.[ATTACH=CONFIG]30843[/ATTACH][ATTACH=CONFIG]30844[/ATTACH][ATTACH=CONFIG]30845[/ATTACH]

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

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

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

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!

EnhancedSearchWidgetCapture.PNG

RobertScheitlin__GISP

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

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

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

eSearchWidget.zip

AaronKreag

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

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

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

DevonHedemark1

Aaron,

I believe you are correct about 2.5 widgets not working with a 3.6 viewer. To clarify, I have downloaded the latest 3.6 compiled viewer, configured the main XML to hit our map services, and now am working on downloading and configuring the 3.6 widgets for the 3.6 viewer. I work on the 3.6 viewer configuration on my production GIS server but staff is not hitting the URL to the 3.6 viewer so it is just a separate folder at wwwroot. Our staff uses the 2.5 viewer I have up and running and then when I am done with the 3.6 version I will replace the links that staff hit. I hope that makes sense.

I may look to work with the App Builder. I have been scared to install Adobe AIR and App Builder on my GIS sever in case it causes issues with my production flex viewer 2.5 that I built without app builder. I can take a snap of the GIS server as it is a VM so I will probably bite the bullet and install the App Builder.

Devon

RobertScheitlin__GISP

Devon,
My advice is to completely forget what you had working in 2.5 and just start from scratch. One thing that sticks out to me is you have your fields listed as there is a join on this map service. if there is actually a join on this map service then any where you use a field it has to be the full field name.

i.e.

PIN like '[value]%'

should be:

publish.RDDGIS.PCLCOMP.PIN like '[value]%'

also FULLADDRESS is not even listed in the fields XML...

The titlefield also schould be usinf the full field name.

DevonHedemark1

Devon,
My advice is to completely forget waht you hade working in 2.5 and just sart from scratch. One thing that sticks out to me is you have your fields listed as there is a join on this map service. if there is actually a join on this map service then any where you use a field it has to be the full field name.

i.e.
PIN like '[value]%'
should be:
publish.RDDGIS.PCLCOMP.PIN like '[value]%'
also FULLADDRESS is not even listed in the fields XML...

The titlefield also schould be usinf the full field name.

Hi Robert,

Yes, I will ignore what worked in 2.5 and focus on configuring 3.6. Thanks for the insight.

I have updated the syntax accordingly in my 3.6 esearch and 3.6 search widgets. Here are the updated XML files and a couple screenshots of the results from the Search widget vs. the Esearch widget. BOTH the XML's attached here are from compiled 3.6 widgets. I still get only one result with the Esearch and two results with the search widget for the same PIN search.

Thanks for all your help and any further insight you may have. Devon

esearch_updated.zip

RobertScheitlin__GISP

Devon,

I am not sure if this is it but the more things you have configured incorrectly for the version 3.6 of this widget will add to possible issues. Links do not look the same same way as you have it configured in version 3.6. Links should look something like this now a days:

            <links>
                <link alias="link" disablelinksifnull="true" disableinpopups="false">
                    <![CDATA[{URL}]]>
                    <icon><![CDATA[{Icon_Link}]]></icon>
                </link>
            </links>

If this does not resolve the issue then try just setting the field:

<fields all="true" />

and remove all the other field xml stuff.

DevonHedemark1

Thanks Robert.

I updated the link syntax accordingly and I also specified all fields as you recommended. My link to the assesor map is working which is great. But, I am still only returning one result with the Esearch widget and return two results for the same PIN search with the default 3.6 search widget. I cleaned-up the XML to focus on the PIN search removing all the other configured searches. Here is an updated XML and screenshot.

Thanks again for all the help. Devon

eSearchWidget (2).zip

RobertScheitlin__GISP

Devon,

what is the PIN field type and what is the value that you are entering in both the search and eSearch?

DevonHedemark1

Hi Robert,

The PIN field is string. I have been using the same "test parcel" in both widgets with PIN number 102470018000. I am only typing the numeric value with no quotes or anything else; just 102470018000. I hope this helps.

Regards, Devon

AaronKreag

Robert,

I have a Flex app that has worked fine with Store.gis.ACCOUNTS.prop_id being a String. The following line works great.

<value prompt="Example: 2095 (Numbers Only - Finds All)" isValueRequired="true">Store.gis.ACCOUNTS.prop_id LIKE '%[value]%' </value>

However, I now have a new table in which .prop_id is actually stored as an Integer, length 10. I can not change the database/table but I still need to search the contents of this field like its a string. Is there a way to use something like:

<value prompt="Example: 2095 (Numbers Only - Finds All)" isValueRequired="true"> CAST (Store.gis.ACCOUNTS.prop_id as VARCHAR(10)) LIKE '%[value]%' </value>

Just curious.... Thank you! Aaron

RobertScheitlin__GISP

Aaron,

The rule of thumb that I have figured out is if you cn get the SQL syntax to run in ArcMap then you are LIKELY to get it to use the same syntax on ArcGIS Server through the query task. Now your exact use case... I have not seen this done before.

JuliaGalindo

Hi to all,

I have downloaded the Esearch widget version 3.6.1 and added to the Arcgis viewer for flex application builder without problems (I erased the older one). But, when I compare all layers in the widget with those shown in the online example I am missing some layers, like the Calhoun Parcels. It looks like my application builder is looking to an older Esearch widget.

I have already erase all esearch widgets I could find, I also erased the browser cache (although the application preview is being done in the application builder). Does anyone knows if I am missing something?

Thanks,

NormBushor

Hi All,

I am using the advanced search widget and am getting incorrect results when buffering a feature (parcel), if I buffer at 100 feet the buffer graphic drawn is +-70ft, if I change the units to meters I get the same result, it looks like about 70% of my orginal buffer distance. If I enable graphics and buffer a graphic the buffer distance is fine. I am using Esearch 3.5 with Server 10.1 sp1. All my data is published in WGS 84.

Thanks!
norm

AaronKreag

Julia-

If I understand you correctly....

Its my impression that what you see in the sample/example is exactly that, a sample. If I remember correctly, those are very much like placeholders in the widget. You need to add your own data in the main config and then edit the esearch widget config with your respective data. If that is not the problem, maybe those sample data sets have changed or been edited.

Aaron

JuliaGalindo

Hi Aaron,

Thank you for your reply, yes, I understand what you said, I have to customize the widget. Before doing so, I want to make sure I have the correct widget, because, I need some functionality present in the last widget. I assume, maybe it is a mistake, that, what is available for download is exactly what is present in the online example.
You answer made me go back and review in more detail the Esearch widget download, so I found out that the code I am missing is commented in the eSearchWidget.xml and it can�??t be seen from the inside the application builder (via de widget settings). I will continue to look in that direction�?� to see how to get it work.

Thank again,

Julia-

If I understand you correctly....

Its my impression that what you see in the sample/example is exactly that, a sample. If I remember correctly, those are very much like placeholders in the widget. You need to add your own data in the main config and then edit the esearch widget config with your respective data. If that is not the problem, maybe those sample data sets have changed or been edited.

Aaron

RobertScheitlin__GISP

Norm,

Try setting the spatialreference in the eSearchWidget.xml to this:

<spatialreference>102003</spatialreference>

RobertScheitlin__GISP

Julia,

As you figured out the Calhoun Parcels layer is still in the eSearchWidget.xml Just with a false url as I am not going to publish my map service for every one to play with. Sorry for the confusion.

NormBushor

Robert,
You hit the bullseye again. Thank you!
I'll research that spatial reference to see why the 102100 wasn't working and this one does.
Your hard work on these widgets is highly appreciated!!!
Regards,
norm

JuliaGalindo

Julia,

As you figured out the Calhoun Parcels layer is still in the eSearchWidget.xml Just with a false url as I am not going to publish my map service for every one to play with. Sorry for the confusion.

Thank you Robert!

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

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