Numéro d’ID de bogue |
BUG-000164016 |
Envoi | December 28, 2023 |
Dernière modification | February 18, 2025 |
S’applique à | ArcGIS Pro |
Version trouvée | 3.1.3 |
Système d’exploitation | Windows OS |
Version du système d’exploitation | 11.0 |
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
There is a many to many relationship exists between these two tables.
ROW_NUMBER() OVER (ORDER BY Objekt_Point.OBJECTID) can't guarantee to assign the same row number to the same row because there are multiple rows with the exact same value in Objekt_point.OBJECTID field after the join is executed.
ArcGIS Pro's selection heavily relies on objectids (in this case it is the value from UniktID field) for selection. If these values can't be guaranteed to be same at all time, the selection does not work correctly.
A quick solution to this problem is to add an addition field in the order by clause instead to sort rows the same way when values from the first order by field is same.
Here is what can be used ROW_NUMBER() OVER (ORDER BY Objekt_Point.OBJECTID, PM_ErrandRows.OBJECTID) to assign the same row number to the same row at all time.
Étapes pour reproduire
ID de bogue: BUG-000164016
Logiciel: