<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic FEATURELAYER does not work when any OUTFIELDS are invalid (in arcgis api 3.0) in ArcGIS API for Silverlight Questions</title>
    <link>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featurelayer-does-not-work-when-any-outfields-are/m-p/374758#M9682</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi All, &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I have upgraded to ArcGIS Silverlight API 3.0 and now some of my existing code has undesired behavior.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If you have a featurelayer where any of the outfields specified are invalid the entire featurelayer is not shown at all.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In version 2.2 (my last version - I know I've neglected to upgrade several releases between 2.2 and 3.0) invalid outfields were simply ignored.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I liked that feature because in my custom featurelayermaptips I used that behavior to define category titles for sets on outfield.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Now I have to rewrite all that code.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;And do it in my custom featurelayermaptip code, yuck.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For example,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;esri:FeatureLayer ID="Bit Runs" Visible="False"&amp;nbsp; Mode="OnDemand"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; OutFields="General_Well_Information,WELL_NAME_NUMBER,HOLE_DIRECTION,FIELD,RIG_NAME_NUMBER,OPERATOR,CONTRACTOR,SPUD_DATE,TD_DATE,TOTAL_DEPTH,TIGHTHOLE,Bit_Run_Information,ASSEMBLY_RUN_NBR,RUN_START_DATE,BIT_SIZE,BIT_TYPE,BIT_MANUFACTURER,BOM_NBR,DRILLING_TD_DATE,TOTAL_DEPTH,TOTAL_DEPTH_METRIC,MAX_DEG_DEVIATION,Run_Metrics,DEPTH_IN,DEPTH_IN_METRIC,DEPTH_OUT,DEPTH_OUT_METRIC,INTERVAL_DRILLED,INTERVAL_DRILLED_METRIC,ACTUAL_HOURS,ROP,REASON_PULLED,Other,LATITUDE,LONGITUDE,WELL_ID,WELL_SITE_CD,DOC_WELL_ID"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;SPAN&gt;Url="&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://wellsgis.slb.com:6080/arcgis/rest/services/wellsgisnew/BitAtg/MapServer/5" rel="nofollow" target="_blank"&gt;http://wellsgis.slb.com:6080/arcgis/rest/services/wellsgisnew/BitAtg/MapServer/5&lt;/A&gt;&lt;SPAN&gt;"/&amp;gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I used the dummy outfields General_Well_Information, Bit_Run_Information,Run_Metrics, and Other to make a nice looking &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;hover over map tip. See attached jpg.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;BTW:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;FEATURELAYER consumed from ARCGIS 10.1 MAP SERVICE does not work if you still use ARCGIS SILVERLIGHT API 2.2 - You must upgrade!&amp;nbsp; Not sure if you must upgrade to 3.0 or if 2.4 is sufficient.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 06 Dec 2012 16:46:22 GMT</pubDate>
    <dc:creator>AnastasiaAourik</dc:creator>
    <dc:date>2012-12-06T16:46:22Z</dc:date>
    <item>
      <title>FEATURELAYER does not work when any OUTFIELDS are invalid (in arcgis api 3.0)</title>
      <link>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featurelayer-does-not-work-when-any-outfields-are/m-p/374758#M9682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi All, &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I have upgraded to ArcGIS Silverlight API 3.0 and now some of my existing code has undesired behavior.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;If you have a featurelayer where any of the outfields specified are invalid the entire featurelayer is not shown at all.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In version 2.2 (my last version - I know I've neglected to upgrade several releases between 2.2 and 3.0) invalid outfields were simply ignored.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;I liked that feature because in my custom featurelayermaptips I used that behavior to define category titles for sets on outfield.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Now I have to rewrite all that code.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;And do it in my custom featurelayermaptip code, yuck.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For example,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;esri:FeatureLayer ID="Bit Runs" Visible="False"&amp;nbsp; Mode="OnDemand"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; OutFields="General_Well_Information,WELL_NAME_NUMBER,HOLE_DIRECTION,FIELD,RIG_NAME_NUMBER,OPERATOR,CONTRACTOR,SPUD_DATE,TD_DATE,TOTAL_DEPTH,TIGHTHOLE,Bit_Run_Information,ASSEMBLY_RUN_NBR,RUN_START_DATE,BIT_SIZE,BIT_TYPE,BIT_MANUFACTURER,BOM_NBR,DRILLING_TD_DATE,TOTAL_DEPTH,TOTAL_DEPTH_METRIC,MAX_DEG_DEVIATION,Run_Metrics,DEPTH_IN,DEPTH_IN_METRIC,DEPTH_OUT,DEPTH_OUT_METRIC,INTERVAL_DRILLED,INTERVAL_DRILLED_METRIC,ACTUAL_HOURS,ROP,REASON_PULLED,Other,LATITUDE,LONGITUDE,WELL_ID,WELL_SITE_CD,DOC_WELL_ID"&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;SPAN&gt;Url="&lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://wellsgis.slb.com:6080/arcgis/rest/services/wellsgisnew/BitAtg/MapServer/5" rel="nofollow" target="_blank"&gt;http://wellsgis.slb.com:6080/arcgis/rest/services/wellsgisnew/BitAtg/MapServer/5&lt;/A&gt;&lt;SPAN&gt;"/&amp;gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I used the dummy outfields General_Well_Information, Bit_Run_Information,Run_Metrics, and Other to make a nice looking &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;hover over map tip. See attached jpg.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;BTW:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;FEATURELAYER consumed from ARCGIS 10.1 MAP SERVICE does not work if you still use ARCGIS SILVERLIGHT API 2.2 - You must upgrade!&amp;nbsp; Not sure if you must upgrade to 3.0 or if 2.4 is sufficient.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 06 Dec 2012 16:46:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-api-for-silverlight-questions/featurelayer-does-not-work-when-any-outfields-are/m-p/374758#M9682</guid>
      <dc:creator>AnastasiaAourik</dc:creator>
      <dc:date>2012-12-06T16:46:22Z</dc:date>
    </item>
  </channel>
</rss>

