In the past months, I've submitted some new bug reports: * BUG-000155584 - View on FGDB standalone table gives error “Failed to add data, unsupported data type.” while adding to a map * BUG-000155660 - Definition queries do not appear as active after enabling the query and reopening the definition query again * BUG-000155377 - Unable to create a bar chart on a database view created in a mobile geodatabase * BUG-000140702 [re-opened] - Right-clicking and selecting paste does not work when attempting to paste a value into the query builder in the Select By Attributes tool Edit: And a few more: * BUG-000150273 - ST_Geometry functions applied to the Shape field in Select By Attributes return the error message, "Error 000358: Invalid expression" if the feature class is registered as traditional versioned. * BUG-000155819 - Attribute table of joined layer in Mobile Geodatabase does not open when a definition query with a subquery is applied to the join table. * BUG-000155830 - Failed to open Mobile geodatabase feature attribute table after applying join from a SQL queried standalone table with error: Underlying DBMS Error [ambiguous column name objectid] * BUG-000155888 - In the Create Database View geoprocessing tool, the Output View Name parameter is cleared when the first click after entering the Output View Name occurs outside of the tool interface. * BUG-000156143 - An SQL query containing the EXISTS predicate validates successfully but returns incorrect results from a file geodatabase * BUG-000156405 - Validate Join message is incorrect in ArcGIS Pro when Add Join to table or feature with Definition Query within the same workspace. * BUG-000157223 - The View Icon shows as Standalone table instead as Feature Class in Mobile Geodatabase * BUG-000156931 - Unable to select features using the Explore or selection tool from a view in a mobile geodatabase in ArcGIS Pro. * BUG-000157376 - Unable to select features using the Explore or selection tool from a view with a join in a File geodatabase in ArcGIS Pro * BUG-000157475 - Cannot open table from the Catalog pane for a spatial view found in a mobile geodatabase. * BUG-000157568 - In ArcGIS Pro, when a file geodatabase is placed in a file folder that contains .gdb in the folder name, you cannot add new feature classes, feature datasets, tables, etc...to the file geodatabase. * BUG-000157571 - When running the Make Route Event Layer tool, the Layer Name or Table View default to the table owner instead of the table name in Oracle Enterprise Geodatabase * BUG-000157565 - When running the Make Route Event Layer tool, the Layer Name or Table View default to the table owner instead of the table name in Mobile Geodatabase * BUG-000157718 - Excel to Table tool prefixes table name with "main.main_" when importing to mobile geodatabase * BUG-000157719 - Excel to Table tool prefixes table name with table owner when importing to Oracle enterprise geodatabase * BUG-000157728 - Creating a new geodatabase in a favorite folder causes Catalog to expands multiple folders * Internal Esri GitHub bug reported: ‘Progress Indicator not showing in catalog when creating new mGDB’ [Esri Case 03318871] * BUG-000157736: Create Database View geoprocessing tool returns incorrect data when SQL CASE expression returns a text value in the View Definition parameter * BUG-000157874 - Sorting fails after a Flag field is added to a view definition, the view is joined to a feature layer, and the Flag field is moved to the front of the table * BUG-000157875 - Remove Join tool fails after a Flag field is added to a view definition, the view is joined to a feature layer, and fields in the joined table are reordered and sorted * BUG-000158141: The cardinality of a join is incorrect in the Layer properties for 1:1 joins in ArcGIS Pro 3.1 * BUG-000158140: ArcGIS Pro: Join from table to database view generate Join fields with null values * BUG-000158324: Mobile GDB view definition contains "CREATE VIEW [name of table] AS" , whereas File geodatabase views and enterprise geodatabase views do not. * BUG-000158187: When using "Truncate Table" with a table that has a join, ArcGIS Pro provides an incorrect error message of "001400: Only the data owner may execute" * BUG-000158857: When renaming a table or feature class in a mobile geodatabase in ArcGIS Pro, the selected rename text displays the previous attempt at renaming, even if the attempt failed. * BUG-000158912 - User with ArcGIS Pro 3.1.2 and mobile geodatabase can't save field alias using same name as field for their standalone table. * BUG-000159358: Delete option is available in the attribute table for a field of a joined table * BUG-000159633: In a mobile geodatabase table in ArcGIS Pro, the field alias gets automatically set to the previous field name. * BUG-000159170 - ArcGIS Pro 3.1.2 - Unable to sort joined fields when a mobile geodatabase standalone table is joined to a mobile geodatabase feature class in a 1 to many join. * BUG-000160320: Slow performance in Pro when interacting with the attribute table of data which participates in a join. * BUG-000158623 - ArcGIS Pro - The 'Move to End' button within the Attribute Table does not work as expected while working with tables from regular databases or mobile geodatabase. * BUG-000160924 : SQL query becomes case sensitive when a Feature Layer is joined to a table stored in a Mobile Geodatabase. After joining a feature layer and a table (both stored in a Mobile Geodatabase), SQL query becomes case sensitive and the previous SQL query expression fails to execute. * BUG-000163083 - ArcGIS Pro does not honor the Allow NULL value that is set for the SHAPE field during feature class creation. * BUG-000163402: Double click is required when adding new rows to the attribute table of a feature class that has no user defined fields. * BUG-000163640: SQL Expression applied to the Shape field in Select By Attributes returns the error message, "Error 000358: Invalid expression" if the feature class is registered as traditional versioned. * BUG-000163772: Views in file and mobile geodatabases do not indicate in their Data Source properties if they have been registered with the database * BUG-000163754 - Catalog item properties of FGDB (and Enterprise GDB) database view: "Manage" options (Attachments, Global IDs, & editor tracking) should not be available * BUG-000163933: ArcGIS Pro 3.2 - Appending data from a file geodatabase feature class to a table using matching fields for update throws the error "Error 000229: Cannot open TABLE" despite successful append/update. * BUG-000164071: In ArcGIS Pro, when using the Table Select (Analysis) tool, the Mobile Geodatabase prefix is used as Output Table instead of original Feature Class name * BUG-000164132: The 'Clear' button under the Contents pane selection tab is missing when selecting zero records in ArcGIS Pro * BUG-000164133: The clear button is grayed out when selecting zero records and ensure consistent behavior for the clear button in ArcGIS Pro * BUG-000164128 Unlike ArcGIS Pro 3.1, when importing a Display Filter file in ArcGIS Pro 3.2, the feature layer is not automatically updated according to the imported file. * BUG-000164177: Database Views show SELECT, INSERT, UPDATE, and DELETE Privileges in the Data Source properties * BUG-000164343: ArcGIS Pro 3.2 - The field name in attribute table does not update after applying SQL expression when creating database view in File Geodatabase * BUG-000164295: Sorting a field removes rows from an attribute table with a one-to-many join between a feature class and a standalone table in a mobile geodatabase. * BUG-000164393: The Add Spatial Join tool returns ERROR 000728 when applied to a feature class stored in a Mobile Geodatabase or EGDB * BUG-000164420: Database View created in file geodatabase with Join definition does not create the required duplicate fields * BUG-000164429: When creating a database view, using a cast function in the where clause results in an error * BUG-000164631: Attribute indexes generated on fields participating in an inner join for the creation of a file geodatabase database view * BUG-000164707: In ArcGIS Pro 3.2, there are some geoprocessing tools (such as "Make Feature Layer" or "Make Table View") that have a parameter with a note saying "This parameter is not used". This parameter does not cause any direct issues, however it is confusing and counter-intuitive to clients. * BUG-000164755: The field is not populated when CAST is used with a file geodatabase with "Create Database View" * BUG-000164759 - The "Make Table View" tool output doesn't include a Query section in the Table Properties if the Input table is an unregistered table picked via the Folder Icon. * BUG-000165217 - When a relate exists between a table and a query layer with a composite key joined to another table, related records are not displayed if the query layer name contains a space. * BUG-000166125: ArcGIS Pro 3.2.2 - Make Query Table Tool joining all tables despite selected records * BUG-000167214: Attribute Indexes in a Mobile Geodatabase reappear after deletion in ArcGIS Pro. * BUG-000167373: Query Layer with WHERE clause does not show full query in Diagnostic Monitor * BUG-000167456: Copying or exporting a feature class into a non-EGDB Oracle Database results in long integer fields being displaying as Big Integer in the Fields View * BUG-000167563: Join with definition query doesn't export the correct number of records, instead it exports all the records. * BUG-000167610 - The Create Unregistered Feature Class geoprocessing tool does not honor settings like Geometry Type, Has M, Has Z, or Spatial Reference while creating the output. * BUG-000167752: Misleading error message returned by Copy tool when only the path the to GDB is input without a feature class name. * BUG-000167802: ArcGIS Pro - Can't copy text from geoprocessing input parameter using right-click menu. * BUG-000167962: ArcGIS Pro 3.3 - Wrong context menu options displayed for standalone table in contents pane. * BUG-000168565 - The Find Identical geoprocessing tool auto-populates the Output Dataset name with the data owner name instead of the feature class name when the Input Dataset is picked from the drop-down of the layer list from the map. * BUG-000168914: Error "The SQL expression has invalid syntax" is encountered when a subquery is used on an unregistered table, query layer, or unregistered database view. * BUG-000169056: “ERROR 000358 DBMS table not found[ORA-04043: object xyzx.xyzxy does not exist]” is encountered when using "Make Aggregation Query Layer" tool with Oracle geodatabase. * BUG-000169250 - The Make Aggregation Query Layer geoprocessing tool does not recognize 64-bit Object ID (bigint) as a unique identifier. * BUG-000169342: In ArcGIS Pro when a join is created between two query layers where the second query layers was copy/pasted from the first query layer, there is no reference to the second query in the join properties. * BUG-000170076: Unable to alter the Alias of a field for a registered View via the Fields menu in ArcGIS Pro * BUG-000170416 - The Assign Domain To Field tool fails with "ERROR 000499: table is not editable" while working on views registered with the file geodatabase. * BUG-000170482: When running the Spatial Join tool in Pro, the output feature class name defaults to include the data owner, not the feature class name. * BUG-000170592: ArcGIS Pro's DRA function is highlighted as enabled for raster symbology that does not support DRA. * BUG-000170631: Tables in mobile geodatabase cannot perform one-to-many joins using Add Join geoprocessing tool in ArcGIS Pro. * BUG-000170869: Adding a definition query excludes a row of data when using Add Join geoprocessing tool in ArcGIS Pro * BUG-000171002: Mobile Geodatabase Table Views recognize ObjectIDs as Long (in version 2.9.5) or Big Integer (in versions 3.3.1 and 3.3.2), instead of the expected ObjectID data type. * BUG-000171080: In ArcGIS Pro, when resizing a column in the attribute table by double-clicking on the boundary between two columns, the resize does not stay after refreshing the table. * BUG-000171084: Selecting the "Run" button of geoprocessing tools in ArcGIS Pro through the tab button shows a faint highlight compared to the expected, bolder highlight. * BUG-000171301 - ArcGIS Pro fails with "ERROR 160195: An invalid SQL statement was used." when the Make Query Table tool is run on a Query Layer. * BUG-000171586: Compression Quality when using Export Raster does not honor the range from 0 to 100 * BUG-000171969: Inconsistent Join Operation behaviour when joining tables with definition query in ArcGIS Pro * BUG-000172709: Generate Definition Query From Selection geoprocessing tool includes a toggle to deselect selections. When disabled, it causes the tool to fail. * BUG-000172724: Generate Definition Query from Selection geoprocessing tool documentation does not specify which data types are unacceptable and why. * BUG-000173164: In ArcGIS Pro, the Select by Attributes tool removes the leading space from a value in clause-mode, but not in SQL-mode. * BUG-000173175: In ArcGIS Pro, Select By Attribute with an empty clause or SQL expression will select all the records in a table. * BUG-000173762: In ArcGIS Pro, the Add join tool creates a one-to-one join when the join is created between a Feature class and an unregistered view, even when one-to-many cardinality exists between the data. * BUG-000174348: Contents Search does not filter standalone tables in ArcGIS Pro * BUG-000174199: Inputting a domain name with length greater than 255 characters causes Pro 3.4 to crash. * BUG-000174360: When using the Export Raster geoprocessing tool, if the operation gets canceled, then the Output Raster Dataset parameter gets reset to the original value. * BUG-000174631: Entering a line break into an Attribute Table cell value using Shift+Enter works for the first edit but not for subsequent edits. * BUG-000174722: In ArcGIS Pro, it is not possible to copy a portion of a text value in a layer's attribute table using a mouse. * BUG-000175441: Clicking and dragging row headers in the attribute table to select multiple rows causes the table to scroll left. * BUG-000176895: When a join exists between a table and a feature class in an enterprise geodatabase, 'Select By Attributes' takes a long time to load the results in the attribute table * BUG-000184633: Edit widget in ArcGIS Experience builder does not copy attachments when using the copy/past feature and does not allow you to add attachments until creating the point. * BUG-000184634: Synopsis : Pressing the “Windows + :” shortcut does not insert symbols into text fields within the ArcGIS Pro attribute table. When I google those bug report numbers, I don't get many hits. Question: Why aren't those kinds of bug reports publicly available? * For people who are googling issues online. * For people who don't have access to their organization's My Esri account.* Often, only IT staff at an organization have access to their organization's My Esri account. There are lots of Esri users like me who work in departments other than IT and, therefore don't have access. Thanks.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why aren't more ArcGIS Pro bug reports shared publicly?

