<?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 Re: Specific fields from QueryFeaturesAsync() in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601357#M7363</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1st part of the question: Use the QueryFeatureFields parameter when querying for data:&lt;/P&gt;&lt;P&gt;&lt;A href="https://developers.arcgis.com/net/latest/wpf/api-reference//html/M_Esri_ArcGISRuntime_Data_ServiceFeatureTable_QueryRelatedFeaturesAsync.htm"&gt;https://developers.arcgis.com/net/latest/wpf/api-reference//html/M_Esri_ArcGISRuntime_Data_ServiceFeatureTable_QueryRelatedFeaturesAsync.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternatively, you can call "LoadAsync()" on a feature and it'll fetch the full data. This is especially useful if you identify a feature layer, because the feature you get back will then only have the minimum needed to render, and the geometry might be generalized (this is all done to make the rendering as fast as possible by reducing network load). Performing the full load of a feature would be required before editing it anyway.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Apr 2018 17:16:47 GMT</pubDate>
    <dc:creator>dotMorten_esri</dc:creator>
    <dc:date>2018-04-16T17:16:47Z</dc:date>
    <item>
      <title>Specific fields from QueryFeaturesAsync()</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601355#M7361</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The QueryFeaturesAsync() method on ServiceFeatureTable supports an overload that allows &lt;EM&gt;some&lt;/EM&gt; control&amp;nbsp;over the fields returned&amp;nbsp;by including a QueryFeatureFields enum value.&amp;nbsp; These values are &lt;EM&gt;IdsOnly&lt;/EM&gt;, &lt;EM&gt;Minimum&lt;/EM&gt;, and&amp;nbsp;&lt;EM&gt;LoadAll.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have two questions:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is there no capability in the SDK to pass in a list of out fields (or *) to more finely control what comes back? (The rest interface supports this)&lt;/LI&gt;&lt;LI&gt;I can't find any documentation on the behavior for the &lt;EM&gt;Minimum&lt;/EM&gt;&amp;nbsp;enum value.&amp;nbsp; IdsOnly and LoadAll are pretty self explanatory.&lt;/LI&gt;&lt;/OL&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Apr 2018 14:48:30 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601355#M7361</guid>
      <dc:creator>Mike_Quetel</dc:creator>
      <dc:date>2018-04-16T14:48:30Z</dc:date>
    </item>
    <item>
      <title>Re: Specific fields from QueryFeaturesAsync()</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601356#M7362</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mike,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;To answer your second question, the "Minimum" value for QueryFeatureFields requests&amp;nbsp;the minimum set of fields to render the feature on a map like geometry, ID, and fields needed for the renderer and labels.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope that helps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Apr 2018 15:19:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601356#M7362</guid>
      <dc:creator>NagmaYasmin</dc:creator>
      <dc:date>2018-04-16T15:19:50Z</dc:date>
    </item>
    <item>
      <title>Re: Specific fields from QueryFeaturesAsync()</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601357#M7363</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;1st part of the question: Use the QueryFeatureFields parameter when querying for data:&lt;/P&gt;&lt;P&gt;&lt;A href="https://developers.arcgis.com/net/latest/wpf/api-reference//html/M_Esri_ArcGISRuntime_Data_ServiceFeatureTable_QueryRelatedFeaturesAsync.htm"&gt;https://developers.arcgis.com/net/latest/wpf/api-reference//html/M_Esri_ArcGISRuntime_Data_ServiceFeatureTable_QueryRelatedFeaturesAsync.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Alternatively, you can call "LoadAsync()" on a feature and it'll fetch the full data. This is especially useful if you identify a feature layer, because the feature you get back will then only have the minimum needed to render, and the geometry might be generalized (this is all done to make the rendering as fast as possible by reducing network load). Performing the full load of a feature would be required before editing it anyway.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Apr 2018 17:16:47 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601357#M7363</guid>
      <dc:creator>dotMorten_esri</dc:creator>
      <dc:date>2018-04-16T17:16:47Z</dc:date>
    </item>
    <item>
      <title>Re: Specific fields from QueryFeaturesAsync()</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601358#M7364</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.esri.com/migrated-users/3050"&gt;Morten Nielsen&lt;/A&gt;&amp;nbsp;I guess I was inquiring if there was anything that offers more granular control of what gets returned then is provided by QueryFeatureFields.&amp;nbsp; Something in between, minimal and everything.&amp;nbsp; Consider the&amp;nbsp;rest API's ability to take a delimited list in out fields&amp;nbsp;in the query task:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="" class="image-1 jive-image j-img-original" src="https://community.esri.com/legacyfs/online/401544_Capture.JPG" style="width: 620px; height: 426px;" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Apr 2018 17:31:43 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601358#M7364</guid>
      <dc:creator>Mike_Quetel</dc:creator>
      <dc:date>2018-04-16T17:31:43Z</dc:date>
    </item>
    <item>
      <title>Re: Specific fields from QueryFeaturesAsync()</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601359#M7365</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;At this point, no there is not.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Apr 2018 17:33:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/specific-fields-from-queryfeaturesasync/m-p/601359#M7365</guid>
      <dc:creator>dotMorten_esri</dc:creator>
      <dc:date>2018-04-16T17:33:12Z</dc:date>
    </item>
  </channel>
</rss>

