Latest Contributions by RhettZufelt

After more testing, it appears as if using dynamic layers in the attribute table is only available for those users running SDE. Or at least, the only way I can get a "dynamic" layer to add it's attribute information to the attribute table is if there is also a matching FeatureServer to go along with the MapServer (even though I only load from MapServer). At least it appears that way.  the only difference I could see in my services that don't work, and the ESRI services that do is the matching FeatureServer for the mapservice.  Once I add a FeatureServer, but still load only the MapServer/ dynamic service, THEN I will get the attribute information in the table. Of course, we avoid SDE like the plague, so I only have it set up for "testing", and my testing says it is required to utilize the attributewidget with dynamic layers (at least with default config, have not tried altering the xml to override this yet). R_ ... View more

So, is there something special about the ESRI service(s) you listed below, as both of them will show up in the attribute table.  Of course, the way you coded it visible="false", one has to actually click the checkbox to turn it on. The first time I turn on the dynamic layer I get this error (twice): TypeError: Error #1009: Cannot access a property or method of a null object reference. at com.esri.ags.components::AttributeTable/updateGraphicCollection() at com.esri.ags.components::AttributeTable/checkForVisibilityAndScale() at com.esri.ags.components::AttributeTable/refresh() at widgets.AttributeTable::AttributeTableWidget/featureLayer_hideShowHandler() at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.core::UIComponent/dispatchEvent() at mx.core::UIComponent/setVisible() at mx.core::UIComponent/set visible() at com.esri.ags.layers::Layer/set visible() at widgets.AttributeTable::AttributeTableWidget/updateFeatureLayersVisibility() at widgets.AttributeTable::AttributeTableWidget/layer_hideShowHandler() at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.core::UIComponent/dispatchEvent() at mx.core::UIComponent/setVisible() at mx.core::UIComponent/set visible() at com.esri.ags.layers::Layer/set visible() at com.esri.viewer.components.toc.tocClasses::TocMapLayerItem/refreshLayer() at com.esri.viewer.components.toc.tocClasses::TocItem/setVisible() at com.esri.viewer.components.toc.tocClasses::TocItem/set visible() at com.esri.viewer.components.toc.tocClasses::TocItemRenderer/onCheckBoxClick() after dismissing/continuing past the error, it seems to load/unload the attributes as you check/un-check the checkbox (as expected) so it appears to actually honor the visible="" from the checkbox.  If I uncheck a layer, it's tab is removed from the attribute table.  If I load as visible="true", then I never get the error, no matter how many times I check/uncheck the box.  With the type="feature" layer, I never get the error, no matter if visible on load or not. However, no matter how I load my services, I only see the attributes if I load them as type="feature", and will NOT show any attributes from a dynamic service.      <operationallayers>             <layer label="311" type="feature" visible="false" alpha="1.0"                                      url="http://sampleserver3.arcgisonline.com/ArcGIS/rest/services/SanFrancisco/311Incidents/FeatureServer/0"/>             <layer label="PoolPermits" type="dynamic" visible="true" alpha="1.0"                                      url="http://sampleserver6.arcgisonline.com/arcgis/rest/services/PoolPermits/MapServer"/> <layer label="WasteSites" type="dynamic" visible="true" alpha="1"   url="http://gis01.wch-rcc.com/ArcGIS/rest/services/Base/All_Waste_Sites2/MapServer"/> <layer label="MRTest" type="feature" visible="true" alpha="0.5"   url="http://gis01.wch-rcc.com/ArcGIS/rest/services/rkz/mrtest/MapServer/0"/>          </operationallayers> In this example the MRTest attributes populate the grid, WasteSites just seems to be ignored (no tab, no data, nothing).  Same thing if I load the MRTest as dynamic. Unfortunatly, my service is not public, but here is how I have it loaded.  Do you see anything I am missing?  This is a AGS 10.05 service, and have also tried with 10.11 service, but no joy. Any ideas? R_ ... View more

Hey Shaun, Just to clarify a bit more, the AttributeTable widget allows you to: a) work with layers added to the map (for feature layers, it directly adds them, for a map service it goes in an find the corresponding featurelayers and adds them) e.g:      <operationallayers>             <layer label="311" type="feature" visible="false" alpha="1.0"                                      url="http://sampleserver3.arcgisonline.com/ArcGIS/rest/services/SanFrancisco/311Incidents/FeatureServer/0"/>             <layer label="PoolPermits" type="dynamic" visible="false" alpha="1.0"                                      url="http://sampleserver6.arcgisonline.com/arcgis/rest/services/PoolPermits/MapServer"/>       </operationallayers> Would add 311 layer and corresponding feature layers(2) from PoolPermits map service. You dont have to do anything in the widget's config for this. Is this really true?  I can see the attributes from any service loaded as type="feature", but I see no attribute information at all with any of the type="dynamic" mapservices using the default attributetablewidget.xml. The only example in the documentaion is for AppBuilder and it has a screenshot allowing you to select which layers to show in the attribute table.  Is this actually modifying the xml to show sublayers, or is the AttributeWidget actually supposed to show them all by default like it does with type="feature"? Thanks, R_ ... View more