Bud

In the past months, I've submitted some new bug reports:

BUG-000155584 - View on FGDB standalone table gives error “Failed to add data, unsupported data type.” while adding to a map
BUG-000155660 - Definition queries do not appear as active after enabling the query and reopening the definition query again
BUG-000155377 - Unable to create a bar chart on a database view created in a mobile geodatabase
BUG-000140702 [re-opened] - Right-clicking and selecting paste does not work when attempting to paste a value into the query builder in the Select By Attributes tool

Edit: And a few more:
BUG-000150273 - ST_Geometry functions applied to the Shape field in Select By Attributes return the error message, "Error 000358: Invalid expression" if the feature class is registered as traditional versioned.
BUG-000155819 - Attribute table of joined layer in Mobile Geodatabase does not open when a definition query with a subquery is applied to the join table.
BUG-000155830 - Failed to open Mobile geodatabase feature attribute table after applying join from a SQL queried standalone table with error: Underlying DBMS Error [ambiguous column name objectid]
BUG-000155888 - In the Create Database View geoprocessing tool, the Output View Name parameter is cleared when the first click after entering the Output View Name occurs outside of the tool interface.
BUG-000156143 - An SQL query containing the EXISTS predicate validates successfully but returns incorrect results from a file geodatabase
BUG-000156405 - Validate Join message is incorrect in ArcGIS Pro when Add Join to table or feature with Definition Query within the same workspace.
BUG-000157223 - The View Icon shows as Standalone table instead as Feature Class in Mobile Geodatabase
BUG-000156931 - Unable to select features using the Explore or selection tool from a view in a mobile geodatabase in ArcGIS Pro.
BUG-000157376 - Unable to select features using the Explore or selection tool from a view with a join in a File geodatabase in ArcGIS Pro
BUG-000157475 - Cannot open table from the Catalog pane for a spatial view found in a mobile geodatabase.
BUG-000157568 - In ArcGIS Pro, when a file geodatabase is placed in a file folder that contains .gdb in the folder name, you cannot add new feature classes, feature datasets, tables, etc...to the file geodatabase.
BUG-000157571 - When running the Make Route Event Layer tool, the Layer Name or Table View default to the table owner instead of the table name in Oracle Enterprise Geodatabase
BUG-000157565 - When running the Make Route Event Layer tool, the Layer Name or Table View default to the table owner instead of the table name in Mobile Geodatabase
BUG-000157718 - Excel to Table tool prefixes table name with "main.main_" when importing to mobile geodatabase
BUG-000157719 - Excel to Table tool prefixes table name with table owner when importing to Oracle enterprise geodatabase
BUG-000157728 - Creating a new geodatabase in a favorite folder causes Catalog to expands multiple folders
Internal Esri GitHub bug reported: ‘Progress Indicator not showing in catalog when creating new mGDB’ [Esri Case 03318871]
BUG-000157736: Create Database View geoprocessing tool returns incorrect data when SQL CASE expression returns a text value in the View Definition parameter
BUG-000157874 - Sorting fails after a Flag field is added to a view definition, the view is joined to a feature layer, and the Flag field is moved to the front of the table
BUG-000157875 - Remove Join tool fails after a Flag field is added to a view definition, the view is joined to a feature layer, and fields in the joined table are reordered and sorted
BUG-000158141: The cardinality of a join is incorrect in the Layer properties for 1:1 joins in ArcGIS Pro 3.1
BUG-000158140: ArcGIS Pro: Join from table to database view generate Join fields with null values
BUG-000158324: Mobile GDB view definition contains "CREATE VIEW [name of table] AS" , whereas File geodatabase views and enterprise geodatabase views do not.
BUG-000158187: When using "Truncate Table" with a table that has a join, ArcGIS Pro provides an incorrect error message of "001400: Only the data owner may execute"
BUG-000158857: When renaming a table or feature class in a mobile geodatabase in ArcGIS Pro, the selected rename text displays the previous attempt at renaming, even if the attempt failed.
BUG-000158912 - User with ArcGIS Pro 3.1.2 and mobile geodatabase can't save field alias using same name as field for their standalone table.
BUG-000159358: Delete option is available in the attribute table for a field of a joined table
BUG-000159633: In a mobile geodatabase table in ArcGIS Pro, the field alias gets automatically set to the previous field name.
BUG-000159170 - ArcGIS Pro 3.1.2 - Unable to sort joined fields when a mobile geodatabase standalone table is joined to a mobile geodatabase feature class in a 1 to many join.
BUG-000160320: Slow performance in Pro when interacting with the attribute table of data which participates in a join.
BUG-000158623 - ArcGIS Pro - The 'Move to End' button within the Attribute Table does not work as expected while working with tables from regular databases or mobile geodatabase.
BUG-000160924 : SQL query becomes case sensitive when a Feature Layer is joined to a table stored in a Mobile Geodatabase. After joining a feature layer and a table (both stored in a Mobile Geodatabase), SQL query becomes case sensitive and the previous SQL query expression fails to execute.
BUG-000163083 - ArcGIS Pro does not honor the Allow NULL value that is set for the SHAPE field during feature class creation.
BUG-000163402: Double click is required when adding new rows to the attribute table of a feature class that has no user defined fields.
BUG-000163640: SQL Expression applied to the Shape field in Select By Attributes returns the error message, "Error 000358: Invalid expression" if the feature class is registered as traditional versioned.
BUG-000163772: Views in file and mobile geodatabases do not indicate in their Data Source properties if they have been registered with the database
BUG-000163754 - Catalog item properties of FGDB (and Enterprise GDB) database view: "Manage" options (Attachments, Global IDs, & editor tracking) should not be available
BUG-000163933: ArcGIS Pro 3.2 - Appending data from a file geodatabase feature class to a table using matching fields for update throws the error "Error 000229: Cannot open TABLE" despite successful append/update.
BUG-000164071: In ArcGIS Pro, when using the Table Select (Analysis) tool, the Mobile Geodatabase prefix is used as Output Table instead of original Feature Class name
BUG-000164132: The 'Clear' button under the Contents pane selection tab is missing when selecting zero records in ArcGIS Pro
BUG-000164133: The clear button is grayed out when selecting zero records and ensure consistent behavior for the clear button in ArcGIS Pro
BUG-000164128 Unlike ArcGIS Pro 3.1, when importing a Display Filter file in ArcGIS Pro 3.2, the feature layer is not automatically updated according to the imported file.
BUG-000164177: Database Views show SELECT, INSERT, UPDATE, and DELETE Privileges in the Data Source properties
BUG-000164343: ArcGIS Pro 3.2 - The field name in attribute table does not update after applying SQL expression when creating database view in File Geodatabase
BUG-000164295: Sorting a field removes rows from an attribute table with a one-to-many join between a feature class and a standalone table in a mobile geodatabase.
BUG-000164393: The Add Spatial Join tool returns ERROR 000728 when applied to a feature class stored in a Mobile Geodatabase or EGDB
BUG-000164420: Database View created in file geodatabase with Join definition does not create the required duplicate fields
BUG-000164429: When creating a database view, using a cast function in the where clause results in an error
BUG-000164631: Attribute indexes generated on fields participating in an inner join for the creation of a file geodatabase database view
BUG-000164707: In ArcGIS Pro 3.2, there are some geoprocessing tools (such as "Make Feature Layer" or "Make Table View") that have a parameter with a note saying "This parameter is not used". This parameter does not cause any direct issues, however it is confusing and counter-intuitive to clients.
BUG-000164755: The field is not populated when CAST is used with a file geodatabase with "Create Database View"
BUG-000164759 - The "Make Table View" tool output doesn't include a Query section in the Table Properties if the Input table is an unregistered table picked via the Folder Icon.
BUG-000165217 - When a relate exists between a table and a query layer with a composite key joined to another table, related records are not displayed if the query layer name contains a space.
BUG-000166125: ArcGIS Pro 3.2.2 - Make Query Table Tool joining all tables despite selected records
BUG-000167214: Attribute Indexes in a Mobile Geodatabase reappear after deletion in ArcGIS Pro.
BUG-000167373: Query Layer with WHERE clause does not show full query in Diagnostic Monitor
BUG-000167456: Copying or exporting a feature class into a non-EGDB Oracle Database results in long integer fields being displaying as Big Integer in the Fields View
BUG-000167563: Join with definition query doesn't export the correct number of records, instead it exports all the records.
BUG-000167610 - The Create Unregistered Feature Class geoprocessing tool does not honor settings like Geometry Type, Has M, Has Z, or Spatial Reference while creating the output.
BUG-000167752: Misleading error message returned by Copy tool when only the path the to GDB is input without a feature class name.
BUG-000167802: ArcGIS Pro - Can't copy text from geoprocessing input parameter using right-click menu.
BUG-000167962: ArcGIS Pro 3.3 - Wrong context menu options displayed for standalone table in contents pane.
BUG-000168565 - The Find Identical geoprocessing tool auto-populates the Output Dataset name with the data owner name instead of the feature class name when the Input Dataset is picked from the drop-down of the layer list from the map.
BUG-000168914: Error "The SQL expression has invalid syntax" is encountered when a subquery is used on an unregistered table, query layer, or unregistered database view.
BUG-000169056: “ERROR 000358 DBMS table not found[ORA-04043: object xyzx.xyzxy does not exist]” is encountered when using "Make Aggregation Query Layer" tool with Oracle geodatabase.
BUG-000169250 - The Make Aggregation Query Layer geoprocessing tool does not recognize 64-bit Object ID (bigint) as a unique identifier.
BUG-000169342: In ArcGIS Pro when a join is created between two query layers where the second query layers was copy/pasted from the first query layer, there is no reference to the second query in the join properties.
BUG-000170076: Unable to alter the Alias of a field for a registered View via the Fields menu in ArcGIS Pro
BUG-000170416 - The Assign Domain To Field tool fails with "ERROR 000499: table is not editable" while working on views registered with the file geodatabase.
BUG-000170482: When running the Spatial Join tool in Pro, the output feature class name defaults to include the data owner, not the feature class name.
BUG-000170592: ArcGIS Pro's DRA function is highlighted as enabled for raster symbology that does not support DRA.
BUG-000170631: Tables in mobile geodatabase cannot perform one-to-many joins using Add Join geoprocessing tool in ArcGIS Pro.
BUG-000170869: Adding a definition query excludes a row of data when using Add Join geoprocessing tool in ArcGIS Pro
BUG-000171002: Mobile Geodatabase Table Views recognize ObjectIDs as Long (in version 2.9.5) or Big Integer (in versions 3.3.1 and 3.3.2), instead of the expected ObjectID data type.
BUG-000171080: In ArcGIS Pro, when resizing a column in the attribute table by double-clicking on the boundary between two columns, the resize does not stay after refreshing the table.
BUG-000171084: Selecting the "Run" button of geoprocessing tools in ArcGIS Pro through the tab button shows a faint highlight compared to the expected, bolder highlight.
BUG-000171301 - ArcGIS Pro fails with "ERROR 160195: An invalid SQL statement was used." when the Make Query Table tool is run on a Query Layer.
BUG-000171586: Compression Quality when using Export Raster does not honor the range from 0 to 100
BUG-000171969: Inconsistent Join Operation behaviour when joining tables with definition query in ArcGIS Pro
BUG-000172709: Generate Definition Query From Selection geoprocessing tool includes a toggle to deselect selections. When disabled, it causes the tool to fail.
BUG-000172724: Generate Definition Query from Selection geoprocessing tool documentation does not specify which data types are unacceptable and why.
BUG-000173164: In ArcGIS Pro, the Select by Attributes tool removes the leading space from a value in clause-mode, but not in SQL-mode.
BUG-000173175: In ArcGIS Pro, Select By Attribute with an empty clause or SQL expression will select all the records in a table.
BUG-000173762: In ArcGIS Pro, the Add join tool creates a one-to-one join when the join is created between a Feature class and an unregistered view, even when one-to-many cardinality exists between the data.
BUG-000174348: Contents Search does not filter standalone tables in ArcGIS Pro
BUG-000174199: Inputting a domain name with length greater than 255 characters causes Pro 3.4 to crash.
BUG-000174360: When using the Export Raster geoprocessing tool, if the operation gets canceled, then the Output Raster Dataset parameter gets reset to the original value.
BUG-000174631: Entering a line break into an Attribute Table cell value using Shift+Enter works for the first edit but not for subsequent edits.
BUG-000174722: In ArcGIS Pro, it is not possible to copy a portion of a text value in a layer's attribute table using a mouse.
BUG-000175441: Clicking and dragging row headers in the attribute table to select multiple rows causes the table to scroll left.
BUG-000176895: When a join exists between a table and a feature class in an enterprise geodatabase, 'Select By Attributes' takes a long time to load the results in the attribute table
BUG-000184633: Edit widget in ArcGIS Experience builder does not copy attachments when using the copy/past feature and does not allow you to add attachments until creating the point.
BUG-000184634: Synopsis : Pressing the “Windows + :” shortcut does not insert symbols into text fields within the ArcGIS Pro attribute table.

