Are there limitations to the size of the Feature Ids input in the Run Report activity?
Hello. I have a parcel layer with 32,746 features. I want to send all of them to a report, and can do this just fine using the Get Feature Set Object IDs, and then using this output as the Feature Ids input in the Run Report activity. It works fine.
However, I have a different report that requires I pass parcel numbers, not Object IDs to the report. I've created a collection of parcel numbers that I use as the Feature Ids input. The collection looks like this: ["3-2E-05CD-00201","3-2E-05CD-00202"... etc] It works for a subset of the parcels, but fails if I send 30,690 or more records (this translates to a JSON string of 552,421 characters). I'm wondering if there is an upper limit in the size of the Feature Ids parameter that can be sent.
Any ideas?
Thanks, Chris
-
The Run Report activity doesn't apply any specific limitations. You are likely running into limits of the Reporting service.
Most likely your ~30K values are causing the where clause of your report to be larger than the report data source allows. There are different limits depending on the data source type. Ultimately reports are generating SQL statements for their queries and each database type (or ArcGIS Server and its underlying database) has limits on both the length of the SQL statement and on the number of values allowed in a SQL "IN" clause.
There are also max HTTP request size limits of Reporting imposed by IIS. This is something like 4MB, so you are probably not hitting this one yet.
This may not be your exact use case, but if you want to report on every parcel then there may not be a need to supply the feature IDs at all. You could just omit that parameter and update the query in your report to query all the records in the layer/table.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
1 kommentar