New Attribute Table Widget

[ShaunWeston]

Stuggling to get this new widget to work. I'm finding if I specify in the config something like this:

<layer label="Boundaries" url="http://testserver/arcgis/rest/services/Boundaries/Boundaries/MapServer/0"></layer> <!-- non-mapped layer(s), added for just this widget -->

It works and show all features, but doesn't update when you pan to a new extent and if I set the config like this:

  <layersettings>
     <layer name="Boundaries"> <!-- Overwriting layer settings for a map service layer -->
         <sublayer id="0" iseditable="false"> <!-- is editable only supported for a sub layer within a map service layer -->
             <fields>
                 <field name="objectid" alias="ObjectID"/>                  
             </fields>
             <showobjectid>false</showobjectid>
             <showglobalid>false</showglobalid>
             <exportlocation>true</exportlocation>         
             <showattachments>false</showattachments>
             <showrelatedrecords>false</showrelatedrecords>
             <columnsorder>alphabetical</columnsorder>    
         </sublayer>
     </layer>    
  </layersettings>

The above references a map service like this in my main config file:

             <layer label="Boundaries" type="dynamic" visible="false" alpha="1.0"
             url="http://testserver/arcgis/rest/services/Boundaries/Boundaries/MapServer"/>

It doesn't work at all. What am I doing wrong and how can I set this attribute table to work with map services I have defined in the main config file?

[SarthakDatt]

Unfortunately the only work around right now is to customize the widget to take care of this use case or to specifically add feature layers in the config(which you are already doing).

We will discuss within the team about supporting this scenario in out-of-the-box widget for the next release.

[ShaunWeston]

Ok, the only way I can get it to work for a dynamic service is to publish a feature service (enable the feature access capability in the map service) as well, so it appears this is a requirement for this to work?

Your configuration seems fine. Does "http://gis01.wch-rcc.com/ArcGIS/rest/services/Base/All_Waste_Sites2/MapServer" have a corresponding Feature service? The widget would try to look at "http://gis01.wch-rcc.com/ArcGIS/rest/services/Base/All_Waste_Sites2/FeatureServer" and check if it exists and has feature layers, then would add them

[SarthakDatt]

Ok, the only way I can get it to work for a dynamic service is to publish a feature service (enable the feature access capability in the map service) as well, so it appears this is a requirement for this to work?

Yes, right now for the out-of-the-box widget if you don't want to add individual feature layers in the config:

<layer type="feature" url="MapService/layerId-1"/>
<layer type="feature" url="MapService/layerId-2"/>

[KennyHoran]

Unfortunately the only work around right now is to customize the widget to take care of this use case or to specifically add feature layers in the config(which you are already doing).

We will discuss within the team about supporting this scenario in out-of-the-box widget for the next release.

I'll vote for this feature as well.  I too use dynamic MapServers and wondered why nothing would show up in my Attribute Table. Luckily we do use SDE so once each FeatureServer was activated the Attribute Table loaded.

[MichaelVolz]

The issue where a dynamic mapservice sourced from a file geodatabase does not show up in this widget still appears to exist with the Flex 3.2 Build.

Can anyone else confirm this to be the case?

If this is the case, does ESRI plan to modify this widget so a dynamic mapservice sourced from a file geodatabase works with this widget?

[GISDev1]

The issue where a dynamic mapservice sourced from a file geodatabase does not show up in this widget still appears to exist with the Flex 3.2 Build.

Can anyone else confirm this to be the case?

If this is the case, does ESRI plan to modify this widget so a dynamic mapservice sourced from a file geodatabase works with this widget?

Yes, it still only works on Feature Server services which need SDE.

[BjornSvensson]

Yes, it still only works on Feature Server services which need SDE.

Actually, it's not a question about SDE or not.  It's a question about whether you publish the MapService as a Feature Service (in addition to MapService).

Still, it's a problem.

We're looking to fix this for the next release.  See https://github.com/Esri/arcgis-viewer-flex/issues/98

[marcostenorio]

the error was partially corrected. Existing feature and dynamic, the AT show only the feature

[BjornSvensson]

Marcos, I'm not sure I understand.  Could you explain in more details?

It might be better to do this in a new discussion thread (instead of re-using this one from last year).  Go to ArcGIS Viewer for Flex‌ and click "Actions -> Create -> Discussion".

[GISDev1]

Actually, it's not a question about SDE or not.  It's a question about whether you publish the MapService as a Feature Service (in addition to MapService).

Well this would be cool to learn about then.

Is it possible to publish a Map Service with the Feature Service checkbox checked without SDE? Maybe your comment is meaning that SDE isn't necessary, as maybe you are differentiating the terms SDE and an Enterprise GDB?

According to the ArcGIS Server 10.1 Help document here: http://resources.arcgis.com/en/help/main/10.1/index.html#//0154000002w8000000, an enterprise geodatabase is needed for Feature Service capabilities.