The significance of the ArcGIS Pro 2.0 version number
At the ArcGIS Pro 2.0 release, the version number changed from 1.4.1 to 2.0. ArcGIS Pro adheres to the semantic versioning specification, which defines versions in a "major.minor.patch" versioning scheme. The 2.0 version of ArcGIS Pro is a major release. In contrast to a minor or patch release, a major release introduces backwards incompatible changes. These include compatibility changes for ArcGIS Pro project (.aprx) files and other ArcGIS Pro document formats, and breaking API changes in the ArcGIS Pro SDK for Microsoft .NET. The list below provides additional detail regarding compatibility changes between older versions and ArcGIS Pro 2.0.
- ArcGIS Pro document files (project, project template, layer, map, and layout files): ArcGIS Pro document files are forward and backward compatible between minor releases, such as 1.4 and 1.3. Since ArcGIS Pro 2.0 is a major release, these files will be forward compatible only. This means future versions of ArcGIS Pro will be able to open them, but older versions such as 1.4 cannot. You cannot directly save a copy of an ArcGIS Pro 2.0 project that can be opened with any 1.x version of ArcGIS Pro. A project package created using ArcGIS Pro 2.0 contains 2.x and 1.x versions of the project, so it can be opened in any version. The appropriate project for the version of ArcGIS Pro you are using will be opened. For more information, see Save a project.
- ArcGIS Pro add-ins: ArcGIS Pro 2.0 will not load add-ins built for earlier versions. Please contact your add-in provider for an updated version of the add-in. If you are a developer, you will need to rebuild your add-in using version 2.0 of the ArcGIS Pro SDK for Microsoft .NET. For additional information, see What's new for developers.
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.0.1
ArcGIS Pro 2.0.1 addresses error reports for software instability submitted by users since the release of ArcGIS Pro 2.0.
ArcGIS Pro crashes when using the Create Scene Layer Package tool with multipatch data that uses procedural symbols.
Location Referencing tab does not appear in ArcGIS Pro if ALRS layers are copied and pasted from another map.
Renaming a table in the Contents pane in ArcGIS Pro breaks the Source tab, which is in the table's Layer Properties dialog box.
In ArcGIS Pro 2.0.0, the raster item preview is not displayed after selecting and displaying the data for the second time or subsequent times.
Using the not equals (!=) relational operator in the Python window throws a syntax error.
ArcGIS Pro Layout.exportToPDFdoesn't work when run from Windows Service.
If a scheduled task is created to run when the user is logged out of a Windows machine, Pro Layout class export functions (for example, exportToPDF) do not work.
Cancelling out of the Browse 3D model files dialog box when using the Replace MultiPatch tool causes ArcGIS Pro to crash.
Cloud Raster Format (CRF) output results in a long processing time due to large incorrect bundle size.
Adding or modifying a field or domain through the Fields or Domains view can leave locks that make the data uneditable until you restart ArcGIS Pro.
The Append geoprocessing tool can be slow when used with data that has attachments. All attachments are queried even if only a few input records are selected.
Interacting with the vertical range slider on the ribbon causes ArcGIS Pro to crash.
ArcGIS Pro crashes upon opening if the add-in folder is not accessible.
Issues addressed at ArcGIS Pro 2.0
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.0 to learn about new functionality introduced in this update.
Kernel Density does not honor the output projection specified in the Environment settings.
The Reclassify tool rounds the original values instead of reclassifying to new values if the input is a double precision raster.
ArcGIS Pro does not localize the input field names for the World Geocode Service when using the Geocode Addresses geoprocessing tool.
Output parameters in the Locator Properties dialog box are not translated in localized versions of ArcGIS Pro.
In the Weighted Overlay tool, the error message about the sum of Percent Influence Weights or the pop-up text of Evaluation Scale are not translated in localized versions of ArcGIS Pro.
The No test field mapping option in the Append tool does not automap to the same field name if the naming convention differs.
Unable to license the application if the user name begins with numbers.
Provide a correct error message when trying to geocode a table and the user doesn’t have privileges to geocode.
Rectangular multipatches exhibit interior shadows and fragmentation when transparency is enabled to approximately 40 percent.
The Point Statistics tool does not properly handle decimal values for the neighborhood shape parameters when the Units type is set to Map.
When publishing selected layers in a map, include tables only if they are related.
The Viewshed tool may fail on a very large dataset with the following error message, "ERROR 010067: Error in executing grid expression. Bad access location in visibility map (VMPUT)."
The output from Zonal Statistics may be all NoData with the Maximum statistic type.
Raster to ASCII tool output is not as expected in certain circumstances. With the Regional setting set to a language that uses a comma locale, the Decimal symbol to the point character, and the Digit grouping symbol to the comma character, the output from the tool will have commas instead of the expected points for decimal values.
When creating an animation, the extent the user establishes and sees in the creation and preview of the animation does not match the view extent in the exported movie, which limits the ability to accurately and efficiently control the appearance of the movie.
The sublayer names of a mosaic dataset are not translated.
When run as a standalone script, the Create Vector Tile Package tool fails with the following error message, "ERROR 000623: Invalid value type for parameter in_map."
Vector tile packages with international characters in the file name do not draw in ArcGIS Pro.
Using the Merge tool on feature classes with attachments results in a 999999 error.
Unable to license the application if the user name is all numeric.
Layouts exported as PDF with layers and feature attributes do not maintain the hidden fields set in the feature class or shapefile when viewed in Adobe Reader.
The Manual Interval classification method does not allow you to insert a class break for a raster.
For the Feature To Raster and Polygon To Raster tools on certain non-English languages, the attribute table may be empty when the output is to a file-based raster format such as Grid or Tiff.
Map series exports PDFs that open in actual size mode instead of zoom to page level.
The Expand tool may fail on certain datasets with larger values for the Number of Cells parameter.
The value for the Interval Size reverts to 1 in Defined Intervals classification, when the value is set to less than 1.
The Locator Properties dialog box title is not translated.
Date Fields label is hardcoded.
Creating a composite address locator that includes a portal item locator results in an invalid locator.
The FeatureToRaster tool is much slower than the PointToRaster and PolygonToRaster tools.
When defining the license manager server for Concurrent Use licensing option, ArcGIS Pro does not accept a server name longer than 30 characters.
Unable to type in text boxes after pressing Alt key sequences multiple times.
Some tools on the Imagery tab are enabled when there are no raster layers in the map.
Map Series should use the description part of the coded value domain similar to how it is used in pop-ups and tables.
MapBox-based basemaps added to a map from the basemap gallery do not draw.
Feature templates are not re-created when the layer's renderer is changed.
Reclassify does not change NoData cells when there is a single remap entry that remaps NoData to some other value.
A clip with projected on-the-fly data is okay if the input is projected, but it is not okay if the clipped features are projected.
When using ArcGIS Online Enterprise logins with public key infrastructure (PKI), the PIN dialog box is hidden behind the application.
For the Viewshed tool on non-English language pack, the output name is added to the Contents pane but the raster not added to the display.
KML files created using the Layer to KML tool do not display correctly if input data is not in WGS84 (WKID: 4326).
A sample record in the Ortho-Mapping workspace displays Phi field even when the Load orientation option is turned off.
Georeferencing using the Save as New option turns NoData cells to 0 (zero).
Some error messages in the Geostatistical Wizard are not completely localized.
You are unable to use unfederated geocode services as utility services in Portal for ArcGIS 10.5 as input address locators in Geocoding geoprocessing tools.
When sharing a layer as a vector tile layer, some labels are not translated when using the Japanese language pack.
Unable to add a locator to a project from a portal using the Locate pane.
In a map series, when there is more than one map frame on the layout, switching the selected map frame for the map series results in incorrect behavior when navigating the pages.
3D line symbols cannot be larger than 5,000 meters when displayed in real-world units.
Graduated Colors/Graduated Symbols symbology renderers are not exported when exporting a point feature layer to KML.
Dash template values in line symbols are incorrect in imported .mxd documents.
The Classified renderer has a few problems with the Manual Interval method.
When the Append tool is used in ModelBuilder, creating a variable with the Input Dataset and Target Dataset parameters and setting the Schema Type to No_Test cause the drop-down list of fields on the Source tab to be empty.
Required Layer.version parameter is not written for layers in the protocol buffer of vector tiles.
The Append tool fails when source and target datasets contain a GlobalID field, and the feature service property supportsApplyEditsWithGlobalId is true on the target feature service.
In dynamic text, the domainlookup="true" fails to apply the domain description.
Switching layers on and off during geoprocessing in ArcGIS Pro prevents layers from drawing until the tool or model stops.
Setting names of participating locators are not translated to Japanese on the Locator Properties dialog box of composite locators when using the Japanese language pack.
The Use Multithreading Performance option on the Locator Properties dialog box of a composite locator is not translated when using the Japanese language pack.
ME- (IME-Japan-Ctrl key) Unable to edit a multipatch feature in ArcGIS Pro (unless pressing Ctrl with Japanese Pack) on Japanese operating system and changing IME keyboard.
When an ArcGIS Online geocoding utility service references a geocode service based on reference data in a custom projection, ArcGIS Pro crashes when the utility service is used for search in the Locate pane.
The color scheme for unclassed symbology is displayed incorrectly in the Contents pane.
Weighted Sum may produce an incorrect result when a non-valid field in the input raster is selected.
When the Locate tool in ArcGIS Pro is configured to find features of a layer, the tool does not find the feature if the search attribute has the Long data type and contains more than five characters.
The Reclassify or Weighted Overlay tools crash when the tool is run from the dialog and the remap table specified a string field with a large number of characters.
IsoCluster tool fails in Python when the output from Make Mosaic Layer is used as input.
The Con and SetNull tools return the incorrect result when the input is a float raster and the Expression where clause is "Value" <> 0.
Math tools crash in ArcGIS Pro when the input is a raster layer made with a query string.
The Weighted Overlay raster function does not honor the RESTRICTED keyword.
Cost Connectivity tool will create an invalid network in the output when two input regions touch.
Local functions are not honoring the Compression environment setting.
Nesting arcpy local functions may cause a crash if the Scratch workspace is in_memory.
Lookup tool may fail when saving to Grid raster if there is a large number of records in the attribute table.
The NumPyArrayToRaster function creates incorrect output when the input is a large floating-point numpy array.
Point, Polyline, and Polygon To Raster tools revert the specified output raster name back to the default if other parameters were changed.
IDW, Nearest Neighbor, and Trend, when the Extent environment is specified in the tool dialog, only the points within that extent are used. In scripting and in ArcGIS Pro, all the points are used.
Reclassify tool produces incorrect output if the input raster does not have a spatial reference.
Kernel Density may produce incorrect results when the Geodesic method is used and the output is an ArcSDE raster.
Viewshed, Observer Points and Visibility tools may produce incorrect output if the Mask or Cell Size environments are set, or if a polyline dataset is used for the input observers.
Reclassify tool dialog does not allow a remap table with a single entry to be used for remapping NoData cells to another value.
Sample tool extracts incorrect time dimension values when there is more than one sample point, and input is a netCDF raster layer with both time and other dimensions.
Geostatistical Analyst Layer to Points tool with a validation field and an EBK Regression Prediction Layer does not produce the expected error.
Extract by Circle, Extract by Points, and Extract by Polygon may create output that is all NoData if the Coordinate system environment is not set to the input data.
The Geostatistical Analyst Wizard crashes if there are two layers with same name.
Tools that output to Grid raster may fail when attempting to use non-English characters in the output name.
EBK Regression Prediction tool should return an error if a specified Input Explanatory Raster does not exist.
A crash may occur when accessing a raster object created by the NumPyArrayToRaster function when the Extent environment is set outside the extent of the input NumPy array.
Simple kriging with probability output in the Geostatistical Analyst Wizard triggers an error when trying to optimize the model.
Fill tool with the Z limit specified may give incorrect results when there is a large number of sinks.
Local functions in arcpy.sa fail when accessing bands from a multiband raster.
Kernel Interpolation gives incorrect geostatistical layer output when points and barrier feature class are in different projections.
An enterprise geodatabase cannot be used as the default geodatabase for a project.
Provide a command line installation option to specify a licensing portal URL.
Region Group does not retain the original input values in the link attribute if the input raster has cell values greater than 32767.
The Nibble tool calculates incorrect values for areas adjacent to NoData cells in the input raster.
The Path Distance tool generates an output raster with cell values of all zero when the Table option is used for the Vertical Factor parameter.
The sections below list 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
Web feature layers (feature services)
Feature caching has been disabled for feature layers when the data source is a map service sublayer. To determine if a map service is being used, open the Layer Properties dialog box; click the Source tab; and, under the Data Source group, look at the Url property. If the URL contains MapServer, the data source is a map service sublayer.
For services that do not support pagination, the number of records in use by the application (such as through drawing, querying, or geoprocessing) will not exceed the value set in the maxrecordcount property on the service, which is usually set to 1,000 or 2,000 records. This issue is now known to have existed since ArcGIS Pro 1.0.
Maps and scenes
- 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.
- When you import a coordinate system, the spatial reference information (domain, resolution, and tolerance) is not imported with it. These properties are needed for layers, but not for maps. They are necessary for editing workflows. To work around this, use the Project tool to project data, and then copy and paste the feature dataset or feature class path into the coordinate system parameter text box, instead of importing a coordinate system.
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.
- Lines symbolized with proportional symbology in the 3D layers category of a scene will not draw with different widths until you change a proportional symbology property, such as Minimum size. If you vary symbology by size on lines or polygon outlines in the 3D category, they will not draw with different widths at all.
- 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.
- Alternate symbols (different symbols drawn at different scales) do not participate in symbol layer drawing.
- In 3D layers, the Randomness symbol property marker symbol layers in a polygon symbol cannot be connected to a data attribute.
Labeling and annotation
- It is not possible to set placement positions for polygon labels in 3D.
- One-digit numeric text will not display Eastern Arabic digits when the locale or text symbol settings are set for this type of display.
- Converting labels to annotation for a rotated map is not supported.
- Graphics and grouped graphics are not supported in the upgraded ArcGIS Pro version of annotation.
- If you see error 000204: Error creating input feature cursor while upgrading your annotation feature class, restart ArcGIS Pro and upgrade the feature class again.
- 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.
- In some cases, the application can crash when you click Refresh on a KML layer with frequently updated network links.
- 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.
- 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.
- Windows Media Player may not play exported animation video from ArcGIS Pro. If Windows Media Player or another common video player does not play your animation video exported from ArcGIS Pro, you need to download and install the missing codec files. (It may be missing the necessary codecs.) See Common animation questions to learn more about potential issues with viewing an exported animation.
- Bookmark files (.dat) from ArcGIS Desktop cannot be imported into ArcGIS Pro. To create an animation in ArcGIS Pro from bookmarks used in a desktop document, they must be part of the map, globe, or scene document and the document imported into your project.
- 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.
- Time is not supported across linked views.
- The time slider does not initiate the first time it is enabled for mosaic datasets. If you reopen the Layer Properties dialog box, disable and reenable time, and click OK to close the dialog box, the time slider (and the contextual Time tab on the ribbon) appear.
- The range slider is not supported across linked views.
- When different ranges are set in multiple views of the same map, geoprocessing tools only use the first view's range filter settings. This also applies to time filter settings.
- Range layer properties cannot be defined for multiple layers at once.
- Range slider properties are not persisted per range when multiple ranges are defined.
- Expressions are not yet supported for range definitions.
Manage data and geodatabases
- Running more than one instance of ArcGIS Pro can degrade performance when using Cut or Copy to copy a large number of features to the clipboard.
- The Keep source attribute values check box is disabled on the Paste Special dialog box when you paste annotation features.
- Reviewer batch jobs:
- The Connectivity Rules, Metadata, and Custom check types are not supported and will be skipped during batch job execution.
- Batch jobs added from a UNC path are copied in 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.
- Unsaved feature edits cannot be validated using Reviewer Rules.
- Reviewer results:
- Session Results project items are not included when shared using the Share as a Project Package tool.
- Session Results project items are not included when shared using the Create Project Template tool.
- The Add Session context menu item is not disabled when there is an invalid Reviewer workspace 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.
- 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 Flag Missing Features tool does not support undo or redo of result creation.
- 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. Global functions should only be processed as Raster Analysis tools in Portal for ArcGIS.
- Global functions do not support geoprocessing environments.
- If a project is saved with a selection set and reopened, the GeoName To Features tool needs a new selection set to enable the Apply button.
- The GAIT geoprocessing tool supports vector application schemas only and cannot be used to validate TanDEM-X High Resolution Elevation Data Exchange (TREx) Program data.
- The GeoNames To Geodatabase geoprocessing tool is failing validation for the GeoNames Source File parameter and the GeoNames Table Name parameter when the parameters are set by dragging them from the Catalog pane.
- The Unzip MGCP Cell And Import geoprocessing tool fails on Windows 10 Simplified Chinese Language when ArcGIS Pro is installed from the Simplified Chinese localized setup.
- 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.
- 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 Portal for ArcGIS.
- 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.
- Feature layers that reference registered data cannot have sync or export capabilities enabled when sharing to Portal for ArcGIS 10.5 or 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 Portal for ArcGIS 10.5 portal that uses basic authentication, the portal must have the enableRemoteTokenUserValidation property enabled to be able to switch between users.
Analysis and Geoprocessing
- The Point To Raster and Point To Polygon tools may produce incorrect output if the Geographic Transformation environment is set.
- The Make NetCDF Table View tool crashes if the input variable is a scalar variable.
- It is not possible to overwrite existing Grid rasters from a tool dialog. The output parameter only accepts the bands within the Grid.
- The Cost Connectivity tool fails when attempting to use polygonal features as input regions when only the Basic or Standard licenses are available.
- The Extract Multi Values to Points tool may not extract the correct values when the input raster is an image service. It may fail when the input points feature is an XY Event layer.
- The Math tools cause the application to crash if raster function layers that point to Image Services are used as input.
- The Point Solar Radiation tool encounters an error if the output coordinate system specified in the Environment has a different spatial reference than that of the input points. If an Extent environment is set, the tool may not execute.
- The Reclassify tool executes successfully with an empty remap table from the tool dialog. A valid reclassification is required for the tool.
- The Sample tool gives incorrect output when an input Multidimensional raster is used in Comma locales.
- The Solar Radiation Graphics tool fails when the output spatial reference environment is set to be different than the input data.
- The Spline with Barriers tool generates unexpected NoData cells under certain condtions.
- 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. The tool crashes the application when complex streams are used in conjunction with lakes and point elevation inputs.
To view the PDF document, you need a copy of Adobe Acrobat Reader, which you can download for free from https://acrobat.adobe.com/us/en/products/pdf-reader.html.