When I google those bug report numbers, I don't get many hits.

Question: Why aren't those kinds of bug reports publicly available?

For people who are googling issues online.
For people who don't have access to their organization's My Esri account.
- Often, only IT staff at an organization have access to their organization's My Esri account. There are lots of Esri users like me who work in departments other than IT and, therefore don't have access.

Thanks.

Najděte více příspěvků označených jako

Geodatabase

Accepted answers

AndrewMunn

Hi @ChristianWells and @Bud

Our bug pages are searchable by Google and other search engines.

I think the issue that makes searching on Google inconsistent is that bugs are taken offline briefly for editing and then returned to the support site. After that we have to wait for Google to crawl through the support site again to update their search results.

The bugs are available through the support site search more quickly because our search tool indexes our own content more often than Google indexes our content.

We have tried to minimize the types of edits that cause bugs to be temporarily removed, but there still are some edits that trigger a copy review before they can be returned to the support site. We copy review the bugs so that no public field contains customer information or internal only information.

I don't think it is a matter of formatting the search query, using the bug id and "Esri" or "Esri support" should work fine.

All comments

ryanuthoff

What's disappointing is the sheer amount of bugs Esri must have in their software. You're just one person. I'm one person. And think about the number of bugs we, as individual people, have submitted. Then let's add up all of the other users of Esri's software and think about the amount of bugs that must be getting submitted.

