Latest Contributions by HeatherGonzago

Hi Brian, We definitely want to figure this out in case it was a bug introduced at 3.1. In order to do this though, the best route is to contact our Tech Support group as they can take the right steps to get everything documented and in the system. You can contact them directly at http://support.esri.com/en/ or by calling 888-377-4575. Thanks. ... View more

Take a look at what JC wrote in this post. Would this apply to your situation? http://forums.arcgis.com/threads/73768-Searchbox-in-3.1?p=262795&viewfull=1#post262795 ... View more

Also, for the results displaying incorrectly. Please take a look at what I replied in this thread, http://forums.arcgis.com/threads/73768-Searchbox-in-3.1?p=262305&posted=1#post262305. ... View more

By any chance, is your application public? It may be easier if I could take a look. If not, let me take the info you already provided and see if there is anything else going on. ... View more

Hi everyone, We got the same issue that you described above and after a lot of testing it appears the issue is related to how the geocoding locator service is set up. The application expects 'optional' result extent coordinates (Geographic), which will fail if a custom Geocoder does not have set since it will erroneously create an extent at 0,0. When creating a locator, the optional result extent coordinates are not automatically set. More on this is written in the help at http://resources.arcgis.com/en/help/main/10.1/index.html#//00250000004n000000, under Return display extent output fields. The easiest way I found was to go into your locator's (not the service) properties > and there is an outputs option > click on "return display extent output fields" set to yes, by default it's no. > rebuild the locator > republish the service. [ATTACH=CONFIG]20604[/ATTACH] You should not get the result off of Africa anymore. We are updating the fix but for now, please use this as a workaround. ... View more

So the problem seems to stem from only the popups? Is it that when you initially load the map, nothing displays and then after refreshing it does display correctly? If you disable the popups, does it display correctly the first time around? Did any of the data within the map change between 3 and 3.1? Meaning, did the indexes of the layers referenced for the popups get altered at all? I know, easy enough but thought it would be a good thing to check on that as well. ... View more

The default height and width of the dialog changed from 500 to 300 which is probably giving you the results you are seeing as well. This can be configured in the tag using both height and width tags. http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Splash_widget_tags/01m300000005000000/ ... View more

We will definitely take this into consideration as it does appear that others besides yourself have asked for this functionality. Thanks for suggestions. ... View more

Currently working with dynamic workspace functionality (adding layers on the fly, dynamic rendering, etc.) can be done via the API. This is doc'd at http://resources.arcgis.com/en/help/flex-api/concepts/index.html#//017p0000002p000000. Functionality for this behavior is currently not available directly using OOTB Viewer. You would need to create a custom widget that implements this. Bjorn and I showed this in last year's Dev Summit in addition to Lloyd and Bjorn showed it at last year's UC. These demos were specific for rendering but you could take that same premise using samples in the API (under the what's new section) and write it into your own custom widget. This is something that is being considered for a future release of Viewer. http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#//01m300000020000000 - developing in viewer concepts http://resources.arcgis.com/en/help/flex-api/samples/index.html#//01nq0000006m000000 - API samples http://proceedings.esri.com/library/userconf/devsummit12/index.html - dev summit proceedings, search for configuring customizing flex viewer http://proceedings.esri.com/library/userconf/proc12/tech-workshops.html- ArcGIS Viewer for Flex-Advanced Topics ... View more

The default height and width of the Splash dialog has changed from 500 to 300. You can update the size of the dialog using link > content > height and width tags for the Header Control widget.  And Width and Height tags for the Splash widget config. See if you can change this back to 500? Do you still get the same issue? http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Header_Controller_widget_tags/01m30000000n000000/ http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Splash_widget_tags/01m300000005000000/ ... View more

Hi everyone, Just a little clarification to help ease any confusion. The Search Header is currently designed to work to always use the geocoding locator service, whether you specify the default or one of your own. If you do choose to work with your own layers as well and add the <searchlayers> tag, it will use both the locator AND the layers you specify. The documentation has been updated to reflect this as to hopefully avoid anymore confusion. http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Header_Controller_widget_tags/01m30000000n000000/ http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Header_Controller_widget/01m30000003s000000/ Thanks for all your patience, and enjoy the new functionality:-) ... View more

Thanks for all your testing. We are actively looking at this and will respond ASAP. Thanks for your patience. -Heather ... View more

Using App Builder 3.1 with a map that is not either in geographic or web mercator is a known issue. It'll be fixed in the next release. To get around the issue you need to open the config.xml that gets generated from App Builder and set the wraparound180 attribute to false. There is no way currently to do this directly using App Builder as you can by modifying configuration files. ... View more

I really like the idea of the new searchbox in the HeaderControllerWidget, but I'm not able to configuring it as I want. Don't know if I'm doing it wrong or if it's impossible without changing the source code. I want to use my own searchlayers and no locator at all, and I want the results to display as graphics. First of all I think the conceptual graphic in the documentation is wrong, it looks like the <labels> tag and <symbols> tag is supposed to be in the <searchlayer> tag, but in the text it says they should be in the <search> tag which seems to be correct. My config-file looks like this (the search tag): <search>         <searchlayers>             <searchlayer>                 <url>http://oskar75:6080/arcgis/rest/services/test/Sokning/MapServer</url>                 <layerids>0,1,2</layerids>                 <searchfields>FASTIGHET,ADRESS,TEXT</searchfields>             </searchlayer>                  </searchlayers> <zoomscale>5000</zoomscale> <labels>   <searchprompt>Skriv fastighet, adress eller plats</searchprompt>   <noresults>Inga träffar hittades</noresults>   <searchresulttitle>Sökträff</searchresulttitle>   <clearfeaturelabel>Rensa</clearfeaturelabel> </labels> <symbols>   <simplemarkersymbol color="0x00FFFF" alpha="0.7" size="10"/>   <simplefillsymbol color="0x00FFFF" alpha="0.5">    <outline alpha="0.9" width="2"/>   </simplefillsymbol> </symbols> </search> The search works fine for my three layer ids but also displays searchresult from what I guess is the default locator. Is there anyway to disable that? I don't see any graphics to my results though, is something wrong with my <symbols> tag? (My layers are one polygon layer and two point layers). My last wish I think would require editing the source code (maybe something for the next version?), I would like the resultlist to display and update while typing, without pressing enter, after the users has entered a number of characters (for example 4 or 5). Good catch! You are correct, the labels and symbols are not in the correct location in the graphic. We will update that ASAP. Please refer to what is referenced in the text. As for using ONLY searchlayers and not the default geocode locator as well... this should be working like that already. I do see what you are referring to. When putting in ONLY searchlayers I am getting requests made to both the layers in addition to the geocode locator. There was another post regarding the default locator always being used so I'm thinking there may be more to all of this. We'll look into it and see what may be causing the problem and get back to you ASAP. Thanks. ... View more