Data Layers for Native GIS

Connectors

A connector pushes Salesforce records to a hosted feature layer in ArcGIS, where they form a reference layer. Because the records live in ArcGIS, mobile workers view them on the map even when the records aren't primed on the device through Briefcase. The app makes reference-layer records available through the ArcGIS SDK instead. Before any reference-layer records appear, set up Briefcase for the object and prime at least one record in the app. Connectors suit static, high-volume data that exceeds the app's offline priming limits, such as Assets that mobile workers reference across many work orders.

The connector treats Salesforce as the source of truth and syncs one way, on a schedule that you define. So that the app recognizes the synced records as Salesforce records, you add four fields to the ArcGIS feature layer: Object Name, Record ID, Last Modified, and Record Type. When mobile workers tap a record in a reference layer, they see the record's Salesforce details and can create or update it. Set up connectors in the Connectors section of the Data Layers tab. See Set Up a Native GIS Connector.

Related Objects

Related objects plot the records in a work order's related list directly on the map, without syncing to ArcGIS. A related object always links to the work order, such as work order line items or a custom object whose records tie to the work order. Because related objects use the app's priming mechanism instead of syncing to ArcGIS, mobile workers always work from current Salesforce data. Related objects suit dynamic data that changes with the work.

A record's location comes either from a field on the record itself or from a lookup to another object that holds the coordinates. Mobile workers can view and create or update these records, and they see the full Salesforce layout for a related record. Set up related objects in the Related Objects section of the Data Layers tab. See Set Up Related Objects for Native GIS.

When to Use Connectors or Related Objects

Choose a data layer based on how the data changes and how much of it there is.

• Use a connector for static, high-volume data that exceeds the app's offline priming limits, such as Assets. The connector pushes the data to ArcGIS so that mobile workers view it offline without priming every record. For example, use a connector to show nearby assets that aren't associated with the work order, so that mobile workers view them in a geospatial context.
• Use related objects for dynamic data tied to the work, such as records in a work order's related list. Related objects use the app's priming mechanism and don't require a sync, so mobile workers always work from current Salesforce data. For example, use related objects to plot the work order line items or the assets associated with the work.

Native GIS maps can also show view-only data from external ArcGIS feature layers that don't represent Salesforce records. Mobile workers see a pop-up for those records but can't act on them. You add external feature layers to the web map in the ArcGIS portal, not on the Data Layers tab. See Set Up ArcGIS for Native GIS.

Supported Geometry Types

Connectors and related objects both plot points, lines, and polygons on the map. A record's location field determines the shape:

• For points, use a geolocation field.
• For lines and polygons, use a text field that contains GeoJSON in the Feature format, not the FeatureCollection format.

Other geometry types can appear on the map but can't be created or updated.