Search: Handle selected properties for List operations

Many of our List operations for SearchServiceClient accept an optional list of property names, but for .NET this isn’t as intuitive since model property names like Name won’t actually work (server error): name is required. Additionally, while etag is also not recognized, @odata.etag (theunderlying property name) causes a different server error: that @odata.etag is not allowed in $select or $expand query parameters.

[brjohnstmsft]

An alternative to exposing this parameter on the client would be to have Get[Resource]Names APIs instead. That’s the original purpose behind adding $select to those REST APIs in the first place. Those APIs actually run much faster with $select=name because we use a different code path in the service that doesn’t retrieve all the metadata, only enumerates the names.

[brjohnstmsft]

@heaths A parameter like onlyName would work, although the response would be less convenient to consume than having a dedicated Get…Names API. Choosing between them might come down to which is most discoverable.