The fact that my bug was first introduced in 10.9.1 and first logged on September 8, 2022 and sat in Esri's bug queue for 1.5 YEARS before finally being addressed and fixed in 11.4 (which will be over 2 years since the bug was first logged by the time 11.4 is released), should be enough to say how big Esri's bug backlog is. Or alternatively, how under-staffed Esri's bug fixing department is. Completely unacceptable and disappointing.

wayfaringrob

I completely agree. There is more tone policing than action. Sick of it.

Bud

I am finding that I could spend all day every day reporting new bugs to Esri. My organization pays a lot of money for this software, and here I am, essentially being an employee of Esri as a tester, except we're paying Esri, they're not paying me.

This can't continue.

Edit: I understand that Esri's business model is to deploy rapidly and fix later. But I feel we are at a breaking point. Esri needs to invest more in testing and bug fixing. Otherwise, customers will find the software too problematic and borderline unusable. Example: Is ArcGIS Pro the right tool for tabular/join-based geodatabase analysis? In that case, we couldn't use ArcGIS Pro due to bugs, and had to use Excel instead.

Bud

For our notes, BUG-000158187 is now googleable.

https://www.google.com/search?q=BUG-000158187+site%3Aesri.com

AndrewMunn

Hi Bud, thanks for this post. I am seeing the same behavior. I have reached out to our internal search engine optimization team to understand what might be happening. We may be able to improve the sitemap to make it easier for Google to find all the bug pages.

