Learn about the bugs fixed at this release and limitations that still exist in the software.
Minor releases and patches are cumulative. When you install a minor release or patch, the functionality of any minor releases or patches you may have skipped is incorporated. For example, if you update from version x.x.1 to version x.x.3, the update incorporates the functionality of version x.x.2. It is not necessary to perform an incremental update of version x.x.2 before installing version x.x.3.
The list of issues addressed describes bugs that were reported to Esri Technical Support and are fixed in the latest versions of ArcGIS Pro.
Issues Addressed at ArcGIS Pro 2.1.3
ArcGIS Pro 2.1.3 fixes the issues listed below. No new functionality is included with this patch.
A Python script in ArcGIS Pro working with a secure map service from a standalone ArcGIS Server with built-in security fails.
When a map or layer is copied, their metadata is not also copied. For layers with UseSourceMetadata=TRUE, the property is flipped when copied.
Vector tiles at LOD 15 of a flat cache contain features that should be filtered out at that LOD.
Drag-drop operation inadvertently deletes source data.
Issues addressed at ArcGIS Pro 2.1.2
ArcGIS Pro 2.1.2 fixes the issues listed below. No new functionality is included with this patch.
The following error, Failed to add data is returned when adding a .slpk file containing Lithuanian character such as Å¡ in layer name or pop-up configuration windows.
ArcGIS Pro 2.0.1 crashes when opening locator properties when language is set to German.
ArcGIS Pro's ArcGISIndexingServer.exe generates thousands of *_gdal.sqlite files in %TEMP% directory.
ArcGIS Pro crashes when editing annotation in Japanese.
The Extract Data tool runs slowly when you choose the boundary of the currently selected graphic.
ArcGIS Pro crashes when boundary labeling is missing a corresponding label from the pair.
ArcGIS Pro crashes when calculate field is used on annotation that is participating in a join.
The Summary Report tool cannot work with a report template if the name contains Japanese characters.
For comma delimited languages, placement patterns are lost when publishing to server if there is a decimal in the placement values.
There are gaps in vector tile viewing when cooking a tile set that has been diced to chop up a large polygon.
Display filters that transition from one geometry to another at an LOD boundary show both geometries.
In a map series, the spatial reference is not honored when based on an index layer field.
The map view intermittently does not refresh when using multiple mosaic dataset layers.
The Build Stereo Model tool requires an Advanced license level to build new stereo models and to rebuild existing stereo models.
The quality of the DSM product generated from satellite images using the Ortho Mapping workspace-based workflow degraded in ArcGIS Pro 2.1
Changing stereoscopic mode in the application options causes the stereo model selector to be blank.
ECW files cannot be read in ArcGIS Pro.
When a layout contains a TIFF with certain bit depths the application crashes.
GeometryEngine.Offset leaves extra segments in the output when offset type = OffsetType.Miter.
Issues Addressed at ArcGIS Pro 2.1.1
ArcGIS Pro 2.1.1 fixes the issues listed below. No new functionality is included with this patch.
ArcGIS Pro sometimes crashes when auto-georeferencing is performed.
Editing of Enterprise geodatabase data on Windows 7 clients may be slower if a matching connection file is not found.
Layers from a feature service in a CoreHost application cannot be edited.
Summary Reports crashes if the input feature layer was created using the Customer Derived Areas tool.
The Enrich Layer geoprocessing tool calculates incorrect values for Market Potential and Consumer Expenditure Index variables.
The mensuration input constraints are turned off by default. The constraints can be turned on in the mensuration options.
ArcGIS Pro crashes when focusing on Sentinel imagery in image space.
ArcGIS Pro crashes when a feature class or feature dataset that does not contain a valid extent is selected in the Clipping Geometry field of the Export Raster pane.
Attribute tables and the Attributes pane do not allow you to enter a minus sign (dash) for long or short integer field values.
Issues addressed at ArcGIS Pro 2.1
The list of issues addressed describes bugs that were reported to Esri Technical Support and are fixed in the latest versions of ArcGIS Pro. See What's new in ArcGIS Pro 2.1 to learn about new functionality introduced in this update.
Sliver edge polygon labels move when other label classes are turned on.
Arrange 3D symbols in a unique order within styles.
Symbology created using custom fonts displays incorrectly.
When renaming an item, you can't select the text you want to change using the mouse.
Spatial indexes are deleted when executing append as system administrator.
The thumbnail images for label placement styles are different in localized versions of ArcGIS Pro compared with the English version of ArcGIS Pro.
In a map series, when an index name field is numeric, and a page query is applied in a copy of the index layer, the displayed layer disappears.
Some multipatches show discontinuities when displayed with transparency.
When you create a new connection to an ArcGIS Enterprise server, the string "(user)" is included in the file name to indicate it is a user-level connection. This string is not localized.
There is a difference in number of Maplex labels placed due to minimum feature size not calculating the correct area.
The units string of the Tolerance parameter in the Simplify Polygon and Simplify Line tools is not localized.
If a visible scale range is applied to a value containing d', all unique values that include d' are set to the same visible scale range.
The Create Vector Tile Package tool fails with error 000623: Invalid value type for parameter in_map, when run as a standalone script.
Enhancement to the description of version conflict resolution in editing options.
The order of symbol classes is inverted in the Contents pane when multiple symbol classes are reordered by dragging and dropping in the Symbology pane.
An ArcGIS Pro layout exported with PDF layers and feature attributes does not maintain the hidden state of fields set in the feature class/shapefile when viewed in Adobe Reader.
ArcGIS Pro map series exports PDF with the default view in Adobe Reader as “actual size” instead of “zoom to page level."
Paste attribute does not work when attribute field contains special characters.
When using an Excel table with the Add Join tool, joined field values are changed to NULL if the attributes from the join field have non-English characters.
The returnUpdates REST call does not return updated endTime to reflect data added after a service is published as a web feature layer from ArcGIS Pro.
Map Service does not report timeInfo correctly for a query layer that is made time-aware by binding it to a parameter.
Coincident boundary labels are not placed, even when there is enough room.
Duplicate styles are shown after the display language is changed from English to another language.
Newly added display filters should be named New Filter.
MapBox-based basemaps added to a map from the Basemap gallery do not draw.
Values are incorrectly considered out of range when symbolizing polygons with graduated colors.
Styles cannot be removed from a project when the language is Japanese.
The word "Color" is not localized when you vary the appearance of symbols.
The Table To Domain tool crashes ArcGIS Pro if the input table contains numeric values for the Code and Description fields.
The wrong custom basemap name is shown when you use the Custom basemap in Map and Scene option.
Symbols rotated by attribute do not carry through to vector tiles.
Stroke symbol layer widths do not draw wider than 5000 in 3D symbols when the Display 3D symbols in real-world units option is used.
Running the Reconcile Versions tool on a version owned by an OS-authenticated user returns the error "Parameter is missing or invalid."
The Dashes effect contains incorrect template values for symbols originating from imported maps.
When symbolizing with manual interval with any number of classes, the topmost symbol class must have the option to Insert Break Above.
The documentation on the Create Vector Tile Package tool erroneously states that input maps must be WGS 1984 Web Mercator (Auxiliary Sphere) projection.
The required Layer.version parameter is not written for layers in the protocol buffer of vector tiles.
Dashed lines are displayed incorrectly in legends.
A misleading error message is displayed in the Properties window of a PostgreSQL table containing a field name that has more than 31 characters.
A ghost version appears when reconciling a version owned by an OS-authenticated user from the Geodatabase Administration dialog box.
Layer.getSelectionSet returns NONE when run from a script tool or as a stand-alone script.
Documentation for symbol layer drawing references an Advanced button that is not present.
Symbology that references a font that has a Scandinavian minuscule (ø) in the font name fails to display correctly.
Error results created when using the Query Attributes check contain invalid values in the Description property.
The color scheme is displayed incorrectly in the Contents pane with unclassed symbology.
When converting labels to annotation on a rotated map, the extent of the annotation feature class is incorrect when the Rotate labels with map option is checked on.
The Back button in Page Layout Element Property panes does not always work.
A vector tile layer displays incorrectly at high resolution for some map coordinate systems.
ArcGIS Pro crashes while accessing the Indexes property of a feature class joined with a .csv file through the Layer Properties dialog box.
The Disperse Markers tool fails to create an output if the reference scale is not set in ArcGIS Pro.
Round end dashed line symbology gets converted to a square end in legends.
When you search in the Catalog pane, the string "Search Results" appears at the top of the list of items that were found. The string is not localized.
When renaming an item, if you type a new name then click somewhere else in the Catalog pane or the catalog view, the rename operation would be cancelled. The rename is only successful if you press Enter.
There are unlocalized strings in mesh symbol properties.
In the Options dialog box, on the Metadata tab, the text refers to the Project pane instead of the Catalog pane.
Vector Tile Package output is incorrect when Flat tiling format is used.
ArcGIS Pro 2.0 and Desktop 10.5.1 users require explicit object-level privileges to view SQL Server geodatabase data in the Catalog tree. Instead, granting general database-level permissions should allow all objects to be visible within the Catalog tree.
There are performance issues when inserting a legend referencing a very large data set.
The Create Mobile Map Package tool fails if a feature class in the map participates in feature-linked annotation, but the annotation feature class is not in the map.
Parsing Degree Minutes Seconds with formatting tags in dynamic text causes the coordinates to disappear.
The Table To Excel tool fails when Input Table is a feature service and the Use domain and subtype description option is checked.
MapFrame Fixed Scale constraint is not working correctly.
Scale Bar numbering position offset Y is not working.
Printing drops features from the layout if there exists a selection set (selection feedback is included).
Add to Current Map fails for an OSA user connection.
When creating line features, the diamond cursor doesn't often display allowing the user to access the editing menu for deleting vertices.
In ModelBuilder, if a variable is set as a precondition and the precondition is removed, the variable still acts as a precondition.
In ArcGIS Pro 2.0.1, the Share As menu displays group names incorrectly if the names contain commas.
Unable to create features below the ground.
Tables that are selected with layers in the Contents pane should be included when shared as a web layer.
Simplify Line and Simplify Polygon fail on empty input files.
The generalization of a vector tile package alters the shape of features at large scales.
Identify Route tool does not work on an ALRS network when zoomed in beyond 1:300 scale.
Layer Files generated in ArcMap and opened in ArcGIS Pro do not honor transparency settings.
When ArcGIS Pro is set to use a language pack that does not match the language of the OS, searches do not return correct results.
Some Pipeline Referencing tools cause the application to crash when run through an edit session in a Python script.
Add the capability to provide paths to all datasets and geodatabases.
On a Japanese operating system, show "/" or "_" by default when adding a feature service layer from ArcGIS Enterprise to avoid " \" being replaced by "￥" as "￥" is a Japanese operating system specification for "\".
When using the Field Calculator on a hosted feature service in ArcGIS Pro, the process takes a lot longer than using the Field Calculator on a hosted feature service in ArcGIS Online.
SDK: Implement a convenient method on table for getting a count of the tables rows.
In the resource document link for Disperse Marker Tool, add a note to set a reference scale on the map prior to executing the tool.
Select Layer By Location selects incorrect records with the Are Crossed By The Outline Of option.
Update documentation about procedural layers to specify that they are for markers or fills.
Add the ability to reorder label classes.
This section lists known limitations by functional area of ArcGIS Pro. Software developers are actively working to fix these issues in future versions of the software.
Mapping and visualization
- Swipe does not work for group layers.
- In pop-ups, numbers in Arabic locale do not honor the machine locale settings.
- Measure does not work with maps that do not have a coordinate system.
- You cannot specify a selection symbol per layer. If you import a map with a selection symbol set for a layer, the main color is extracted from the symbol and set as the selection color for that layer.
- Heat map symbology for point feature layers in a scene are drawn using real-world units. If you switch to a different symbology method, new symbols will also draw in real-world units, possibly rendering them so small that they are difficult to see. To change this setting, right-click the layer in the Contents pane and click Properties. On the Layer Properties dialog box, click the Display tab and uncheck Display 3D symbols in real-world units.
- The color scheme applied to a layer symbolized as a heat map may appear differently when the map is shared to ArcGIS Online.
- The view extent can change slightly when zooming to a bookmark, or exporting an image or layout, from a scene in isometric view mode.
- An imported ArcMap, ArcGlobe, or ArcScene document containing an animation will not import the animation. The animation isn't imported because animations in ArcGIS Pro are built on a new framework that includes properties such as view extent, visible layers, and current map time in single keyframes. It is recommended that you remove ArcGIS Desktop animations before importing the document into ArcGIS Pro.
- Overlay elements cannot exceed 4000x4000 pixels. The map view and the preview window can draw overlays at different sizes. If an overlay exceeds 4,000 pixels, it will not be drawn.
- It is recommended you do not modify layers or map properties during the animation export process to avoid the risk of incorrect export or application hang.
- When you publish an annotation layer to a feature service, the visibility range from the annotation sublayers in ArcGIS Pro is not maintained. However, the visibility range from the annotation feature class annotation classes is maintained. The resulting annotation displays differently between ArcGIS Pro and the feature service when the annotation sublayer overrides the annotation class visibility ranges.
- The ArcGIS Coordinate Systems Data setup installs files that are required for some horizontal and geographic transformations and all file-based vertical transformations. In ArcGIS Pro 2.0, the setup had two options (per-machine and per-user) which were installed in different locations for each option. At the 2.1 release, the options are now split into two separate setup packages. When you install the ArcGIS Coordinate Systems Data setup, you are not warned to remove a previously installed setup. This is ok, the setup does not need to be removed. If you are using the per-machine setup, it can be used for ArcMap or Server 10.6 for Windows. If you have previously installed the per-user setup, you will be warned to uninstall it before installing the 2.1 version.
Interactive 3D Analysis
- The interactive analysis tools do not work in isometric view mode.
- The interactive viewshed tool may draw red analysis bands on the visible (green) vertical faces of features—such as building multipatches and extruded polygons— when the viewshed direction is tilted up or down away from horizontal. To avoid the issue, you can widen the viewshed's vertical field-of-view angle, rather than rotating the view direction.
- The application may crash when group layers containing KML data are reordered in the Contents pane.
- A crash can occur when a network link refreshes a time-enabled KML source file.
- Time-enabled KML in 3D does not work as expected when animated with the ArcGIS Pro time slider.
- Remote styles are not honored in some cases.
- Inline style elements on ground overlays are not honored.
- Tessellated lines in 3D may draw coarsely.
- The KML camera is not honored if it is at or below the ground surface.
- Rotated ground overlays are not yet supported.
- Some KML screen overlays are not yet supported.
- Some ground overlay image formats are not supported.
- KML scale and orientation properties are not honored on 3D model marker symbol layers.
- KML data written with dates that represent years under '0100' is not supported.
- KML data with incorrect XML date formats is not supported. For example, years must be represented by four digits.
- OLE objects, reference grids, and map frame clipping are not currently supported and are dropped when you import map documents into a project. Check the Notifications on import of a map document for specific items that may have been dropped.
- Attribute table, table frame button, and other layer options are disabled after adding a single layer to a map via the layout view.
Symbols and symbology
- Polygon features in the 3D Layers category of a scene drawn with proportional symbology using 2D symbols are not extruded when the Data represents property is set to Height.
- Values less than 1 are excluded from the legend in the Contents pane and in a layout for layers drawn with relative-sized proportional symbology when a maximum size is specified.
- Rendering may vary unexpectedly for the same symbol drawn in a 2D and 3D context. See Unsupported symbol drawing for more information.
- Custom geometric effects are stripped from symbols when they are converted from ArcMap to ArcGIS Pro. There will be no indication that this has occurred, and symbol geometry logic may therefore be disrupted.
- In 3D layers, the Randomness symbol property marker symbol layers in a polygon symbol cannot be connected to a data attribute.
- Time is not supported across linked views.
Manage data and geodatabases
- Relationship classes that are attributed or have a cardinality of many to many are not supported for branch versioning.
- When using the Topology wizard to create a new topology, if the input dataset and feature class are stored in an enterprise geodatabase, and have been newly created in the same session of ArcGIS Pro, the new empty topology dataset may become corrupted. A workaround for this issue is to remove the feature class from the map, or close and re-open ArcGIS Pro before using the topology wizard (or when running the Add Feature Class to Topology tool) to create a new topology.
- With Branch versioning, if the owner of a private version is changed, the version is unusable until the Server SOC is restarted.
- After you reconcile and post a branch version with Default then change to the Default version, sometimes the changes may not appear. The workaround is to right-click on the layer(s) and select Properties > Cache > click Clear Cache. Another alternative is to save the project, close and reopen ArcGIS Pro, and the changes will then be displayed.
- If you attempt to make a connection using a connection file created with ArcGIS Desktop in ArcGIS Pro, it will fail if the connection file has an extension in UPPERCASE (for example, .SDE). If you change the connection file extension to lowercase (for example, .sde), the connection will succeed.
- Geoprocessing tools for geodatabases and databases:
- The Alter Field geoprocessing tool lists the field alias instead of the field name in the field name parameter.
- The new fields that may be added to a table by executing the Enable Editor Tracking geoprocessing tool will not be reflected in the table until the project is closed and reopened.
Index and search data
- Items are automatically indexed when maps, folders, and databases are added to a project. Content is indexed and search terms are evaluated based on rules for the language ArcGIS Pro is set to use. If you create a project and search for items using the English version of ArcGIS Pro, the search results will be based on English rules. If you later set ArcGIS Pro to use a different language, at first the search results are unlikely to return the expected results. The search terms will be evaluated based on rules for the new language, but the index will have been constructed to support English content. The next time the index is updated, content will be indexed appropriately for the new language and searches will return the expected results.
- Reviewer batch jobs:
- Batch jobs added from a UNC path are copied into project packages when shared using the Share as a Project Package tool with the Share outside of Organization option unchecked.
- Reviewer rules:
- Reviewer rules are not persisted when layers are shared using the Sharing as a Layer Package tool.
- Reviewer rules based on the Feature on Feature, Duplicate Feature, Invalid Event, or Event on Event check will become invalid when a participating layer is copied from one map to another.
- Reviewer results:
- The Add Session context menu item is not disabled when there is an invalid Reviewer workspace connection.
- Reviewer sessions added from a versioned geodatabase will become invalid when the version is changed to the project's Database connection.
- Column sorting in the Reviewer Results pane is not supported for keyboard accessibility.
- The Update Results pane does not support undo or redo of edits.
- A metadata result's corresponding data source is not automatically displayed in the Catalog view metadata panel when opened from the Reviewer Results pane.
- Geoprocessing tools:
- The Delete Reviewer Session geoprocessing tool's Session parameter does not support the selection of multiple items for deletion. Session items must be added individually to the Delete Reviewer Session geoprocessing tool.
- The Write to Reviewer Table geoprocessing tool fails to run as a stand-alone script in Python or the command line if the parameter value for the Origin Table Name, Review Status, Subtype, Notes, Severity, or Check Title parameter is a string data type.
- The Enable Data Reviewer geoprocessing tool's Register as Versioned parameter does not support versioning of the Reviewer tables when creating new or upgrading existing Reviewer workspaces for PostgreSQL. To manually register the Reviewer tables as versioned, right-click each of the following tables in the Catalog pane and click Manage > Register as Versioned.
- The Flag Missing Features tool does not support undo or redo of result creation.
- Sometimes validating network topology will result in the process timing out. The error message will read, "Validate Network Topology - Edit operation failed. The server took too long to answer. The client has timed out. (status code 28)." Although the client has timed out, the process will continue to run on the server for up to 10 minutes.
- In some workflows, it might be possible to end up with a version that is locked for every user, even the version owner. This workflow generally follows the pattern of creating a new version in a map, making some edits, and saving those edits. Next, a new project and map is opened to the same version created in the previous session. You may encounter a locked version.
- Viewing associations will fail when the map's spatial reference is different from the utility network spatial reference.
- Adding an inline network attribute which exceeds the 64-bit limit results in invalid trace results.
- The Update Is Connected geoprocessing tool will sometimes crash on large networks.
- The Validate Network Topology geoprocessing tool will sometimes time out when executed from the Utility Network Data tab on the ribbon.
- Some functional issues and limitations arise if multiple utility networks are added to a map. Tools such as Trace Locations and Modify Associations cannot operate on the second utility network in a map.
- The addition of a utility network layer to a map with another utility network layer with the same version is not blocked.
- Validation of a utility network will fail if the coordinate system of the map does not match the coordinate system used to create the utility network.
- Appending data into a utility network (with the network topology enabled or disabled) should be detecting features that are added outside the extent of the utility network and fail.
- A trace error is not returned if a subnetwork trace discovers both a source and sink in a subnetwork.
- The placement of starting points and barriers is not blocked on these utility network feature classes: the structure boundary feature class, the device assembly feature class, the subnet line feature class, or asset group or asset type values in the structure junction or structure line feature class which have an association role of Structure.
- When you attempt to remove a subtype on a utility network feature class which is required for the utility network, an error number of '999999' is given.
- The utility network will allow you to create multiple asset group names with the same value for a feature class. This should be blocked, but isn't.
- When you run Export Subnetworks, the Subnetworks table should be refreshed.
- When importing rules or associations files, when a domain value has a comma embedded in double quotes, such as, "Single Phase, overhead", this will cause the application to crash.
- No errors are generated when you enable or validate a network topology with ambiguous conditions if that utility network has no rules. For example, placing geometrically coincident lines of different types creates a condition of ambiguous connectivity.
- The Update Subnetworks tool doesn't refresh the list of dirty subnetworks.
- When you rename the utility network layer, it is unchanged in the map.
- Executing a trace only creates new selections. It doesn't respect the core selections such as new, add, remove, and select from.
- The Validate Network Topology tool operates on 2D maps with z-values. However, this tool does not run on a 3D map of the same data.
- Deleting an asset type that has a rule assigned to it causes the Export Rules tool to fail with a '999999' error instead of a more informative error.
- Importing an XML workspace fails against an XML workspace from a utility network created with the Export XML Workspace tool.
- The Export Associations, Export Subnetwork Controllers, Import Associations, and Import Subnetwork Controllers tools do not run in services.
- When you validate a topology which is disabled, the success toast message displays.
- When you run the Validate Topology tool, the table view for errors doesn't refresh.
- When configuring trace parameters that use network attributes against a domain, the domain description is shown but not the domain value.
- It is not yet possible to publish a trace as a geoprocessing service.
- Some uncommon workflows can result in the utility network resulting in a state of mixed versions. The utility network layer may point to the default version while the utility network feature classes may point to a named version.
- The execution of the Create Utility Network tool checks for the privilege Publish server-based layers but not the additional permission of Create, update, and delete. Also, this tool does not check for the portal to be an ArcGIS Enterprise portal and should not allow execution if the active portal is ArcGIS Online. Also, this tool does not check if the federated server is at version 10.6.
- When subnetwork name fields are added while adding tiers for hierarchical domain networks, the subnetwork name fields which are added should not support NULL values and the default value should be Unknown.
- When you change a version, the trace locations are not cleared.
- When adding a tier, entering a Subnetwork Field Name does not check for bad field names, such as a field name beginning with a number.
- When using the SDK, if you are in an open edit session, calling ValidateNetworkTopology crashes.
- When using geoprocessing tools, you cannot browse to a service based utility network portal item as the input network parameter. To add the service based utility network as an input, use the utility network layer in the map or drag and drop the utility network portal item from the Catalog pane onto the input parameter.
- When searching the contents of the active portal, you can search for web layers and browse to them to see the layers, tables, and images they contain. However, you can't search directly for the layers, tables, and images contained by a web layer. If a web layer doesn't include providing data as one of its capabilities, the layers and tables it contains can't be added to a map.
- When searching for items on the local file system, if you search using text that occurs before or after the period character (.) in any field in the item description (including the item's file name), you will not be able to find the item using that text unless it also occurs in the item description separately, such as in the item's keywords. For example, if the description includes the text June.16, the item will not be found when searching for June or 16. You would only be able to find the item by searching for the entire string June.16. In contrast, when text includes the underscore character (_), you can find the item using only the text that appears before or after the underscore.
- When you are not signed in to the active portal but you are using it to work with public items, you cannot not view metadata for those items. The error message "This item cannot have metadata" will appear in the Details panel instead. Sign in to the active portal to see the item's metadata.
- If you have a model open in the Model Builder view and the Metadata Editor view is also open allowing you to edit metadata for the same model at the same time, the changes that are saved last will replace any previous changes that were made. For example, if you save changes to the model parameters in the Model Builder view, then save changes to the model's metadata using the Metadata Editor view, the metadata changes are saved and the model parameter changes are lost. The reverse is also true: if you save edits to the metadata first, then save changes to the model's parameters, the parameter changes are saved and the metadata edits are lost. This problem also affects tasks if you edit the task and its metadata at the same time. This problem also affects maps if you edit the map's properties in the Properties dialog box and also edit its full metadata at the same time.
- When a portal item does not have full metadata, and the tags provided on the Item page include spaces, commas will appear between each word in the tag when you view the item's metadata.
- There is no way to import existing metadata to a new item using ArcGIS Pro. Also, you can't export metadata to the XML format associated with your current metadata style.
- When maps and layers are shared to the active portal, their metadata is not currently transferred to the new portal item.
- Some items support metadata, but their metadata can't be accessed in ArcGIS Pro. For example, groups in the active portal have a description that isn't currently displayed in the project view. These items currently show the same message as other items that can't have metadata, such as tables in SQLite databases and Excel worksheets.
- When editing metadata in the metadata view, the validation error messages displayed at the top of a page don't remain visible as you edit the item's metadata; they move out of view as you scroll down to the bottom of the page. Also, you can't click the validation error messages to get to the area of the page where there is a problem to fix.
Analysis and geoprocessing
- The Multipatch to Raster tool may cause a crash when an empty multipatch feature class is provided as the input.
Imagery and Raster
- Changing the bands of a Composite raster in the Contents pane does not work properly.
Workaround—Change your bands from the Symbology pane.
- After creating image control points using tools on the Georeference tab, Save As New cannot save a georeferenced raster to BIL\BIP\BSQ formats
Workaround—Save it as TIFF and use Copy Raster to convert it to BIL\BIP\BSQ format.
- The Move editing tool cannot move 3D features in the Z direction in stereo map.
Workaround—Use the Vertices editing tool to edit the Z coordinates of the feature.
- The stereo model does not display in the Stereo Map for stereo pairs with large intersection angles.
Workaround—Rebuild the stereo model for your mosaic dataset with an angle range smaller than 30 degrees.
- A stereo model can be rebuilt using an existing stereo model table with a Basic license. However, a Standard or Advanced license is required to build an initial stereo model.
- Raster catalogs have been deprecated in ArcGIS Pro. You will need to migrate your raster catalog to a mosaic dataset.
- It is recommended that you do not process the global functions on your local machine unless your image datasets are smaller than 500 MB. Global functions should only be processed as Raster Analysis tools in Portal for ArcGIS.
- The Make NetCDF Table View tool may create incorrect time values when "noleap" is used as the calendar attributes of the time variable in the netCDFfile.
Spatial Analyst toolbox
- The Cost Connectivity tool may not connect the paths properly for polygon sources when the coordinate system of the input regions and cost raster are different. Also, the tool will fail when the scratch workspace is set and the default output name is used. The tool will work if the output is instead written to a different workspace.
- The Create Signatures tool may crash when the training samples contain NULL values in the sample field.
- The Euclidian Distance tools with the Environment Mask set may have incorrect statistics in the output raster.
- The Extract Multi Values to Points tool fails when the input points feature is an XY Event layer.
- The Sample tool may fail on an input mosaic dataset raster.
- The Topo To Raster tool generates incorrect output when multipart features are used as input. If individual streams in the input are not single polylines, parts of a stream network may be ignored.
- Workflow connection:
- When you update the data workspace login, the login is not applied immediately. You must restart ArcGIS Pro for your updated credentials to take effect.
- Packages created in ArcGIS Pro can only be opened in ArcGIS Pro. If you have ArcGIS 10.x installed on the same machine, and you double-click a package created in ArcGIS Pro, you will receive a message that the package is invalid.
- When sharing a web layer with a pop-up that is configured to include an image sourced from an attachment, the image is dropped from the web layer.
- When using the ArcPy mapping method CreateWebLayerSDDraft, metadata and folder options are not honored.
- Overwriting a service name in the Upload Service Definition geoprocessing tool only modifies the service item's title. It does not modify the service item name.
- Feature layer pop-up configurations are lost when overwriting the web layer.
- Map image layers that have had their title changed cannot be overwritten.
- The parameter staging_version is only available through the Python API for StageService. This parameter is required when staging a feature, tile, or imagery layer for ArcGIS Enterprise.
- Referencing registered data in a Teradata database can fail or result in an empty service. Instead of referencing the registered data, it can be copied.
- Registered data stores that have different database connections for the publisher's machine and the server cannot be referenced when sharing to Portal for ArcGIS 10.4.1 and earlier.
- Tile layers cannot reference registered data sources. To reference registered data using a cached web layer, share a map image layer that draws using tiles from a cache.
- When sharing a scene to Portal for ArcGIS 10.4 or 10.4.1 with a mosaic dataset as an elevation source, you cannot modify the minimum level of detail of the web elevation layer to ensure caching doesn't occur past the minimum visibility.
- When connected to a ArcGIS Enterprise 10.5 portal that uses basic authentication, the portal must have the enableRemoteTokenUserValidation property enabled to be able to switch between users.
- To share to a federated server, the web adaptor must have admin access enabled.