ArcGIS Pro 3.2.1: The “explore” tool appears to select instead of identify,

[JamalNUMAN]

ArcGIS Pro 3.2.1: The “explore” tool appears to select instead of identify,

I observed that the “explore” tool appears to select instead of identify.

Is this a bug?

[JamalNUMAN]

Fortunately, we have  Robert_LeClair from ESRI. I would appreciate if the bug can be confirmed and reported to the appropriate channel

[Robert_LeClair]

@JamalNUMAN - with the additional details provided, I did review the internals and do not see a listed BUG for this workflow.  It does look like a BUG to me so I'd recommend starting a support ticket to build the BUG report and if validated, then the development team can fix it in a future release.

[BSBlagojevic]

@Robert_LeClair, Thanks for the info. I have already been notified by support. ESRI's attitude "This has been fixed for the upcoming ArcGIS Pro 3.3 release this year" (!?!) is incomprehensible and absolutely unacceptable to me! This opens countless questions related to ESRI's attitude towards defects in its products, towards users, and especially towards testing before the official release of new versions, which I wrote about.

But I will dwell on this question; If the BUG is fixed, why should users wait for a new version, since I'm sure, patches will be published in the meantime? Why not implement the fixed defect in the first next patch?!? Who decides that?

Thank you again!

Regards,

Branislav

[Robert_LeClair]

Branislav - as I work in Esri Training Services, I cannot comment on the process/schedule/etc. of software major and minor releases.  But I do know that the ArcGIS Pro Dev Team works extremely hard to create new functionality, address workflow issues, and resolve bugs found in the software.  I do know there is a very rigorous process that the software must go through before every major release.  As you know, there are several minor releases of the software between major releases and those minor releases do see bug fixes.  Why this fix is scheduled for 3.3 is unknown to me and something I read on the internal systems.  

We (Esri) work very hard to deliver the best GIS software possible.  It takes a "village" to make this happen.  There are many sub-teams in the overall ArcGIS Pro Dev Team working daily to create the product.  In addition, there is the Technical Support team that works directly with the customer to address bugs, issues and workflows.  Those interactions are communicated not only with the ArcGIS Pro team, but ArcGIS Enterprise, StoryMaps and other relevant teams to address and fix issues.  We're really trying but at the end of the day, we're human. Sometimes we make errors in the code or sometimes, it's a workflow that inadvertently breaks something.  We makes mistakes.  I apologize this bug fix is not timely but rest assured, it is fixed and will be delivered.

[BSBlagojevic]

Robert,

Thank you very much for the comprehensive explanation. I believe in your hard work and, let me say, it is VISIBLE! It is not disputed. However, as a senior user of Arc/Info/ArcGIS products, for many years, first in ArcMap, now in ArcGIS Pro, I notice some elementary omissions (like this one with the explore tool or with 'moving graphics'...), which, from a personal point of view, I cannot explain otherwise but in insufficient testing or in testing on negligibly small sets of 'ad hoc' recorded data. I agree with the fact that in every human work some mistakes are made (no one is perfect), but also with the fact that the mistakes we have already made should be a guide to not repeating them. ESRI, again from a personal perspective, has been repeating and renewing them for more years. And that's the problem. So, something is missing in the organization...

Best Regards,

Branislav

[Robert_LeClair]

BUG-000163247 was fixed in the latest ArcGIS Pro 3.2.2 release today - BUG-000163247 for ArcGIS Pro (esri.com)

[BSBlagojevic]

Thank you, Robert! I downloaded and installed it. Yes, BUG is fixed and Explor tool (as well as other fixed functions) now working correctly, which really saves me time in direct cross-testing and review of complex relational databases.

Regards!