Hey folks! My team is experiencing a strange problem where the same tool used on different versions produces different results. We are running several select by queries in a row to help with the quality control process, and when some of the team members on 3.7 use it, it selects far too many/the wrong results. When users on 3.54 use it, the tools seem to work as intended and produces expected results. Not sure if I'm allowed to share the actual model for proprietary reasons, but I wanted to know if anyone else was getting different results version to version.
I know you said you can't share the actual model, but can you share at least the GP Tools you're calling from inside it?
I was just helping a user on another platform with a similar case of different versions producing different results. We weren't able to get enough of their code (also because of proprietary issues) to nail down the specific problem, but after a ton of back and forth, the general problem seemed to be that some tool or library that their code relied on was changed between the versions, and started producing data they hadn't accounted for. In their case, they were suddenly ending up with divide-by-zero errors, because they suddenly started getting a zero value from some chunk of code that had only ever returned valid, nonzero values before the update.
If one of the tools you're using was updated during that last update pass, you might be passing around data that's different from what you expect, which is ultimately leading to the downstream change you're seeing in the results.
Yeah! The tools here are super simple, just selections. We're using select layer by location and select layer by attribute to help locate where specific problems lie on the centerlines we're working on. The tool is attempting to find road centerlines that have a problem (a lack of a proper one way value) and also are missing a flag (a polygon we have been placing onto roads that we identify to have this problem) to show us which roads we missed in our edit review. We have tried a couple different versions, but the tools are essentially chains of select by attribute/select by location.
After further experimentation, we believe we've found that it is the select by location tool that is not working as it should- any known changes?
Yes—teams do sometimes see different selection results across ArcGIS Pro versions, and there are a couple of common causes.
1) Make sure you’re comparing patched builds, not just “3.7 vs 3.5.4.”
There is a confirmed defect where Select By Attributes can return incorrect/partial results for layers sourced from SQL Server: BUG-000177183 (found in Pro 3.5.1, fixed in 3.6 and 3.5.6).
If any of your data is coming from SQL Server/enterprise geodatabase, this is worth reviewing: BUG-000177183
2) Check for “Invert Where Clause” being on in any of the Select tools in the model.
That will make it look like “too many/wrong” features are selected. Related KB: Problem: Select Layer By Attribute returns the opposite records
3) If there are joins (especially one-to-many), “too many rows” can be expected.
Selections are stored by ObjectID; a one-to-many join can make many table rows highlight for the same selected feature: BUG-000154798
Thanks! We'll run through these and I'll report back soon.