Edit Widget 3.1

[JasonNielsen]

Ok i've been working on this for awhile and can never seem to get the edit widget to do what i would like it to. In the tag reference it talks about using the <formfieldsorder> you can pick from "fields, alphabetical, fieldinspector". I have a specific order i'm trying to get and i cant seem to get it to do it. 

for example i have 5 attributes and i want them in the order of: TYPE, DESCRIPTION, STATUS, START_DATE, END_DATE. The following is a copy from my EditWidget.xml.

<?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>true</toolbarcutvisible>  <toolbarmergevisible>true</toolbarmergevisible>  <toolbarreshapevisible>true</toolbarreshapevisible>  <updategeometry>true</updategeometry>  <updateattributes>true</updateattributes>   <layersettings>    <layer name="Active Incident Areas">    <fields>     <field name="TYPE" alias="Type" />     <field name="DESCRIPTION" alias="Description" />     <field name="STATUS" alias="Status" />     <field name="START_DATE" alias="Start" />     <field name="END_DATE" alias="End" />     </fields>    <showobjectid>false</showobjectid>    <showglobalid>false</showglobalid>    <singletomultilinethreshold>60</singletomultilinethreshold>    <formfieldsorder>fields</formfieldsorder>   </layer>  </layersettings>  </configuration>

I've made sure that the name of the Layer is the name of the layer in the main config xml file. Also the service is a type of feature. attached is what is returned.

[ATTACH=CONFIG]20549[/ATTACH]

Which is the order they show up in the MXD i have. I've tried moving them around in the mxd and republish the service but they remain in the same order on the website. 

I've tried clear all cache and temporary files to see if that was the issue but still no luck. Anybody have any othre sugguestions i could try?

thanks.

[SarthakDatt · Accepted solution]

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.

[JasonNielsen]

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.

Thank you very much for letting me know about this. It took care of my issues and i can move on to something else now.

[JustinFultz]

I have this same issue with the attribute table widget. I cannot get the field order for the widget to be honored.

Any suggestions for correcting this? The AttributeTableWidget.mxml doesn't include the same code to be replaced as the edit widget.

[BjornSvensson]

I have this same issue with the attribute table widget. I cannot get the field order for the widget to be honored.

Justin, this has already been fixed for the next release - see https://github.com/Esri/arcgis-viewer-flex/issues/23 which has the link to the actual code changes (if you are compiling it yourself).

[JustinFultz]

I replaced my AttributeTableWidget.mxml with the one on githut and now the fields are sorted alphabetically. Is there a tag or something that I am missing that needs to be added?

[MehulChoksey]

There were couple of changes made to the attribute table widget with regards to ordering.in upcoming release of 3.2. (The source code is available on git.)


  1.       The columnsorder tag now needs to be specified in the layer tag.

  2.       If the fields are specified in the layer tag of the attribute table, then   Attribute table shows the fields in that order.

  3.       The default is the order of fields on the server side.
  Sample config for the attribute table:
  Here Incidents is the layer specie in the main config.
 
 

<?xml version="1.0" ?>

  <configuration>
  <layersettings>

                  <layer name="Incidents" >
                                  <columnsorder>alphabetical</columnsorder>

                  </layer>

  </layersettings>

   

  </configuration>

 


Hope this helps

[JustinFultz]

If I don't specify fields, the behavior is as expected(the order of the fields in SDE). If I do specify fields, they show up in alphabetical order, no matter what the <columnsorder> tag specifies. Is it possible that this was tested with a field list that was in alphabetical order already so this bug wasn't noticed, or am I still missing something?

I've included my config file:

