The QueryFeaturesAsync() method on ServiceFeatureTable supports an overload that allows some control over the fields returned by including a QueryFeatureFields enum value. These values are IdsOnly, Minimum, and LoadAll.
I have two questions:
To answer your second question, the "Minimum" value for QueryFeatureFields requests the minimum set of fields to render the feature on a map like geometry, ID, and fields needed for the renderer and labels.
Hope that helps.
1st part of the question: Use the QueryFeatureFields parameter when querying for data:
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.
Morten Nielsen I guess I was inquiring if there was anything that offers more granular control of what gets returned then is provided by QueryFeatureFields. Something in between, minimal and everything. Consider the rest API's ability to take a delimited list in out fields in the query task: