QueryParameters.MaxFeatures

459
2
Jump to solution
08-17-2017 11:29 AM
MarkCederholm
Regular Contributor II

[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?

0 Kudos
1 Solution

Accepted Solutions
NagmaYasmin
Occasional Contributor III

Hi Mark,

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:

Layer: Damage to Commercial Buildings (ID: 0) 

Hope that helps.

Nagma

View solution in original post

0 Kudos
2 Replies
NagmaYasmin
Occasional Contributor III

Hi Mark,

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:

Layer: Damage to Commercial Buildings (ID: 0) 

Hope that helps.

Nagma

0 Kudos
MarkCederholm
Regular Contributor II

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.

0 Kudos