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; } } }

eSearch popup vs. MapClick popup

MegPeterson

Hi all - I need a better understanding on what's going on behind the scenes with the eSearch tool and a map click.

I have the eSearch widget loaded and displaying the fields and thumbnails I need once records are selected (see attached search_popup.jpg).

But when I click on the same selected point, the point is selected and the popup displays honoring the fields I set in the eSearch.xml, but without the attachments (mapclick_popup.jpg).

I'm trying to figure out how to show the attachments with a mapclick as well, but more importantly, understand where in the code the map click is firing from.

thanks -

mapclick_popup.JPG

search_popup.JPG

BLM_CO_Collector_Domains.xlsx

BLM_CO_Collector_Relationship_Classes.xlsx

TonghuiMing_0-1653472813777.png

NovicaJ_0-1653470283753.png

Vind meer berichten getagd met

Accepted answers

All comments

Anonymous User

Original User: mscavallaro

Marc,

The close button you have indicated in your graphic comes from the ContentNavigator component. I don't do anything with the PopUpRendererSkin.mxml in my eSearch any more. I let esri handle all of it.

Robert, I had a feeling that was the case, I'll just have to disable it. Thanks for your quick reply.

-Marc

RobertScheitlin__GISP

Marc,

The close button you have indicated in your graphic comes from the ContentNavigator component. I don't do anything with the PopUpRendererSkin.mxml in my eSearch any more. I let esri handle all of it.

Anonymous User

Original User: mscavallaro

Hi Robert, I'm having a similar issue, however I cannot up grade to your latest version due to the many changes that I've incorporated. My issue is with the popup that is produced when clicking on a result graphic. For some reason it's displaying two close buttons and a title bar. I want to remove the title bar and the plain X close button. I've tried editing the InfoWindowSkin with no luck. Do you have any suggestions?

[ATTACH=CONFIG]20958[/ATTACH]

Thanks,
Marc

1-22-2013 9-20-24 AM.png

Clip_55.jpg

RobertScheitlin__GISP

next version 3.0.14 is now available.

Version 3.0.14 - 11/14/2012
* Fixed bug where if more than one uniquevalsfromfield was used in an expression
Only one would populate the dropdown.
* uniquevalsfromfield now are aware of isrequired attribute and add a blank entry
in the drop down if necessary.
* Added delay for mouseover in datagrids to allow user to exit datagrid and choose
a button from the popup
* The popup shown from the search results and datagrid is the same popup that gets
displayed when you click on the search graphic on the map.
* Added the ability to add and remove from current selection as well as create a new
selection (which is the default).
* Fix bug where individual layers symbology specified in the eSearchWidget.xml was
not being used with certain spatial searches.
* Added support for disabling search widget results (just use <disablebuttons>result</disablebuttons>).
* Added support for disabling popups completely for this widget.

Anonymous User

Original User: rscheitlin

Meg,

Actually I did understand that. I will add it to my list.

MegPeterson

Hi Rhett/Robert - thanks for the responses.

Didn't have it backwards but didn't employ your suggestion and I'm really liking how it's all coming together. (Until it all changes again....that is!). Thanks for the help.

Eeks - Rhett - I meant DIDemploy your suggestions and I'm liking how it's coming together...!

Robert - my head hurts

. Thanks for the update.

FYI: one thing I noticed with the fixed datagrid is if I'm hovering and click on row #3 in the table for example, and then try to open the attachment for that record in the popup, I can't get to that popup record because right when I move my mouse over the records above #3, it dynamically opens up the other row popus? Clear as mud?

Thanks again to you both.

Anonymous User

Original User: rscheitlin

Meg,

Yep as you mentioned until it changes again... Well based on this thread I have dug into the issue and it is fixed in version 3.0.14 coming out soon. There will be no difference between the popup when you click on the result graphic in the map or the popup you get when you click the search result/datagrid, they will both have attachments. And a couple of other fixes and enhancements as well. Then get ready for it because Flex Viewer 3.1 is projected to be out in December and the API team has made big changes with relates and a built in feature attribute widget that may seriously change this widget.

MegPeterson

Hi Rhett/Robert - thanks for the responses.

Didn't have it backwards but didn't employ your suggestion and I'm really liking how it's all coming together. (Until it all changes again....that is!). Thanks for the help.

Anonymous User

Original User: rzufelt

Meg, are you sure you don't have that just backwards?

You photo's look like mine did before I disabled the popup feature of eSearch, (however, my "mapclick" looks like your search, and vice versa).

Do you have a src/popups/layerconfig.xml file for that layer also? it looks like it is pulling one popup from the eSearch and one from the popup.xml file.

I just disabled the popups from eSearch and set a popup.xml file for my layer includeing <showattachments>true</showattachments>. This makes my "built in" popup look just like the on you show as search.jpg with all the fields I set in the popupconfig.xml AND all the attachemts show just like in your search_popup.jpg (at least with FV 3.0).

R_

RobertScheitlin__GISP

Meg,

The issue is that when you click on one of my results in the widget or the datagrid I am able to set the PopUpRendererSkin to my custom one in the eSearch and thus that the ability to show attachments using the search graphics due to some custom extending of esri components I have done. When you click on the graphic in the map esri handles many things inside their code (unexposed) and thus I can not force it to use my extended component (so far). Hope this explains the difference you are seeing.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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