Bud

Here's an example of a bug that I reported in May 2023:
BUG-000158187 - When using the Truncate Table tool with a table that has a join, ArcGIS Pro returns an incorrect error message, "001400: Only the data owner may execute."

The bug is visible on the Esri Support site: https://support.esri.com/en-us/bug/when-using-the-truncate-table-tool-with-a-table-that-ha-bug-000158187

But strangely, the Esri Support page does not come up when I google that bug:
https://www.google.com/search?q=BUG-000158187+site%3Aesri.com

As far as I know, that bug wasn't "taken offline briefly for editing and then returned to the support site". The reason I say that is: I haven't received any email notifications about changes to that bug, such as comments or status changes. And I would think that bug is a very low priority, so I would be surprised if it has been acted on recently.

survey123_solutions

I just wanted to share the bug that I am referring to above (who knows, this may cause a bit more urgency) - This is it
https://support.esri.com/en-us/bug/generating-reports-from-the-arcgis-survey123-web-design-bug-000144853

And when we looked at it August 2023, it was not actively being worked on. For a system that is supposed to be used for Feature Reports? How is that? We had issued 200 licenses for users to begin using the Survey that was developed, then "needed" to generate those reports- and then this! So I am "now" on the "ArcGIS Pro" Reports journey - while allowing my users to use the 38 page Feature Report Template temporarily. Very frustrating. Praying that ArcGIS Pro Reports are a bit more user friendly, while the last week of working on them has not been so, but I am holding out hope.

