Manage feature layers
Organization administrators and owners of feature layers (feature services) that reference registered data can control editing access, allow data exports, and configure advanced editing options.
Note:
If the feature service is published on a federated server secured with web-tier authentication, for example, Integrated Windows Authentication (IWA), Lightweight Directory Access Protocol (LDAP), or client-certificate authentication, you cannot configure service and layer settings through the portal website. In such cases, you must use ArcGIS Server Manager on the federated server to manage service and layer settings.
Control editing access
As the owner of a feature layer that references registered data or as an administrator, you can change the settings on the layer to control whether editing is allowed and what types of edits can be made.
The settings described in this section affect users who are not the layer owner, not an administrator, and not a data curator. To perform the editing operations enabled on the layer, these users must be members of a default or custom role that has the privilege to edit features.
Enable editing and configure the types of editing that are allowed
Follow these steps to enable editing on a feature layer that references registered data:
Sign in to the organization as the item owner or an organization administrator.
If you sign in as the item owner, you must be a member of a role with the privilege to publish server-based layers.
Open the item page for the feature layer.
Click the Settings tab.
Scroll to the Feature Layer section and expand the Configuration heading.
Check the Enable editing box.
In the What kind of editing is allowed? section, choose from the following options:
Add—Allow editors to add feature geometry. Editors can also provide attribute values when they create the feature.
Delete—Allow editors to delete features.
Update—Allow editors to update feature geometry and attributes. To allow editors to update attributes only and not update feature geometry—in other words, they cannot move features or alter feature shapes—choose Attributes only.
In the What features can editors see? section, choose one of the following options:
Editors can see all features—Enable this option when the editor should be able to access all features in the feature layer.
Editors can only see their own features (requires editor tracking)—If the source data is from an enterprise geodatabase and has editor tracking enabled, you can enable this option to prevent users from accessing sensitive or proprietary information, such as medical records or research data, for features that are added by other editors.
Editors can't see any features, even those they add—Enable this option when the editor doesn't need or shouldn't see newly added features. For example, if you have people collecting survey information from the public using apps such as ArcGIS Survey123, you may not want the editor to see the information the survey respondents provide, as it could be private or sensitive information such as the respondent's home address.
Note:
When Editors can't see any features, even those they add is enabled, data is not visible through the feature layer to anyone in any ArcGIS apps.
Choose one of the following options for the What features can editors edit? section:
Editors can edit all features—Allow editors to delete or modify features created by themselves and others.
Editors can only edit their own features (requires editor tracking)—Allows editors to delete or modify the features they create but not delete or modify others' features. This option is only supported if the source data is stored in an enterprise geodatabase and has editor tracking enabled.
Click Save, and click Save and restart.
The edits are applied immediately.
Add and update features from a file
You can use an updated file to add features to a layer in an existing feature layer if you are any of the following:
The owner of the feature layer
An organization administrator
A member of a shared update group with which the feature layer is shared
This allows you to publish initial data, or even an empty feature layer, and later add more data as it becomes available without having to overwrite the entire feature layer. For example, if you have a number of employees who do inspections in the field and they gather that information in a .csv file or a custom app that writes to a shapefile, you can take the file from each inspector at the end of the day and update the feature layer with the new data.
If the update file contains changes to features that are already published, you can also use the input file to update existing features. This requires that the layer and the file you use to load updates both contain a field of unique values that ArcGIS Enterprise can use to identify the feature to update.
Caution:
You must ensure that the field values in the update file and the layer correctly and uniquely identify the feature to update. If the values do not, you can lose data when an update overwrites attributes for an existing feature. Adding and updating features fails if you update results with nonunique values in a field you have identified as unique.
Field names, including the letter case, in the file you use must be identical to those in the existing feature layer. When you publish from a .csv or Microsoft Excel file that has field names with spaces, the field names in the feature layer have underscores inserted between words. When you add or update, you must insert underscores in the field names in the file; otherwise, field names will not be identical.
You can use the following file formats to add or update data:
Shapefile (zipped)
CSV file (
.csv)—The spatial field must be provided in latitude and longitude coordinates.Microsoft Excel file—The spatial field must be provided in latitude and longitude coordinates.
Note:
The update operation does not delete features. To delete features using an uploaded file, overwrite the layer.
If the feature layer is enabled for offline editing, you can only add features; you cannot update features.
Adding or updating features does not add or update attachments on the feature layer.
To add or update big integer, date only, or time only fields from Excel or
.csvfiles, the field values must meet the following requirements:Integer values that fall outside the range of -2147483648 to 2147483647 will be interpreted as big integers.
To be interpreted as date only, values must be in the format YYYY-MM-DD or DD/MM/YYYY.
To be interpreted as time only, values must be in the format hh:mm:ss or hh:mm:ss.sss.
For examples of date and time values, see Date and time fields in ArcGIS Enterprise.
If the feature layer does not contain these field types, you can map them to other types, such as a double for big integer fields or a string for date only fields.
Complete the following steps to upload a file to add features to or update features in a feature layer:
Sign in to the organization as the owner of the feature layer or as an organization administrator.
Open the item page for the feature layer.
Click Update data on the feature layer item's Overview tab.
Tip:
You may need to click the Show more button
to see all options.Alternatively, you can open the Update data window from the Data tab by clicking the Update data button
.The Update data window appears.
Choose one of the following options and click Next:
Add features—Inserts new features from the file to the feature layer or inserts new rows to a table layer.
Update features—Uses the values in the file to update attribute values for existing rows in the layer. If the layer is a feature layer, you can also update feature locations.
Add and update features—Performs both of the actions described above.
Note:
Do not use the object ID field or feature ID (FID) field as the unique identifier when you update features unless you know for certain that no one has deleted features from and added features to the feature layer.
If the feature layer contains more than one layer, choose the layer to add to or update and click Next.
Use one of the following methods to specify the updated file:
Click Your device, browse to and select the file, and click Open.
Drag the file from your desktop or File Explorer onto the Update data window.
Specify which fields in the file correspond to which fields in the layer and click Next.
The remaining steps vary depending on the update option you choose, the layer type you're updating, and what type of fields are present in the file.
If you are updating data, define which fields in the layer and the file uniquely identify each feature or row and which can be used to ensure the correct data from the file updates the correct feature or row in the layer.
If the file contains date values that store time in a time zone other than UTC, choose that time zone from the Time zone selection drop-down menu.
If you are updating the data in a feature layer, choose one of the following options:
Attributes only—Updates nonspatial attribute values only.
Geometries and attributes—Updates both spatial and nonspatial values.
Note:
If you chose the Add and update features option, added features always contain both attributes and geometries.
If you are adding features or rows only (not updating), click Add and complete to append the features or rows. If you are updating only or updating and adding features or rows, click Update and complete.
The size of the layer and which options you chose will affect the time it takes to apply updates. As soon as this process completes, the updated layer is available in maps, scenes, and dependent WFS layers and feature layer views.
Allow offline editing or collaboration
To allow others to take the feature layer offline and work with it while disconnected from the network, or to share feature layer data as a copy in a distributed collaboration, you must enable synchronization on the layer.
When you enable synchronization, it allows offline editors to get the latest updates to features at the time they connect. Any edits they made to features while disconnected are also applied at the time they connect. It also allows changes made to the layer in the sending organization of a collaboration to be synchronized to the feature layer in the participating organizations.
Tip:
You do not have to enable editing on the feature layer to take it offline; you can enable synchronization to allow users to take a feature layer offline for reference (read-only) purposes.
Open the item page for the feature layer.
Click the Settings tab.
Scroll to the Feature layer section and enable the Enable Sync (required for offline use and collaboration) toggle button.
Click Save, and click Save and restart.
The edits are applied immediately.
Allow appending data
As an organization administrator or the owner of a feature layer, you can append data to the layer. You can also configure a feature layer to allow others to append data to the layer when they access it in the portal.
Follow these steps to allow others to append data to a feature layer:
Open the item page for the feature layer.
Click the Settings tab.
Scroll to the Feature layer section.
Enable the Append toggle button.
Click Save, and click Save and restart.
Other members who have access to the layer can now append data to the feature layer.
Allow shared template editing
As an organization administrator or the owner of a feature layer, you can add, update, and delete shared templates. You can also configure a feature layer to allow others with access to the layer the ability to add new templates and update or delete the templates they own.
Follow these steps to allow others to edit shared templates:
Open the item page for the feature layer.
Click the Settings tab.
Scroll to the Feature layer section.
Scroll to the Shared templates section and enable the Allow others to create and manage their own shared template toggle button.
Click Save, and click Save and restart.
Other members of your organization with access to the layer can now can add, update, and delete shared templates.
Allow data exports
As an administrator or the owner of a feature layer, you can export data from the layer. You can also configure a feature layer to allow others to export data from the layer when they access it in the portal.
Follow these steps to allow others to export data:
Sign in to the organization as the item owner or an organization administrator.
If you sign in as the item owner, you must be a member of a role with the privilege to publish server-based layers.
Open the item page for the feature layer.
Click the Settings tab.
Scroll to the Feature layer section.
Scroll to the Export data section and enable the Allow others to export to different formats toggle button.
Click Save, and click Save and restart.
Now other members of your organization can export data from the feature layer.
Configure advanced editing options
Follow these steps to configure additional editing-related properties:
Sign in to the organization as the item owner or an organization administrator.
If you sign in as the item owner, you must be a member of a role with the privilege to publish server-based layers.
Open the item page for the feature layer.
Click the Settings tab.
Scroll to the Feature layer section..
Expand the Advanced options section.
You can set the following properties:
Allow update of true curves—If the source data contains true curve features, you can enable this option to allow editors to update these features. However, when an editor performs edits from a client that does not support true curves, the true curve features are overwritten with a series of short, straight line segments held together with vertices to approximate an arc (also referred to as densified lines). To avoid this, you can also enable the Only allow true curve updates by true curve clients option. At this time, ArcGIS Pro is the only ArcGIS client that can edit true curves.
Allow default z-value when inserting or updating features—Allows you to specify a default z-value. If an editor adds or updates a feature through the feature layer and does not specify a z-value, the default z-value is applied.
Allow geometry updates without m-values—Use this setting if layers in the feature layer are enabled to store m-values, but you are not using the m-values. When editors edit feature geometries through the feature layer, NaN m-values are inserted if the client does not provide a value.
Add realm to user name when applying edits—This option allows you to specify a value to be appended to the usernames recorded when editing through the feature layer. This allows you to differentiate when a user is editing through the feature layer rather than directly against the data in the geodatabase. To enable this, check the Add realm to user name when applying edits option and type the realm value to add to usernames.
Sanitize HTML to remove unsupported entities and attributes—When this option is enabled, it prevents the input of unsupported HTML entities or attributes. This option is enabled by default and, unless editors require the ability to input these unsupported HTML entities, do not disable this option. Disabling this option allows a user to enter any text in the text boxes, which exposes the service to potential cross-site scripting (XSS) attacks.
Click Save, and click Save and restart.
The edits are applied immediately.
Manage allowed utility network operations
For feature layers that participate in a utility network, you can control which utility network operations are available to users through the item settings page.
To update the allowed operations, complete the following steps:
Sign in to the organization as the item owner or an organization administrator.
If you sign in as the item owner, you must be a member of a role with the privilege to publish server-based layers.
Open the item page for the feature layer.
Click the Settings tab.
Scroll to the Utility network section.
Enable or disable the following allowed operations:
Enable subnetwork controller—Allows users to designate features as subnetwork controllers for a given tier.
Disable subnetwork controller—Allows users to remove the subnetwork controller designation from features.
Export subnetwork—Allows users to export a subnetwork details and topology.
Enable network topology—Allows users to enable the network topology.
Trace—Allows users to perform network traces; requires network topology.
Validate network topology—Allows users to validate the network topology for a given extent or selection sets.
Update subnetwork—Allows users to update subnetwork on a given tier which sets subnetwork fields on features participating in the subnetwork.
Query network moments—Allows users to return the network properties.
Update is connected—Allows users to update connectivity status for features participating in the network.
Disable network topology—Allows users to disable the network topology.
Synthesize association geometries—Allows users to generate geometry representations for associations.
Trace configurations—Allows users to create, modify, and use named trace configurations.
Diagnostics—Allows users to access diagnostic information.
Associations—Allows users to work with network associations.
Locations—Allows users to access network location information.
Circuits—Allows users to access circuit-based network information; requires a telecom domain network.
Unit identifiers—Allows users to work with unit identifiers; requires a telecom domain network.
Click Save, then click Save and restart.
The allowed operations are updated for members of your organization with access and the required privileges.
Considerations for feature layers published from cloud data warehouse data
The preceding settings do not apply to a feature layer published from ArcGIS Pro that references data in a supported cloud data warehouse. Settings for this type of feature layer display the values for parameters that were set when the layer was published.
If you created a snapshot when you published the feature layer, two snapshots of the data were copied from the source cloud data warehouse and placed in a system database—one snapshot for the feature layer and one for its associated map image layer. Settings are available that allow you to update the snapshot for both layers to incorporate changes made to the data in the source cloud data warehouse. See Refresh data for snapshot layers for instructions.