Thanks Sarthak, Taking your idea and playing with it some I see that the widgets can be moved above when open or by clicking the widget window IF that widget was in a widgetcontainer that opened after the other widgets.  So, if I move the attribute table to a widgetcontainer that loads first, all other widgets can be moved above/below by clicking. However, I do like the "docked" to the bottom of the page option, and still see no way to make that "table" do anything but overlap on top of everything else. R_ ... View more

So I added this to the ExportWebMapForm.mxml    <esri:exportOptions>     <esri:ExportOptions dpi="{dpiDD.selectedItem}"/>    </esri:exportOptions> also added this: <mx:FormItem id="printDPI"      label="Select DPI"      width="100%"      includeInLayout="true"      visible="true">   <s:DropDownList id="dpiDD" width="100"     labelField="dpi"     selectedIndex="0">    <s:ArrayList>     <fx:Object dpi="96"/>     <fx:Object dpi="266"/>     <fx:Object dpi="300"/>    </s:ArrayList>   </s:DropDownList> </mx:FormItem> This puts the dropdown list for dpi on the print screen and executes with no errors.  However, the new dpi value is not being passed as a parameter.  Anyone know what I am doing wrong and how to make it pass this value as a parameter? Thanks, R_ ... View more

Yes, I can confirm this is still an issue.  It seems like I have to work harder now to make it happen, and only on some of my lines, but it still does. R_ ... View more

Thanks for the information.  However, it doesn't matter how I load it, it still opens above all other widget windows.  even if I open a widget afterwards, it puts it below the attribute table so it can't be seen. I am trying to figure out how to make it open behind other widgets. R_ ... View more

Thanks Dasa, Sorry I didn't get examples posted, been pretty hectic around here. Maybe it's just an issue if you live in Washington 😮 R_ ... View more

I am using 3.0.16 and do not get the error.  However if I delete the titlefield or leave it blank, I ALWAYS get a search return with no values.  So, no error, but no valid search either. I also have this set  <popupsdisabled>true</popupsdisabled> which might be why you get an error and I don't (titlefield is for the popups) R_ ... View more

Don't remember for sure, but if I remember correctly, the issue was if there wasn't symbology set for each layer. You may be able to copy your desired symbology to the bottom of each layer as a work around.    <symbology>     <simplefillsymbol color="0x00FFFF" alpha="0">      <outline color="0x00FFFF" alpha="0.8" width="2" />     </simplefillsymbol>     </symbology>   </layer> R_ ... View more

Actually it is a layout widget.  It opens up a relate table.  I believe it is from a widget created by Robert Scheitlin.  It was written for 3.0 not 3.1 so that is probably why there is a problem now.  Which is okay, I removed it from the config file.  I wont upgrade the Application that uses it until he has the opportunity to update it.  It really is a dormant application right now so I'm in no hurry, he's pretty good about updating all of his widgets. The SearchWidgetFixedDG tag goes in the UI section of the config.xml. Robert has already updated his widgets.  you can get the 3.1 version here: http://www.arcgis.com/home/item.html?id=5d4995ccdb99429185dfd8d8fb2a513e R_ ... View more

Meg,  i can not reproduce this issue, but am using the latest version.  I only have the </symbols> set at the end (no symbology for individual layers) and all my searches produce the same highlight/outline regardless of text or graphic search. Is there a reason you can't update?  Robert has addressed some of the symbology issues with spatial search a couple versions back. R_ ... View more

You might check with your IT folks.  Our "government" network only allows "approved" traffic debuggers as given to me by the IT department. At first, they just captured my info for me, but got tired of it. R_ ... View more

Ed, What you "see" on the map and what the eSearchWidget "select" are completely independent of each other. It appears as if you are drawing all features in the <layer> tag in the map.  When you configure eSearch to only select for regional_command= 'RC-East', it will "select" the matching features in the sublayer defined for that search and allow you to interact (zoom to, popupinfo) with them. If you only want to "see" the features where regional_command= 'RC-East', you would add that to the sublayer definitionexpression in the <layer> tag. http://resources.arcgis.com/en/help/flex-viewer/concepts/index.html#//01m30000000p000000 Another option would be to not have it visible in the map, and have the eSearchWidget assign the same or similar symbology using the <symbology> as described in the eSearchWidget XML configuration.pdf.  This way, only the features that match the current search criteria would be visible, using the symbology assigned to that layer in the esearchwidget.xml layer tag. R_ ... View more