survey123_solutions

Chrisian, thanks so much for the feedback. It's happened to me numerous times where I have actually had to send the Bug to the person at Tech Support that was trying to help me for days and weeks- when I learned of the bug myself - but they still did not know about it. It should be communicated. It should be on the very page that user is using. Right now a bug that was found after months of me using the Survey123 Feature Reports too (and banging head against wall), "then" had to use our "company credits" to pay for "professional services" - where I provided just about everything, after all i had months of work into this, i provided all of the templates I had created with a simple request - why do the filters that are "visible" on the computer window "not the same" as the filters that generate in the PDF that is exported? It was absolutely maddening! That is when I find out-

1- That there is a bug associated with that - wonderful!
2- That the report template workaround that was suggested -- was a 38 page Microsoft Word Template that crashes my machine every time I try to edit it.

That is only ONE of many scenarios. That I can go into.

It's just not right. In my 25 years of developing apps across so many platforms with so many companies, I've never come across a company that operates like this. And again, I'm a huge fan of GIS, love some of the people that I've worked with, but the sheer lack of support online, allowing the paying customers to go crazy, then telling them that they need to pay for professional services to figure out a workaround to the defective platform that Esri is charging us for... is quite frustrating to say the least. I do love the world of GIS though!

survey123_solutions

I have wasted MONTHS of my time only to find that there were bugs associated with the very thing that had me spending thousands of hours trying to solve. Not once, not twice, but many times. Only to find out from Tech Support that there was a bug associated with that - and then us paying for premium tech support to find a workaround. As much as I love GIS and the Esri products, there is SO much that needs to be improved.

Christian_Wells

Thanks for the reply @AndrewMunn and the recommendations for customers looking up this information.

AndrewMunn

Hi @ChristianWells and @Bud

Our bug pages are searchable by Google and other search engines.

The bugs are available through the support site search more quickly because our search tool indexes our own content more often than Google indexes our content.

I don't think it is a matter of formatting the search query, using the bug id and "Esri" or "Esri support" should work fine.

Christian_Wells

fyi @AndrewMunn - this thread has been ongoing before and after the new support site migration re: SEO for bugs on the support website. Do you have any tips for getting the best search results for bugs? Or do you know if there is any focus on improving SEO related to bugs?

Bud

Bugs still don't seem to be googleable. I tried googling a fixed bug: BUG-000155660. But I didn't get any hits.

Yet, that bug is listed in the support site: https://support.esri.com/en-us/bug/definition-queries-do-not-appear-as-active-after-enabli-bug-000155660

Searching the support site works. But I still think bug information should show up in search engines.

NielsVemmelund1

I just want to add to this discussion that it would be really nice if I could search for a specific bug on support.esri.com:
Search with the BUG filter on >
If the _exact_ bug number is matched
Then - show the bug content OR return its status ('under review';'secret') if the content of the bug for any reason is unavailable to the user community
Else if it's not found, return 'no such bug number'

That would save us (me at least) a lot of time.

