The following limitations are known in this version:
•VertiGIS Networks does not support working with SAAS releases of Studio Web, as we cannot guarantee that the updates are not affecting the Networks deployment.
•If you use a public shared web map in the App, always make sure that you stay logged in to the Portal (manually), otherwise, some actions such as edit associations, diagrams, or tracing might not work as expected.
•When publishing a web map with ArcGIS Pro 3.5, templates from Subtype Group Layers disappear. As a workaround, use ArcGIS Pro 3.3 for publishing your consumer web map.
•General - When creating network elements, the rules for the utility network (UN) are loaded for snapping. It is not yet possible to catch non-network elements at the same time. As a temporary workaround, the rules for the utility network can be turned off and on via a switch during capture, e.g., when creating a network feature that is to be snapped to a construction point.
•Editing versioned data currently requires that exactly one single feature service is referenced in the web map.
•Currently Network Editor offers no support for app templates that contain multiple map elements.
•Features that have containment associations to other features cannot be deleted.
▪Esri web clients -including Networks Editor- do not natively support editing true curves. While curved geometries can be viewed (ArcGIS Server simplifies them automatically for display), editing is not possible as long as the Feature Service enforces true curve constraints.
▪By default, the Feature Service Only allow true curve updates by true curve clients setting is enabled. As a result, any attempt to edit features containing curves from a web client will be rejected.
▪You can disable this setting to allow editing, but note that any geometries modified or created in the Networks Editor will not preserve true curve segments.
•Annotations that consist of an arc-segment in its base line are not yet visible on the map.
•Annotations with a base line consisting of more than two edges are drawn as if they had only two edges (start and endpoint), respecting the annotation class settings.
•Leader lines of Annotations are not yet visible on the map.
•Annotation texts with special characters might get cut off at the end during creation.
•Associations included in the template definition are not yet stored in shared templates. As a result, the template is available, but associations are ignored when creating features from the template.
•Publishing with ArcGIS Pro 3.5.2 or 3.5.3 may cause geometry errors. If an invalid geometry is detected (e.g., polyline with zero paths), a notification is displayed to the user.
▪Changing the Primary feature builder of a group template to "Offset" is currently not supported.
▪Snapping only supports the Utility Network snapping rules from the primary feature of the template.
▪Non-spatial features are not supported.
▪Attributes in non-mandatory fields are set to null.
▪Mandatory fields receive the value defined in the template.
▪Templates that include annotations or dimensions are not supported.
•In certain circumstances, there can be an offset of the displayed dimensions between ArcGIS Pro and Networks. Circumstances are related to dimension style configuration:
▪Text symbol vertical and horizontal alignment.
▪Text symbol offset configuration.
•Currently, dimensions are only displayed with ARIAL font. If any other font is used in the dimension class, it will be ignored.
•Currently no support for printing within a version.
•Dimension layers can only be printed with the new Geoprocessing-based Printing Engine.
•Annotation layers might get cut off during printing.
•Updating your solution from 1.12 to 1.13 will cause the 3 known conflicts Erased node,'1_e*p3nd|id and Changed value dev001 to dev002. These can be ignored.