Bug
MapServerIdentifyResults is ignoring the MaxRecordCount set in the map service config file. This works fine when the connection is through DCOM.
| Bug ID Number | NIM007675 |
|---|---|
| Submitted | March 28, 2007 |
| Last Modified | June 5, 2024 |
| Applies to | No Product Found |
| Version found | 9.2 |
| Version Fixed | 9.3 |
| Status | Fixed |
Workaround
The bug happens because we have a logic to test for esriIdentifyTopmost.esriIdentifyTopmost inherently means that we are really interested in the top most layer only.When we do the identify operation, we shall loop through all layers to exact all find results. However, if it is only the topmost layer that we are interested in, after collecting result for the first layer, we could just stop identifying.However, we test the top layer condition prior to testing whether the maxRecordCount has been reached. Hence in a situation where only we are interested in the topmost layer and there are more than maxRecordCount number of records there, the testing of maxRecordCount part is ignored.Steps to Reproduce
Bug ID: NIM007675
Software:
- No Product Found
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App