Bogue
MapServerIdentifyResults is ignoring the MaxRecordCount set in the map service config file. This works fine when the connection is through DCOM.
| Numéro d’ID de bogue | NIM007675 |
|---|---|
| Envoi | March 28, 2007 |
| Dernière modification | June 5, 2024 |
| S’applique à | No Product Found |
| Version trouvée | 9.2 |
| Version de correction | 9.3 |
| Statut | Fixed |
Solution de contournement
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.Étapes pour reproduire
ID de bogue: NIM007675
Logiciel:
- No Product Found
Recevoir une notification lorsque le statut d’un bogue change
En savoir plus sur ce sujet
Rechercher des informations associées
Rechercher une formation sur ce sujet
Explorer des pistes et donner un avis
Obtenir de l’aide auprès des experts ArcGIS
Télécharger l’application Esri Support