(I haven't been able to do that in the new support site - but as i remember it was possible on the old site.
disclaimer - i haven't studied the documentation of the new support search function yet 😀)

wayfaringrob

Right. I have had numerous problems with support not showing up on the zoom call or not calling when they said they would. Or they call around the clock as if you are holding them up. The burden is always on the user to identify the cause of the issue. If you can't figure out how to reproduce the bug, they waste your time suggesting you try the same workarounds you've already tried and act like they can't do anything about it. This is why I don't report bugs anymore. It was way too much work and often ended with no resolution. So I post things as ideas, but then Esri complains that oh, you can't post that here. Fine! Won't post at all then. You'd think they'd be interested in doing something about their poor reputation for bugs and crashes...

ryanuthoff

I 100% agree with this. I've seen several threads on geonet where Esri employees say to log a bug with Esri support. I'm not sure if Esri employees have actually interacted with Esri support, but that is often easier said than done. On average, I have to wait 3-5 days for the assigned support analyst to reply back to me anytime I reply back to their email containing questions. I've also been ghosted by Esri support when we schedule a call to review the issue.

Finally, when I can finally get support to reproduce my issue, the bug sits in the Esri backlog for months and months, if not longer, before most likely being marked as "Not in current product plan." I had to create an ArcGIS Idea for Esri to change their documentation to explicitly list why a tool would fail under certain conditions. Luckily, that post got Esri to change their mind and actually address the issue. But having to jump through all these hoops just to submit bug reports (that might have already been submitted in the past) is ridiculous.

wayfaringrob

I totally agree. With the sheer volume of bugs found in Esri software and the onerous technical support process, it should be much, much easier for users to not only report but to find information about existing bugs, updates, and workarounds that may pertain to them. This would save people a lot of hassle in trying to diagnose or wasting time with redundant tech support calls that go nowhere. (Or, as many young users do, in my experience -- not bother with any of that and eventually walk away from GIS). They need a Communities site for bug reports similar to Microsoft's feedback hub. There needs to be more transparency, and more accountability for actually fixing what often feels like beta software. There is no reason a private multibillion dollar corporation cannot hire the resources to at least human test things for basic functionality before release and to address issues and feature requests rapidly.

Bud

@JoshuaBixby, like you mentioned, the bug numbers are in the URLs now. Nice!

support.esri.com/en-us/bug/the-attribute-table-of-a-joined-layer-in-a-mobile-geoda-bug-000155819

https://support.esri.com/en-us/bug/the-attribute-table-of-a-joined-layer-in-a-mobile-geoda-bug-000155819

Christian_Wells

@Bud, thank you for the reminder.

Digging into this, I found that any time a bug is modified or edited, including when a product team changes the fields for the latest version reproduced, the bug is taken offline immediately. Then it has to be republished by our copy editing team.

I acknowledge this is not a good experience, and the web team has it on their backlog to ensure bugs persist until they are explicitly republished.

BranislavBlagojevic

Unfortunately, this is not an isolated case; Attribute Driven Symbology BUG-000104316 was discovered back in April 2017 (BUG-000104316: The attribute-driven symbology assigned to features .. (esri.com)) and he is still not resolved!!! Elementary cartography...really poor!

Bud

Here's an example of a bug I reported 9 months ago, but it still isn't available on the Esri Technical Support website: https://support.esri.com/en/search-results#search?q=000150273&content-type=Bugs

BUG-000150273 - ST_Geometry functions applied to the Shape field in Select By Attributes return the error message, "Error 000358: Invalid expression" if the feature class is registered as traditional versioned.
Reported: June 24, 2022

I'm told the bug is still "In Review". Does it normally take that long for Esri to review bugs?

JoshuaBixby

Christian, thanks for the updates. Here's hoping "later this year" is more like summer than 12/31/2022. 🙂

Christian_Wells

I heard back this morning, @Bud - it sounds like they are already aware of the issue, and it's related to bugs going through the review and edit process multiple times. However, it is on their roadmap as they migrate the site to a new platform later this year.

In addition, @JoshuaBixby asked about the URL with the bug number instead of a GUID. This URL change is also planned for the new site migration and will help with SEO indexing.

Timelines can change, but this is being tracked, and I want to close the loop with both of you.

Christian_Wells

Thanks, Bud - I reached out to the web team on these as examples and waiting to hear back.

Bud

Why are some bugs googleable, like this one: BUG-000085841

But other bugs aren't googleable, like this one: BUG-000140702 ?
While that bug does have a permalink in the Esri Support Search site, I don't get any hits if I google the bug number or bug title.

Christian_Wells

Thanks, @JoshuaBixby - this feedback is helpful, and I will share it with our web team for the support website. I'm glad to hear it's consistent for My Esri.

JoshuaBixby

@ChristianWells , you seem to understand the support and defect processes well, so maybe you can have some influence on the following. It would be great if the URLs for bugs and defects were decipherable from knowing the bug or defect. For example, BUG-000094271 has a URL of support.esri.com/en/bugs/nimbus/QlVHLTAwMDA5NDI3MQ== . Whatever the rhyme or reason is behind turning "BUG-000094271" into "QlVHLTAwMDA5NDI3MQ==" isn't documented anywhere. For an organization with tens of thousands of GIS users that logs 50-100 defects and enhancements a year, linking internal documentation to Esri Support documentation is a very manual process. It would be nice if one could determine the URL by knowing the BUG or ENH number.

Update: For My Esri, both the old/classic UI and the new UI support URLs that are derived directly from bug or enhancement numbers. For BUG-000094271 and the My Esri classic UI, the URL is: my.esri.com/classic/#/support/bugs/BUG-000094271

Christian_Wells

I want to offer some insight into the process of logging a bug which explains why some bugs aren't visible. Some of the information below may be common knowledge, and I want to leave this here in case others stumble upon this thread.

Technical Support is the point of contact to validate and identify a defect.
1. We build a reproducible case with workflows, data, and software logs to verify a potential defect.
2. We also research our existing internal resources to see if a bug already exists and an accurate match.
3. Once we log a new defect or identify an existing one, we attach it to your account, and it shows up in My Esri for Authorized Callers.
  1. If you need Support access, you can request permissions through MyEsri by following these steps.
The defect then undergoes a two-step review process for technical accuracy and copy editing.
1. Some defects may need additional testing and validation during the technical review process, extending the review process.
2. Once the defect passes through our copy-editing process, it makes its way to the Support website, where you can search for bugs using this link. Esri Support Search. (Make sure the filter is set to "Bugs").

As @DanPatterson pointed out, one of the bugs can be found on the Support website. The other bugs you listed are in our technical review process, which is why they can't be found on the Support site.

@Bud, if you have specific questions about any of the bugs you listed or want to discuss this further, please feel free to send me a private message, and I'll be happy to connect.

BranislavBlagojevic

ESRI today... a name, a survivor from the seventies and eighties, which groans under the weight of its own semi-finished products, full of bugs! Of course, they know about it, but the fun is more complete with the users; it is more social, offers more Ideas, i.e. of well-paid user frustrations and...and justifies the existence of not only ESRI, but n similar ones. Business model or rot (???) Hmm...The first evolves legal responsibility/obligation! Rot just a fake story about respect, interaction with users and well-worn staleness.

ryanuthoff

You're not wrong. This is exactly why there needs to be more competition in the GIS industry. Maybe companies would put more emphases on making a quality product instead of only fixing bugs in future versions, forcing you to pay for maintenance so you have access to future versions, which just introduces more bugs and thus starting the cycle all over again.

Brian_Wilson

The Esri business model is entirely built on having you contract with them for support so you keep paying.

If the software was easy to install and easy to use, the demand for support would shrink.

If the software was not buggy there would be less need to stay on a contract, you could just stick with a version for years.

Because their services are expensive it creates a substantial market for consultants too.

I don't feel I am being cynical, it is just the model they chose. But I do think if the software itself was the product and not support contracts, they would put less focus an annual new feature list and more on making things work better.

Bud

Agreed. I think Esri could save a lot of money by making it easier to find bug info. If I googled an issue and there was already a bug for it, then I'd subscribe to the bug updates rather than submitting an additional ticket.

ryanuthoff

I'm sure companies have their reasons to not share their bugs with the public, I get it. But so much time could be saved if we had access to it. It's a waste of time for me to reach out to Esri support for something they are already aware of. Not to mention it's a waste of time for Esri support to spend time supporting end users when the bug has already been documented.

Bud

I think IBM does. I don't remember ever dealing with a bug that wasn't posted publicly. If a bug was created from one of my tickets, then it would be posted online.

Brian_Wilson

Does anyone outside of the open source community maintain a bug database with public access?

danretired

BUG-000140702: Right-clicking and selecting paste does not work whe.. (esri.com) is fixed at least, the other two didn't show

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.