There are cases where users have a host of issues in a given area of ArcGIS Pro. Not just a specific bug or a gap in functionality (idea) but a multitude of issues causing a loss of faith in parts of Pro.
Example from @chill_gis_dude in ArcGIS Pro Field Calculator is not working with a double field:
I manage an ArcGIS Enterprise deployment and we have noticed similar issues after upgrading to Pro 3.0 and higher and have completely gone back to 2.9.
We have models that run weekly to do select by locations and then calculate the geometry (acreage) of those selected polygons and have noticed that it is calculating erroneous acreages inconsistently. An obvious 20 or 40 acre polygon being calculated as 6 acres etc.
We have also noticed similar issues with field calculator where we are just calculating field3 to be a simple concatenation of field1 and field2 and have noticed that it pulls in data from other fields not even referenced in the expression.
We've pretty much lost all faith in the field calculator and calculate geometry tools, two of the most important tools in Pro. Its like buying a calculator and the "+" not working correctly every time. Trying to get them logged as bugs but the issues are very hard to reproduce.
Our layers are stored in an enterprise geodatabase driven by SQL Server 2016.
I’ve heard similar concerns from other organizations. They say they have no choice but to remain at Pro 2.9 for the time being due to general issues in a specific area of Pro.
What is the most effective way to bring concerns like this to the attention of the right Esri staff members?