<?xml version="1.0" ?>
<configuration>
 <layersettings>
  <layer name="Delivery Point Additions">
   <columnsorder>fields</columnsorder>
   <fields>    
    <field name="DP_REQUEST_ID" alias="Request ID" visible="true"/>
          <field name="REQ_DATE_STR" alias="Request Date" visible="true"/>
          <field name="DP_NAM" alias="Name" visible="true"/>
          <field name="BUS_A" alias="Bus A" visible="true"/>
          <field name="BUS_B" alias="Bus B" visible="true"/>
          <field name="AQ_PROCESS_STATUS" alias="AQ Process Status" visible="true"/>
          <field name="TRANSMISSION_OWNER" alias="TO" visible="true"/>
          <field name="CUSTOMER" alias="Customer" visible="true"/>
          <field name="ASS_DUE_DATE_STR" alias="Assessment Due Date"/>
          <field name="ASS_COMP_DATE_STR" alias="Assessment Complete Date" visible="true"/>
          <field name="DPNS_STUDY_REQ" alias="DPNS Study Required" visible="true"/>
          <field name="DPNS_AGRMT_SENT_DATE_STR" alias="DPNS Agreement Sent Date" visible="true"/>
          <field name="DPNS_AGRMT_DUE_DATE_STR" alias="DPNS Agreement Due Date" visible="true"/>
             <field name="DPNS_AGRMT_RECIEVED_DATE_STR" alias="DPNS Agreement Recieved Date" visible="true"/>
             <field name="DEPOSIT_RECIEVED_DATE_STR" alias="Deposit Recieved Date" visible="true"/>
             <field name="DPNS_STUDY_DUE_DATE_STR" alias="DPNS Study Due Date" visible="true"/>
          <field name="DPNS_STUDY_FINISH_DATE_STR" alias="DPNS Study Finish Date" visible="true"/>
          <field name="NITSA_EXECUTION_DATE_STR" alias="NITSA Execution Date" visible="true"/>
          <field name="UPGRADE_ID" alias="Upgrade ID" visible="true"/>
          <field name="NTC_ID" alias="NTC ID" visible="true"/>
          <field name="VOLTAGE" alias="Voltage(kV)" visible="true"/>
          <field name="LOAD_MIN" alias="Load Min(MW)" visible="true"/>
          <field name="LOAD_MAX" alias="Load Max(MW)" visible="true"/>
          <field name="NOTES" alias="Notes" visible="true"/>
   </fields>
   <showobjectid>false</showobjectid>
   <showglobalid>false</showglobalid>
   <exportlocation>false</exportlocation>
   <showattachments>false</showattachments>
   <showrelatedrecords>false</showrelatedrecords>             
  </layer>
 </layersettings>
</configuration>

[ScottMcGee]

There were couple of changes made to the attribute table widget with regards to ordering.in upcoming release of 3.2. (The source code is available on git.)


  1.       The columnsorder tag now needs to be specified in the layer tag.

  2.       If the fields are specified in the layer tag of the attribute table, then   Attribute table shows the fields in that order.

  3.       The default is the order of fields on the server side.
  Sample config for the attribute table:
  Here Incidents is the layer specie in the main config.
 
 

<?xml version="1.0" ?>

  <configuration>
  <layersettings>

                  <layer name="Incidents" >
                                  <columnsorder>alphabetical</columnsorder>

                  </layer>

  </layersettings>

  

  </configuration>

 


Hope this helps

Note to ESRI:

The above (posted by an ESRI employee) does not work with the Flex 3.2 AttributeTable widget.

I have spent three days trying to get the fields in the attribute table to be shown in the same order as I have them listed in my AttributeTableWidget.xml file. I have tried numerous things and NOTHING has any effect at all on the ordering of fields in the attribute table. The fields always show in alphabetical order. Here's what I've tried:

1) <columnsorder>fields</columnsorder>
2) <columnsorder>fieldinspector</columnsorder>
3) <columnsorder>alphabetical</columnsorder>
4) Not specifying the <columnsorder>
5) Put the <columnsorder> tag in every conceivable location in the XML file
6) Tried <columnorder> (singular) instead of <columnsorder> (plural)
7) After every trial, I clear my browser's entire history and cache, close it, restart it, and clear the cache and history a second time.

Here's the code from my AttributeTableWidget.xml file:

<?xml version="1.0" ?>
<configuration>
     <layersettings>
        <layer name="Surface USFWS"> <!-- type="feature" -->
            <columnsorder>fields</columnsorder>
            <fields>
                <field name="Refuge" alias="Refuge Name"/>
                <field name="NWR_Unit" alias="NWR Unit"/>
                <field name="LRS_Tract" alias="LRS Tract"/>
                <field name="OTYP" alias="Owner Code"/>
                <field name="OWNTYP" alias="Owner Type"/>
                <field name="Casetype" alias="Case Type"/>
                <field name="Surstat" alias="Surface Status"/>
                <field name="Serial_full" alias="Full Serial No."/>
                <field name="Cvyno" alias="Conveyance No."/>
                <field name="Cvydate" alias="Conveyance Date"/>
                <field name="Acres_LGL" alias="Acres (Legal)"/>
                <field name="Acres_GIS" alias="Acres (GIS)"/>
                <field name="USS" alias="USS No."/>
                <field name="Lot" alias="Lot No."/>
                <field name="Block" alias="Block No."/>
                <field name="Survey_Tract" alias="Survey Tract"/>
                <field name="Notes" alias="Notes"/>
            </fields>
        </layer>
    </layersettings>
</configuration>

And here's the relevant code from my config.xml file:

    <map attributionvisible="true" esrilogovisible="true" openhandcursorvisible="false" scalebarvisible="true" scalebar="default" zoomslidervisible="false" wraparound180="true" addarcgisbasemaps="true" initialextent="-17927341.877726927 10083228.80475048 -17862599.714769468 10119918.578327317" wkid="102100" top="40" portalurl="https://www.arcgis.com">
        <basemaps>
            <layer type="tiled" label="Topographic" icon="https://www.arcgis.com/sharing/rest/content/items/6e03e8c26aad4b9c92a87c1063ddb0e3/info/thumbnail/topo_map_2.jpg" url="http://services.arcgisonline.com/ArcGIS/rest/services/World_Topo_Map/MapServer" visible="true"/>
        </basemaps>
        <operationallayers>
            <layer type="feature" label="Surface USFWS" url="http://myserver/arcgis/rest/services/Land_Status_Mapper/Land_Status/FeatureServer/0" mode="onDemand" visible="true"/>
        </operationallayers>
    </map>

ESRI says that the <columnsorder> tag is required. But logically, that makes no sense. If the widget is supposed to honor the field order as specified in the XML file, then the <columnsorder> tag seems contradictory.

So, ESRI states it's possible to specify the attribute table field order in Flex 3.2. Frankly, I don't see how it is possible. Please, ESRI, if this is possible, give us an explicit example of how it's done. I've wasted too much time on random trial-and-error testing.

[ScottMcGee]

After yet more random trial-and-error testing, I have determined that the field order in the attribute table is always based on an alphabetical sort on the field alias. Thus, if my XML looks like this:

<?xml version="1.0" ?>
<configuration>
     <layersettings>
     <layer name="Surface USFWS"> <!-- type="feature" -->
        <columnsorder>fields</columnsorder>
            <fields>
                <field name="LRS_Tract" alias="LRS Tract"/>
                <field name="Refuge"    alias="Refuge"/>
                <field name="Notes"     alias="Notes"/>
                <field name="NWR_Unit"  alias="Unit"/>
            </fields>
        </layer>
    </layersettings>
</configuration>


Then the attribute table looks like this:
[ATTACH=CONFIG]23108[/ATTACH]



However, if I add letters in front of the field alias names, then I can force the fields to sort in the order which I want to see in the attribute table. But this is still regardless of the order that the fields are listed in the XML. While this method achieves the desired results, it is still unacceptable because now the field names have a, b, c, d, etc. appended to the front of them, which is silly and doesn't make sense from an end-user standpoint. So this code:

<?xml version="1.0" ?>
<configuration>
     <layersettings>
        <layer name="Surface USFWS"> <!-- type="feature" -->
        <columnsorder>fields</columnsorder>
            <fields>
                <field name="LRS_Tract" alias="c - LRS Tract"/>
                <field name="Refuge"    alias="a - Refuge"/>
                <field name="Notes"     alias="d - Notes"/>
                <field name="NWR_Unit"  alias="b - Unit"/>
            </fields>
        </layer>
    </layersettings>
</configuration>


Results in an attribute table that looks like this:
[ATTACH=CONFIG]23109[/ATTACH]


So, regardless of what ESRI states in the "What's New for 3.2", the attribute table widget does not honor the field order as specfied in the AttributeTableWidget.xml file.


P.S. I have officially submitted this as a bug.