Latest Contributions by RhettZufelt

Robert, while on the subject, I see that there is a geometryserver AND spatialreference set in the eSearchWidget.xml. Was wondering if these should match, or how they "interact" with each other.  Does one override the other or what? R_ ... View more

OK, I had a type in my useutc="true" option in my popupconfig.xml, so now the built in popups report the correct date as well as the esearch widget. Got the format of the date in selectionwidget, but it is still 1 day behind and the export shows the long date.  Will let you know if I find a solution. R_ ... View more

I didn't see anywhere that the date format was being passed from the xml to the swf so I had to add it to get the format to take affect with the selection widget. Interesting about the day off.  If I use the selection widget OR just click on a feature that I have a popupconfig for, the date is one day behind what is in the actual data. Also, if the data is null, it reports 12/31/1969. However, Roberts eSearchWidget reports the correct date. R_ ... View more

It is one of the widgets included with the viewer for flex. http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#/Query_widget/01m30000003m000000/ R_ ... View more

Nice that you figured out that I had symbology set for one of my layers and not the other before I did 😉 Kind of weird with the yellow hightlight.  Like Cory said, no big deal, but I notice if I print with a selection from the esearch or selection (with glow filter removed) widgets, the cyan highlight (I have mine set to cyan) will be yellow on the print. However, if I select one with the popup (click on it), I have the same selection color, but it prints as the same cyan you see in the selection. R_ ... View more

Rhett,    Not sure I understand this??? I have two dynamic services in my map.  One is of wastesites polygons, the other is buildings.  both have uniquvalue render symbology. If I search the wastesite polygon layer, and keep the selection active, it will print just fine. If I search the buildings polygon layer, and keep the selection active, I get the error.  If I close the eSearchwidget, I can then print without the error. Went back to 3.0.13 and do not get the error.  it prints just fine regardless of selections. R_ ... View more

Curious what happens if you have the eSearch select some features from a "different" service. I am using the latest version and can print without issues with a search/selection on one of my services. However, if I try the same thing, but with a selection on a "different" service, I get an error: (not the same error, but still wonder if it is "layer" specific) [RPC Fault faultString="Unable to complete operation." faultCode="400" faultDetail="Error executing tool.: Layer "hiddenLayer_Buildings": Missing 'symbol' in simple renderer. R_ ... View more

Yes, this "old" site seems to work for me.  The eSearch version is: [ATTACH=CONFIG]19559[/ATTACH] R_ Hint:  hold the Alt key and click on the top of the eSearchwidget to get the version information. ... View more

Cory/Robert, It appears as if it is not related to the URL, but rather the selection of the feature. If you open the second map and try to print, you get the error.  however, if you open the second map, then close the esearch widget the selection is removed (the selected item remains in the datagrid, but is no longer "highlighted" on the map), then it will print just fine. R_ ... View more

Seems to be working fine for me. Try making a large change in the <zoomscale> and see if you notice it (I.e., try 5000 and 50). Basically, this is the scale that it zooms/pans INto when you click on a result in the query widget.  Once the "popup" comes up, the "Zoom to" button is part of the popup and does not change with the queryWidget.xml settings and zooms in 1/16th of the current map each time you click it (up to max zoom)and is not part of the QueryWidget. If you are using tiled services, make sure the zoomscale you are setting is between your upper and lower LOD scales or it will not be able to zoom there. Also, if you are already zoomed in, clicking on the result in the Querywidget will pan you to the new selection, but will not zoom "out" so would appear to be not working if you are already zoomed in (I.e., zooms in, but doesn't zoom out). Try dragging your slider all the way down to zoom out as far as possible, then see if you notice the zoom function when you click on a returned feature. R_ ... View more

Really like the add/remove to/from selection option.  A handy feature. I did notice that if you switch to a different layer/table, then the selection is cleared.  Don't even know if it is possible without a huge re-write, but a nifty "enhancement" would be to allow it to add to the selection regardless of which layer/table it is from (I.e., don't clear the selection on layerChanged). R_ ... View more

Nadeem, Using AGS 10.01 I did the following. Loaded a single band raster layer as a basemap and set <excludebasemaps>false</excludebasemaps>. Comment out all layers in eSearchWidget.xml and make onlythese="false" (Even if you say onlythese="false", and you have a layer listed, it will only give you the results in the fields(IE, it still honors the field settings, even if onlythese="false"). So, if I remove all layers info and have it return all with basemaps as such: <layers onlythese="false"> </layers> Then identify a raster layer (singleband), I get the following: [ATTACH=CONFIG]19523[/ATTACH] This is the best way I've found to get the actual "field" names reported back to the identify widget for rasters. If I then copy "exactly" the fields reported from this identify: <layers onlythese="true">   <layer>    <name>All_96_imagery</name>    <fields all="false">     <field name="Pixel Value" alias="Pixel Value from field"  numberformat="2|,|." />               <field name="Pixel value" alias="Pixel value from field"  numberformat="2|,|." />     <field name="Stretched value" alias="Stretched value from field"  numberformat="2|,|." />     <field name="Stretched Value" alias="Stretched Value from field"  numberformat="2|,|." />    </fields>    <links>     <link includeinresults="true" field="" alias="" tooltip="">      <linkprefix></linkprefix>      <linksuffix></linksuffix>      <iconfield></iconfield>      <iconprefix></iconprefix>      <iconsuffix></iconsuffix>     </link>    </links>    <zoomscale>15000</zoomscale>    <forcescale>true</forcescale>   </layer> I get this (note that I have both values with different case to demonstrate how "sensitive" it is. Also, I have noticed that some times it's Value, others it's value (In this service, the case for value is different for Pixel Value, vs Stretched value), so look at what is being returned when you do not have a layer defined to get the actual field name). (the two in red work, the others don't) [ATTACH=CONFIG]19524[/ATTACH] Also, I can't find wkid="29900" in any current ESRI listings, maybe try 29902 (at least if this "is" Irish National Grid). I think 29900 is the old number. Anyway, not sure about the missing widget name, but this works for me on all single band rasters tested (just have to make sure to get the field spelling correct). Of course, once you get it "working", you can set the onlythese="" to whatever you want and it won't affect your returns from this layer. R_ ... View more

Makes sense, though I had not tried it before to know if it was always this way. I was just trying to find ways to re-produce this error. This was one of them (most common seemed to be my syntax of the layer name/fields :o). R_ ... View more

Are you trying to search a table without loading a layer also?  I see the latest version has some errors if there are no layers defined. R_ ... View more

How are you loading the layer with kerneldenisty in the main config.xml?  What type="", visible="", do you have any displaylevels="" or visiblayers="", definitionexpression, or anything like that set for this layer (do you see the raster layer on the map when you click on it, and wkid of map same as this layer(29900))? Also, have you tried making a new ArcMap document with just the kernel density layer and publish as a new service.  Then load that service into the map and try to identify against it?  Might give you an idea if it is an issue with that particular service rather than a config issue. Any chance that you've upgraded from a previous version of the Identify widget without doing a clean on the project or removing/re-adding the (updated) IdendifyWidget.mxml in the modules list? R_ ... View more