POST
|
Hi Kenny, Thanks for reporting this. We will have a fix for the next version(3.3). If you are working with un-compiled version of the Viewer, you can look here: https://github.com/Esri/arcgis-viewer-flex https://github.com/Esri/arcgis-viewer-flex/issues/102 Hope that helps.
... View more
04-10-2013
08:57 AM
|
0
|
0
|
165
|
POST
|
Refer to: http://forums.arcgis.com/threads/80970-Flex-3.2-Attribute-Table-field-order-I-thought-this-was-configurable-in-the-XML
... View more
04-01-2013
10:20 AM
|
0
|
0
|
114
|
POST
|
Hey Scott, Thanks for reporting this. I can confirm that this is an issue with the AttributeTable component(in the api). Both the Edit and the AttributeTable widget are doing the right thing and while the AttributeInspector(used by the Edit Widget) works fine, the AttributeTable component does not refresh based on the order. The fix needs to go in the api for this one.
... View more
04-01-2013
10:18 AM
|
0
|
0
|
344
|
POST
|
You set the token property on the IdentifyTask: http://resources.arcgis.com/en/help/flex-api/apiref/com/esri/ags/tasks/BaseTask.html#token Alternatively, you can append the token to the url itself.
... View more
03-25-2013
08:22 AM
|
0
|
0
|
146
|
POST
|
Hey Jason, The reason its not showing anything in the AT widget is because Attribute Table component is not able to create the columns. The Search widget should set the outfields on the (result)feature layer for that to happen, otherwise it just shows the 'displayfield'. My guess is your service does not have a display field set, hence you see nothing. Quick fix for this would be to update the SearchWidget.mxml by adding:
private function createSearchResults(featureSet:FeatureSet, queryFields:XMLList):ArrayCollection
{
var result:ArrayCollection = new ArrayCollection();
var layerDetails:LayerDetails = queryLayer.layerDetails;
if (!queryTitleField)
{
queryTitleField = featureSet.displayFieldName;
}
for each (var graphic:Graphic in featureSet.features)
{
var resultAttributes:ResultAttributes =
ResultAttributes.toResultAttributes(queryFields, textDirection, graphic, featureSet, queryLayer, layerDetails, widgetTitle, queryTitleField, queryLinkField, queryLinkAlias);
var searchResult:ResultItem = new ResultItem(graphic, resultAttributes);
result.addItem(searchResult);
var infoWindowRenderer:ClassFactory = new ClassFactory(PopUpRenderer);
infoWindowRenderer.properties = { popUpInfo: configurePopUpInfo(resultAttributes)};
graphic.infoWindowRenderer = infoWindowRenderer;
}
resultFeatureLayer.outFields = queryLayer.outFields; // for Attribute Table and/or AttributeInspector
resultFeatureLayer.visible = true;
resultFeatureLayer.featureCollection = new FeatureCollection(featureSet, layerDetails);
switch (featureSet.geometryType)
{
case Geometry.MAPPOINT:
{
resultFeatureLayer.renderer = new SimpleRenderer(resultMarkerSymbol);
break;
}
case Geometry.POLYLINE:
{
resultFeatureLayer.renderer = new SimpleRenderer(resultLineSymbol);
break;
}
case Geometry.POLYGON:
{
resultFeatureLayer.renderer = new SimpleRenderer(resultFillSymbol);
break;
}
}
return result;
}
... View more
01-18-2013
10:49 AM
|
0
|
0
|
471
|
POST
|
I've checked the box for "Add results as operational layer", and as expected, the results from a search are shown in the legend, layer list, and a tab is added for the results layer in the attribute table. However, the attribute table is blank with no records or fields. The results in the search widget are visible and there parcels selected. I've attached a screenshot to help illustrating what I'm experiencing. Yes, the search and query widgets were both updated at 3.1 to start using feature layer(s) instead of graphics layer to be able to share results. I tried using the out-of-the-box search widget with the Attribute Table widget working as expected. Would it be possible for you to share the config.xml and the search widget's config. Would be easier to debug.
... View more
01-18-2013
07:24 AM
|
0
|
0
|
600
|
POST
|
Hey Ronald, I am not able to reproduce the issue when using out-of-the-box MapSwitcher widget and TOC component. Here's the excerpt from the config I used(works as expected):
<widget left="0" top="0" config="widgets/HeaderController/HeaderControllerWidget.xml" url="widgets/HeaderController/HeaderControllerWidget.swf"/>
<map wraparound180="true" addarcgisbasemaps="false" initialextent="-13906490 5826218 -13430340 6280858" fullextent="-13906490 5826218 -13430340 6280858" top="40">
<basemaps>
<layer type="tiled" label="Streets" url="http://services.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer" visible="true"/>
<layer type="tiled" label="Topo" url="http://services.arcgisonline.com/ArcGIS/rest/services/World_Topo_Map/MapServer" visible="false"/>
<layer type="tiled" label="Aerial" url="http://services.arcgisonline.com/ArcGIS/rest/services/World_Imagery/MapServer" visible="false"/>
</basemaps>
<operationallayers>
<layer type="dynamic" label="WRIA/WAU" url="http://hammerhead.nwifc.org:8080/ArcGIS/rest/services/Public/WriaWau/MapServer" visible="true"/>
<layer type="dynamic" label="Office Location" url="http://hammerhead.nwifc.org:8080/ArcGIS/rest/services/Public/Office_Location/MapServer" visible="true"/>
<layer type="dynamic" label="County" url="http://hammerhead.nwifc.org:8080/ArcGIS/rest/services/Public/County/MapServer" visible="true"/>
</operationallayers>
</map>
<widgetcontainer layout="float">
<widget label="Map Legend" x="80" y="100" preload="open" icon="assets/images/legend32.png" config="widgets/Legend /LegendWidget.xml" url="widgets/Legend/LegendWidget.swf"/>
</widgetcontainer>
... View more
01-16-2013
08:00 AM
|
0
|
0
|
446
|
POST
|
Uday, Just wanted to confirm if you have looked at: Managing custom widgets From the previous link I mentioned-"Starting with version 3.0, it is possible to add and remove custom widgets from application builder. A dialog box is provided to make adding and removing custom widgets as simple as the click of a button. For more information on adding custom widgets into application builder, see Manage custom widgets."
... View more
01-10-2013
07:43 AM
|
0
|
0
|
816
|
POST
|
You can configure it by adding <showrelatedrecords>true</showrelatedrecords> to the popup config.
... View more
01-09-2013
10:41 AM
|
0
|
0
|
168
|
POST
|
Have you looked at this: Packaging Custom Widgets for Application Builder Also, please post Viewer/Builder related questions under: http://forums.arcgis.com/forums/111-ArcGIS-Viewer-for-Flex
... View more
01-09-2013
08:53 AM
|
0
|
0
|
816
|
POST
|
Right now there isn't a way to do that per layer. Its all or none as it applies to the Editor component. The only solution that I can think of right now is that if you are using a 10.1 service, you can publish it in a way where geometry updates are disabled. See: http://resources.arcgis.com/en/help/main/10.1/index.html#//015400000393000000
... View more
01-09-2013
08:44 AM
|
0
|
0
|
363
|
POST
|
You can set <updategeometry> to false in Edit widget's config:
<?xml version="1.0" ?>
<!-- If compiling this widget, make sure to add -keep-all-type-selectors=true to your compiler arguments in the FB project properties. -->
<configuration>
<createoptions>
<polygondrawtools>polygon,freehandpolygon,extent,autocomplete</polygondrawtools>
<polylinedrawtools>polyline,freehandpolyline,line</polylinedrawtools>
</createoptions>
<addfeatures>true</addfeatures>
<deletefeatures>true</deletefeatures>
<toolbarvisible>true</toolbarvisible>
<toolbarcutvisible>false</toolbarcutvisible>
<toolbarmergevisible>false</toolbarmergevisible>
<toolbarreshapevisible>false</toolbarreshapevisible>
<updategeometry>false</updategeometry>
<updateattributes>true</updateattributes>
</configuration>
... View more
01-09-2013
06:44 AM
|
0
|
0
|
363
|
POST
|
Hey Jason, I noticed that this is an issue with the Edit Widget where the <formfieldsorder> is not being honored. Having looked at it in more detail and to be consistent with other widgets, i think it would make sense that if the fields are being specified explicitly in a certain order in the config, then there is no need to specify <formfieldsorder> as it would be redundant. Here's the fix (if you are using the uncompiled version) for the EditWidget.mxml, replace the attributeInspector_showFeatureHandler() method with: private function attributeInspector_showFeatureHandler(event:AttributeInspectorEvent):void { attachmentInspector.addEnabled = editor.attributeInspector.updateEnabled; attachmentInspector.deleteEnabled = editor.attributeInspector.deleteButtonVisible; const featureLayer:FeatureLayer = event.featureLayer; var settingsKey:String = featureLayer.name; if (featureLayer.name.indexOf("hiddenLayer_") != -1) { settingsKey = hiddenFeatureLayerToSettingsName[featureLayer]; if (!settingsKey) { settingsKey = featureLayerToDynamicMapService[featureLayer].name + "/" + featureLayer.url.substring(featureLayer.url.lastIndexOf("/") + 1, featureLayer.url.length); hiddenFeatureLayerToSettingsName[featureLayer] = settingsKey; } } var settingsObject:Object = layerToSettings[settingsKey]; if (settingsObject) { var outFields:Array = settingsObject.outFields as Array; if (outFields && outFields.length) { var attributeInspectorFieldInspectors:Array = []; var fieldInspector:FieldInspector; for each (var fieldObject:Object in outFields) { fieldInspector = new FieldInspector; fieldInspector.featureLayer = featureLayer; fieldInspector.visible = true; fieldInspector.fieldName = fieldObject.name; fieldInspector.label = fieldObject.alias; fieldInspector.toolTip = fieldObject.tooltip; attributeInspectorFieldInspectors.push(fieldInspector); } for each (var field:Field in featureLayer.layerDetails.fields) { if (outFields.indexOf(field.name) == -1) { fieldInspector = new FieldInspector; fieldInspector.featureLayer = featureLayer; fieldInspector.visible = false; fieldInspector.fieldName = field.name; attributeInspectorFieldInspectors.push(fieldInspector); } } editor.attributeInspector.fieldInspectors = attributeInspectorFieldInspectors; editor.attributeInspector.formFieldsOrder = AttributeInspector.FIELD_INSPECTOR_ORDER; } else { var formFieldsOrder:String = settingsObject.formFieldsOrder; if (formFieldsOrder) { editor.attributeInspector.formFieldsOrder = formFieldsOrder; } } var singleToMultilineThreshold:Number = settingsObject.singleToMultilineThreshold; if (singleToMultilineThreshold && !isNaN(singleToMultilineThreshold)) { editor.attributeInspector.singleToMultilineThreshold = singleToMultilineThreshold; } var showObjectID:String = settingsObject.showObjectID; if (showObjectID) { editor.attributeInspector.showObjectID = showObjectID == "true"; } var showGlobalID:String = settingsObject.showGlobalID; if (showGlobalID) { editor.attributeInspector.showGlobalID = showGlobalID == "true"; } } } You would not have to set the <formfieldsorder> anymore with this update.
... View more
01-08-2013
02:33 PM
|
0
|
0
|
783
|
POST
|
Yes. There's another way, where if you have the Edit widget open alongside, it gives the capability of clicking on a feature and selecting it.
... View more
01-08-2013
09:39 AM
|
0
|
0
|
363
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|