Numéro d’ID de bogue |
BUG-000164286 |
Envoi | January 11, 2024 |
Dernière modification | May 27, 2025 |
S’applique à | ArcGIS Online |
Version trouvée | Oct 2023 |
Système d’exploitation | N/A |
Version du système d’exploitation | N/A |
Statut | As Designed
Après examen par l’équipe de développement, il a été déterminé que ce comportement est prévu. Pour plus d’informations, reportez-vous à la section Informations supplémentaires.
|
Informations supplémentaires
This is a known behavior regarding the execution order of filters in feature services. When both viewDefinitionQuery and topFilter are applied to a feature service, the system processes the topFilter first, followed by the viewDefinitionQuery.
To achieve simultaneous execution of both filtering operations, the correct approach is to structure the query using sqlExpression within the viewLayerDefinition instead of using viewDefinitionQuery directly.
The recommended structure is:
json{
"viewDefinitionQuery": "",
"viewLayerDefinition": {
"filter": {
"sqlExpression": "status = 'Active'"
},
"topFilter": {
"orderByFields": "CreationDate DESC",
"groupByFields": "Name",
"topCount": 1
}
}
}
This structure ensures that both the SQL expression filter and the top filter are processed together, providing more precise control over the returned data and preventing unexpected results that may occur when filters are applied in sequence.
Solution de contournement
For query purposes, it is recommended to not add the topFilter parameter on the view definition. Use the queryTopFeatures method to get the correct result.
Étapes pour reproduire