[100.1] Why would setting a value for QueryParameters.MaxFeatures cause QueryFeaturesAsync to fail ("Unable to complete operation") for one ServiceFeatureTable but not another (on a different server)? Perhaps it has something to do with standardizedQueries?
I believe for your service "SupportPagination" is false. To use the "MaxFeatures" in Runtime, you have to have the "SupportPagination" should be "true" of the service just like the below service:
I believe for your service "SupportPagination" is false. To use the "MaxFeatures" in Runtime, you have to have the "SupportPagination" should be "true" of the service just like the below service:
Yep, you're right. Yet another aspect of the REST API that I can't seem to ascertain using the Runtime API (or JS API, for that matter). It's right there in the JSON, too. I think I'm just going to have to hunker down and write some truly useful REST wrapper classes.
