BUG-000113968 for ArcGIS Pro

Bug ID Number	BUG-000113968
Submitted	May 15, 2018
Last Modified	February 14, 2025
Applies to	ArcGIS Pro
Version found	2.1.2
Operating System	Windows OS
Operating System Version	7.0 64 Bit
Status	Non-Reproducible

Additional Information

This problem cannot be reproduced as described using the current development version of ArcGIS Pro 2.3 software. Many changes and improvements were made in ArcGIS Pro 2.2 concerning how metadata is handled when it is imported, which probably accounts for the change in behavior. The problem cannot be observed with shapefiles, feature classes, or any other data that has metadata. A problem can be observed in ArcGIS Pro 2.3 when an un-escaped ampersand is present in the text of the description for an MXD, its layers, or an LYR file (and presumably an LPK that includes such a layer file) where the ampersand was provided in the ArcMap map or layer properties dialog box only. What happens is no content appears in the description if an un-escaped ampersand is present. However, the content can be displayed successfully if users view the full metadata for the map or the layer in the Catalog view. Editing the metadata using the ArcGIS Pro metadata editor corrects the problem. If the map's metadata is edited using the ArcMap metadata editor before the MXD is imported, the problem is corrected and no problems are observed. However, it is impossible to correct the problem for layers within an ArcMap document in ArcMap - the problem can only be corrected in ArcGIS Pro after the MXD is imported because map layers do not have metadata in ArcMap. The presence of the un-escaped ampersand--when it is transferred to the ArcGIS Pro map's metadata or the ArcGIS Pro layer's metadata--causes metadata to be invalid and as a result there can sometimes be problems processing the metadata, as observed in the Properties dialog box, when allowances aren't made for this scenario. This is an existing issue in our Product Plan.