Feature service relationship

Author maps to publish feature services—Documentation | ArcGIS Enterprise

feature service relationship

You have the relationship setup incorrectly. You need to use the GlobalID of the parent and have it go into the GUID field of the child. I seem to be unable to publish a hosted feature service (share as web In memory joins/relates are not supported, thus a relationship class. This definition explains the meaning of customer relationship customer service relationships and assisting in customer retention and driving sales growth. . Mobile CRM apps take advantage of features that are unique to.

If an unsupported renderer is used, the service fails to start. The server log can be used in this case to determine which layers have unsupported renderers. Proportional symbols, as well as unique value renderers based on multiple fields, are not supported by feature services.

Most symbol types can be used with a feature service; however, in some cases, the symbols may be downgraded. For line layers, simple line symbols are supported. If other symbols are used, the feature service converts them to a simple line symbol that best represents the original symbol. For example, a cartographic line symbol in the map document may be drawn as a simple solid line in a feature service client.

If a line symbol is complex or has multiple layers, the feature service downgrades the line to best represent the original line symbol. For polygon layers, simple fill and picture fill symbols are supported. If other symbols are used, the feature service downgrades them to simple fill symbols.

For multilayer fill symbols, the feature service only considers the top layer. Also, a fill symbol's outline symbol has the same level of support as described for line layers above. For point layers, simple marker and picture marker symbols are supported.

If other symbols are used, the feature service downgrades them to picture marker symbols. Multilayer marker symbols are also downgraded to picture marker symbols where the layers are merged into a single layer. Mask properties, where a halo can be set for a marker symbol, are not supported.

When a map service with feature access starts, the symbols are checked and downgraded if needed. In cases where a downgrade is required, a warning is added to the server log to describe which symbols were downgraded.

It is also important to note that if you have layers in your map document that use cartographic representation renderers, the renderers are reported as unique value renderers when clients access the service through REST. It is recommended that you use RGB colors in the symbols; otherwise, minor changes may occur when the colors convert to the RGB color format.

Define feature templates Inserting new features through a feature service is accomplished using the feature templates from the map document. A template allows you to digitize a new feature and have the attribute's default values set accordingly.

Feature services require that a template exist for each feature type. When you start an edit session or publish the service, a default template is created for each type. Default templates are always used for database data. You can create customized templates to use with geodatabase data. See the Custom feature templates section for more information. Set a scale range Feature services only display 1, features by default. You need to set the scale range for the feature layers in the map you publish so the layer will not display at a scale at which more than the maximum number of features would appear.

To set a scale range for a feature layer, right-click the layer in the ArcMap table of contents and click Properties. Field properties Field properties set in ArcMap are exposed through the feature service; this includes field aliases, field visibility, and a field's read-only property.

Read-only fields include system-managed fields, such as ObjectID, globalid, and editor tracking fields geodatabase onlyas well as fields set to be read-only in the map document. When applying an update, if a value is set for a read-only field, the feature service ignores the value. When applying an insert, default values are applied for read-only and invisible fields.

If default values have not been defined, nulls are applied. If the field cannot store null values, the insert fails.

ArcGIS for Server

Layer description and copyright information Layer descriptions and credits copyrights specified in the map document are exposed for each layer in the feature service as a layer description and copyright information, respectively.

If you work with your feature service on the web and you want pop-ups to be available, consider defining them in the ArcGIS. Time support Temporal data—data that represents a state in time—is supported and can be visualized through feature services.

The time information is stored in single or multiple attribute fields and can be used to visualize data at particular times or in time intervals. Temporal data can be exposed through the feature service by enabling time on the Time tab of the Layer Properties dialog box. For more information about how to enable time on a dataset, see Enabling time on your data.

feature service relationship

Coordinate systems Feature services support cases where layers in the map document have different coordinate systems. Coordinate system translations are performed if needed when using the feature service. For example, if a client inserts a feature through a feature service using a coordinate system that is different from the coordinate system of the layer, it converts to the layer's coordinate system before being stored. Spatial queries involving geometries also convert to the layer's coordinate system before being applied to return the correct results.

Geographic datum transformations are also used if needed. You can control the transformation method by setting up transformations in the data frame properties of the map document before publishing. A default transformation is performed if one is not defined in the map.

Although you can publish separate layers that have different coordinate systems, all records in an individual table must use the same coordinate system. Additional geodatabase functionality If your data is stored in a geodatabase, you can take advantage of some additional functionality. Set up this functionality before publishing a feature service.

Define subtypes and attribute domains If the data you publish is in a geodatabase, configure your datasets to use subtypes and attribute domains where appropriate to enhance the user experience of the feature service and prevent data entry errors. These provide ways of categorizing your data and ensuring that appropriate values are entered when the data is edited.

Feature services can detect and use the subtypes and domains. For example, if you have a domain limiting the color of a fire hydrant to red, yellow, or blue, you see a drop-down list in the web application that allows you to only select one of those three colors. To include settings from your subtypes in the feature service, use a unique value renderer based on the subtype field. Custom feature templates Within ArcMap, you can create new templates or modify existing templates to customize the editing experience through the feature service.

This includes setting a default construction tool, which is used to create that type of feature. If you remove a template for a particular feature type, a default template is created when you publish.

Author feature services—Documentation ( and ) | ArcGIS Enterprise

There are different types of construction tools available depending on the type of feature the template creates. For example, if you have a line template, you can only select tools that can be used to create line features. The construction tool saved with the templates is available through the feature service. The only exception is the point tool called Point At End Of Line, which is not supported by feature services. For more information about templates, see Setting feature template properties.

When the map document is saved, the templates are saved with the layers in the map. When the map document is published, these templates are available for feature service clients.

feature service relationship

Once the layers, types, and templates are defined in your map document, you are ready to publish the service. The Publishing feature services section describes how to publish a feature service. Attachments Feature services allow you to query and edit attachments.

An attachment is a media file associated with a feature or object in a geodatabase. For example, with attachments, photographs and videos can be added to a bird sighting and viewed when the sighting point is clicked. To use this feature, datasets within a geodatabase must first be configured to support attachments.

When these datasets are added to a map document and published, clients can query, insert, and delete the attachments through the feature service. There are limits imposed on the size and file types you can attach to a feature service. For more information about how to configure a dataset to support attachments, see Enabling attachments on a feature class. Bird sighting feature service The following section walks you through an example of how to set up a map document, define the data, and define the symbology exposed through a bird sighting feature service.

The feature service allows the birding community to post their bird sightings directly on the map and attach media files, such as photographs, audio files, and video files, to the specific observation points. The steps in this example are applicable to geodatabases and databases; however, feature attachments and custom feature templates are not available in databases.

You can ignore the content that discusses this functionality if the data you're working with is not stored in a geodatabase. For example, tables containing data types that are not supported by ArcGIS can be published, but unsupported data types are not accessible through ArcGIS or the feature service.

See View database data in ArcGIS for information on how the query layer is initially defined when you add a database table to the map. The table must contain a unique integer column maintained by the database. If you create tables and load the data to the database using ArcGIS, a database-maintained unique integer ObjectID is added automatically. If you create data outside of ArcGIS, be sure to include a database-maintained, unique, not null integer column in the table. If such a column does not exist, you cannot publish a feature service.

These properties define how the data appears and what the client can do with the data. Configure a map document in ArcMap Once you define the data, add it to an ArcMap map document you want to publish, and set properties on the layers and tables.

Map document configuration is similar for both database and geodatabase data. However, if your map document contains geodatabase data, you can configure your map to take advantage of extra functionality available only in geodatabases before publishing.

Set a layer name When you add a feature class or table to a map, the default name is the fully-qualified name of the table within the database. At minimum, you should change the layer name so it does not include the database and user name.

Right-click each layer in the table of contents and click Properties. On the General tab, type a useful name that represents the layer's contents and does not include the database and user name. For example, if you add the feature class, rivers, to the map from an enterprise geodatabase named mygdb, and the feature class is owned by the user gdbdata, the default layer name in the map is mygdb. Change the layer name to rivers.

You might change the layer name even further if you set a definition query on the layer that changes what features are displayed in the map. For example, if you set a definition query so that only rivers within 5 miles of mine are displayed, it would be useful to change the layer name to reflect that; for example, set the layer name to rivers near mines.

If the feature class participates in a relationship class and, therefore, related data will be included in the service you publish, you might change the layer name to reflect that. For example, if the rivers feature class participates in a relationship class that joins it to a table containing watershed information, you could change the layer name to rivers and watersheds.

Define symbology A feature service allows you to query features and also get the features' symbology. Clients can use this information to draw features with a symbology that is consistent with what is defined on the service. The symbols returned by the service are based on the symbology of the layers in the ArcMap document.

Using relationship classes with ArcGIS Online? - Geographic Information Systems Stack Exchange

Each symbol in each layer is referred to as a type. For example, a layer symbolized with a simple renderer one symbol has one type.

If a unique value renderer is used, a type returns for each unique value in the renderer. Feature services support simple, unique value, class break, and cartographic representation renderers. If you use an unsupported renderer, the service will not start. Feature services published from ArcMap do not support proportional symbols or unique value symbology based on multiple fields.

Most symbol types can be used with a feature service; however, in some cases, the symbols may be downgraded. For line layers, simple line symbols are supported. If other symbols are used, the feature service converts them to a simple line symbol that best represents the original symbol. For example, a cartographic line symbol in the map document may be drawn as a simple solid line in a feature service client.

If a line symbol is complex or has multiple layers, the feature service downgrades the line to best represent the original line symbol. For polygon layers, simple fill and picture fill symbols are supported. If other symbols are used, the feature service downgrades them to simple fill symbols.

For multilayer fill symbols, the feature service only considers the top layer. Also, a fill symbol's outline symbol has the same level of support as described for line layers above.

For point layers, simple marker and picture marker symbols are supported. If other symbols are used, the feature service downgrades them to picture marker symbols. Multilayer marker symbols are also downgraded to picture marker symbols where the layers are merged into a single layer. Mask properties, where a halo can be set for a marker symbol, are not supported. When a map service with feature access starts, the symbols are checked and downgraded if needed. In cases where a downgrade is required, a warning is added to the server log to describe which symbols were downgraded.

It is also important to note that if you have layers in your map document that use cartographic representation renderers, the renderers are reported as unique value renderers when clients access the service through REST. Esri recommends that you use RGB colors in the symbols; otherwise, minor changes may occur when the colors convert to the RGB color format.

Define feature templates Inserting new features through a feature service is accomplished using the feature templates from the map document. A template allows you to digitize a new feature and have the attribute's default values set accordingly. Feature services require that a template exist for each feature type.

When you start an edit session or publish the service, a default template is created for each type. Default templates are always used for database data.

You can create customized templates to use with geodatabase data. See the Custom feature templates section for more information. Set a scale range Feature services only display 1, features by default. Set the scale range for the feature layers in the map you publish so the layer will not display in a scale at which more than the maximum number of features would appear. To set a scale range for a feature layer, right-click the layer in the ArcMap table of contents and click Properties.

Field properties Field properties set in ArcMap are exposed through the feature service; this includes field aliases, field visibility, and a field's read-only property.

Read-only fields include system-managed fields, such as ObjectID, globalid, and editor tracking fields geodatabase onlyas well as fields set to be read-only in the map document.

When applying an update, if a value is set for a read-only field, the feature service ignores the value. When applying an insert, default values are applied for read-only and invisible fields. If default values have not been defined, nulls are applied. If the field cannot store null values, the insert fails. Layer description and copyright information Layer descriptions and credits copyrights specified in the map document are exposed for each layer in the feature service as a layer description and copyright information, respectively.

If you work with your feature service on the web and you want pop-ups to be available, consider defining them in Map Viewer instead. Alternatively, developers can use the client API itself to define pop-up styles. Time support Feature services support temporal data—data that represents a state in time.

Store time information in single or multiple attribute fields, and use this information to visualize data at particular times or in time intervals. To expose temporal data for a layer through the feature service, enable time on the Time tab of the Layer Properties dialog box. For more information about how to enable time on a layer, see Enabling time on your data. Coordinate systems The map document you publish as a feature service can contain layers that have different coordinate systems.

When clients access the feature service, the feature service translates the coordinate system if needed. For example, if a client inserts a feature through a feature service using a coordinate system that is different from the coordinate system of the layer, the feature service converts the feature's coordinate system to match the layer's coordinate system before storing the new feature.

Spatial queries involving geometries also convert to the layer's coordinate system before being applied to return the correct results. The feature service also uses geographic datum transformations if needed. You can control the transformation method by setting up transformations in the data frame properties of the map document before publishing.

A default transformation is performed if one is not defined in the map. Although you can publish separate layers that have different coordinate systems, all records in an individual table must use the same coordinate system. Joined data You can define attribute joins for layers or tables in the map document.

When you publish a map service with feature access capability to a GIS Server site, joined columns are included in the map service but are not included in the feature service.

The feature service includes only the columns from the join table the table or feature class on which you defined the join. If symbology for the layer is based on a joined column, the map service includes the renderer you used to symbolize features, but the feature service reverts to a simple renderer.

If the renderer in the layer is based on a column from the left most feature class in the join, the map server and feature server includes the renderer. Remove joins before publishing a feature service hosted feature layer to either of these applications.

Additional geodatabase functionality If your data is stored in a geodatabase, you can take advantage of some additional functionality.

Configure this functionality before publishing a feature service. Define subtypes and attribute domains If the data you publish is in a geodatabase, configure your datasets to use subtypes and attribute domains where appropriate to enhance the user experience of the feature service and prevent data entry errors. These provide ways of categorizing your data and ensuring that appropriate values are entered when the data is edited. Feature services can detect and use the subtypes and domains.

For example, if you have a domain limiting the color of a fire hydrant to red, yellow, or blue, you see a drop-down list in the web application that allows you to only select one of those three colors. If you publish a feature service without copying data, subtype information is included in the feature service independent of the renderer you use. If you will publish a feature layer to ArcGIS Online or an ArcGIS Enterprise portal, subtype information is included only when layers are published using a unique value renderer on the subtype column.

Custom feature templates Within ArcMap, you can create new templates or modify existing templates to customize the editing experience through the feature service. This includes setting a default construction tool, which is used to create that type of feature. If you remove a template for a particular feature type, a default template is created when you publish.

There are different types of construction tools available depending on the type of feature the template creates. For example, if you have a line template, you can only select tools that can be used to create line features.

The construction tool saved with the templates is available through the feature service. The only exception is the point tool called Point At End Of Line, which is not supported by feature services. For more information about templates, see Setting feature template properties.

When the map document is saved, the templates are saved with the layers in the map. When the map document is published, these templates are available for feature service clients. Once the layers, types, and templates are defined in your map document, you are ready to publish the service. Attachments Feature services allow you to query and edit attachments. An attachment is a media file associated with a feature or object in a geodatabase.

For example, with attachments, photographs and videos can be added to a bird sighting and viewed when the sighting point is clicked. To use this feature, datasets within a geodatabase must first be configured to support attachments.

When these datasets are added to a map document and published, clients can query, insert, and delete the attachments through the feature service. There are limits imposed on the size and file types you can attach to a feature service.