Relationship types

These are the available relationship types for creating a relationship between items.

Relationship typeOrigin typesDestination typesRulesDescription

Map2Service

Web Map

Map Service, Feature Service, Image Service

None

WMA2Code

Web Mapping Application

Code Attachment

compositeShare, compositeDelete, copyOriginShareOnAdd

Map2FeatureCollection

Web Map

FeatureCollection

None

MobileApp2Code

Mobile Application

Code Attachment

compositeShare, compositeDelete, copyOriginShareOnAdd

Service2Data

Service Item (Hosted Feature Service or Map Service)

Source Data (Service Definition, CSV, Shapefile, Feature Service, Tile Package, Feature Collection)

mustOwnAllItems

Models the association of a derived service and its source data. The derived service is the origin of the relationship. The source data is the destination of the relationship. The source data can be a service. The relationship is queryable in either direction.

Service2Service

Feature Service

Map Service

mustOwnAllItems

Models the association of a source service and a derived service. The source service is the origin of the relationship. The derived service is the destination of the relationship. The relationship is queryable in either direction.

Map2AppConfig

Web Map

Application Configuration

mustOwnAllItems, compositeShare, compositeDelete, copyOriginShareOnAdd

Item2Attachment

*

Microsoft Word, Microsoft Excel, Microsoft PowerPoint, PDF, Image, Visio Document

mustOwnAllItems, compositeShare, compositeDelete

Item2Report

*

Microsoft Word, Microsoft Excel, Microsoft PowerPoint, PDF, Image, Visio Document

Listed2Provisioned

*

*

mustOwnAllItems, compositeDelete, childListing

Style2Style

Vector Tile Service

Vector Tile Service, Style

mustOwnDestinationItem

Service2Style

Vector Tile Service, Style

Vector Tile Service, Style

mustOwnDestinationItem

Survey2Service

Form

Feature Service

mustOwnOriginItem

Survey2Data

Form

*

mustOwnOriginItem

Service2Route

Hosted Feature Service

Route Layer

mustOwnAllItems, compositeDelete

Models the relationship between a feature service containing all the routes and route layer representing each route.

Area2Package

Map Area

Map package, Tile Package, SQLite Geodatabase, Vector Tile Package

mustOwnAllItems, compositeShare, compositeDelete

Map2Area

Web Map

Map Area

mustOwnAllItems

Service2Layer

Feature Service

Feature Service

mustOwnAllItems, compositeShare, compositeDelete

Area2CustomPackage

Map Area

Map Package, Tile Package, SQLite Geodatabase, Vector Tile Package

mustOwnAllItems

Relationship Rules

Each relationship type can have certain rules that are enforced by the server to help keep the items properly related.

  • compositeShare—Related items are logically treated as one shareable item.
    • Prerequisites
      • Both items must be owned by the owner of the relationship.
      • Both items must be shared the same way.
    • Rules
      • If the origin item is shared, the destination item is shared the same way.
      • Sharing of the destination item is not allowed.
  • compositeDelete—Related items are logically treated as one item upon deletion.
    • Prerequisites
      • Both items must be owned by the owner of the relationship.
    • Rules
      • If the origin item is deleted, the destination item is deleted.
      • If the destination item is deleted, nothing happens to the origin item.
  • copyOriginShareOnAdd—The destination item inherits all the sharing permissions of the origin item and is an overwrite of the destination item permissions. This rule applies to Add Item with the relationship call.
  • mustOwnOriginItem—Creator of the relationship must own the origin item.
  • mustOwnDestinationItem—Creator of the relationship must own the destination item.
  • mustOwnAllItems—Creator of the relationship must own both related items.
  • childListing—Both source (parent) and destination (child) items must be listed - the parent publicly and the child privately.


In this topic
  1. Relationship Rules