Bug ID Number |
BUG-000169317 |
Submitted | July 23, 2024 |
Last Modified | October 14, 2024 |
Applies to | ArcGIS Online |
Version found | June 2024 |
Operating System | Windows OS |
Operating System Version | 11.0 64 bit |
Status | As Designed
After review by the development team, it has been determined that this behavior is as designed. See the Additional Information section for details.
|
Additional Information
The current implementation does not support the use of distinct count in combination with aggregation for fields other than those used in the statistics calculation. This behavior applies to both the Online and Enterprise feature services.
Current Behavior:
For non-aggregated queries, the documented behavior is correct.
For aggregated queries with distinct count:
The system always uses the statistics field as the distinct field.
In the example provided, it is the population field.
Out fields are only supported for aggregated queries if they are the group by fields.
Explanation:
The query structure in question presents challenges in interpretation and execution. After careful consideration and discussion with the Enterprise team, it is determined that supporting this specific use case would introduce significant complexity and potential risks to the system.
Workaround
It is recommended for the users seeking to achieve similar results to follow the following approach: Use a group by clause on the desired fields (e.g., GROUP BY zipcode, population). Calculate the distinct sum for each group. If needed, infer the total sum from the grouped results. This method provides a more reliable and supported way to obtain the required information while maintaining system integrity and performance.
Steps to Reproduce