Skip to main content

Documentation Index

Fetch the complete documentation index at: https://withforerunner.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

This feature requires initial setup by your Customer Success Manager. Contact your CSM or get help at support@withforerunner.com to enable ArcGIS syncing for your saved views.
ArcGIS syncing allows you to automatically keep your Forerunner table data synchronized with ArcGIS Online. Instead of manually exporting and importing data, your saved views stay up-to-date in your ArcGIS environment, enabling real-time analysis and mapping workflows.

​
How ArcGIS syncing works

Once configured by your Customer Success Manager, ArcGIS syncing creates a live connection between your Forerunner saved views and your ArcGIS feature layers. As data changes in Forerunner, those updates automatically flow to ArcGIS. Key benefits:
  • Always current - Data updates automatically without manual exports
  • Seamless workflows - Use Forerunner data directly in your ArcGIS maps and apps
  • Reduced manual work - No more downloading and uploading files
  • Consistent data - Everyone works from the same up-to-date dataset
ArcGIS syncing is ideal for organizations that rely on ArcGIS for mapping, analysis, and public-facing web maps.

​
Setting up ArcGIS syncing

Your Customer Success Manager handles the technical setup to connect your Forerunner account with your ArcGIS organization.
1

Contact your CSM

Reach out to your Customer Success Manager to request ArcGIS syncing for specific saved views.
2

Provide ArcGIS details

Your CSM will need information about your ArcGIS organization:
  • ArcGIS Online URL
  • Authentication credentials or service account
  • Target feature service location
  • Any security or access requirements
3

Specify saved views

Tell your CSM which saved table views you want to sync. You can sync multiple views to different feature layers.
4

Review configuration

Your CSM will configure the sync and verify that data flows correctly to your ArcGIS environment.
5

Start using synced data

Once configured, your data begins syncing automatically. Access it through your ArcGIS Online portal.
Plan which saved views to sync before contacting your CSM. Consider views that you regularly use in ArcGIS workflows or need for public-facing maps.

​
What gets synced

ArcGIS syncing transfers data from your saved table views to feature layers in your ArcGIS organization.

​
Synced data includes

All columns visible in your saved view become attributes in the ArcGIS feature layer. Field names and data types are preserved where possible.
Location data (points, polygons) syncs as feature geometries. Only geocoded records with valid spatial data are included in the sync.
Active filters in your saved view determine which records sync to ArcGIS. Only records matching the filter criteria are included.
Changes to records in Forerunner sync to ArcGIS automatically. This includes:
  • New records added to the view
  • Updates to existing record attributes
  • Changes to record locations
  • Records removed when they no longer match filters

​
What doesn’t sync

The following items are not included in ArcGIS syncs:
  • Attached files and documents
  • Non-geocoded records (records without location data)
  • Related records from other tables
  • Audit history and change logs
  • Internal notes and comments

​
Sync frequency

Data syncs occur automatically at regular intervals. The sync frequency can be configured by your Customer Success Manager based on your needs. Available sync intervals:
  • Every 30 minutes - For time-sensitive data that needs frequent updates
  • Hourly - Standard interval for most use cases
  • Daily - For data that doesn’t change frequently
  • Weekly - For relatively static datasets
There may be a brief delay between changes in Forerunner and their appearance in ArcGIS. Plan accordingly for time-sensitive workflows.

​
Using synced data in ArcGIS

Once your saved views are syncing, you can use them like any other feature layer in ArcGIS.

​
Accessing synced layers

  1. Open ArcGIS Online
  2. Navigate to Content in your organization
  3. Find the synced feature layer (typically named after your saved view)
  4. Add to maps or use in web apps
Bookmark or favorite your synced layers in ArcGIS for quick access.

​
Common use cases

Web maps

Create public or internal web maps with live Forerunner data

Dashboard apps

Build ArcGIS dashboards that update automatically with current data

Field apps

Use synced data in ArcGIS Field Maps or Survey123

Spatial analysis

Perform GIS analysis with up-to-date Forerunner data

​
Editing considerations

Do not edit synced feature layers directly in ArcGIS. Changes made in ArcGIS will be overwritten by the next sync from Forerunner.Always make data edits in Forerunner to ensure changes persist and sync correctly.

​
Managing synced views

While your CSM handles the technical configuration, you can manage the data that flows to ArcGIS by adjusting your saved views in Forerunner.

​
Changing synced data

To change what data syncs to ArcGIS:
  1. Update filters in your saved view to include or exclude different records
  2. Add or remove columns to change the attributes in the ArcGIS layer
  3. Modify the saved view and save your changes
Changes to your saved view automatically affect future syncs to ArcGIS.
If you need to change which saved view is synced or add new synced views, contact your Customer Success Manager.

​
Best practices

Avoid frequent structural changes to synced saved views. Adding or removing columns changes the schema in ArcGIS, which may affect maps and apps using the layer.
Name your saved views descriptively. The view name often becomes the feature layer name in ArcGIS, so clear names help others understand what the data represents.
Ensure records in your synced views are properly geocoded. Non-geocoded records won’t appear in the ArcGIS feature layer, which may cause confusion.
Maintain documentation about which views sync to which ArcGIS layers. This helps your team understand data sources and troubleshoot issues.
If you plan to use synced data in public-facing maps, test thoroughly first. Verify that the correct records and attributes appear as expected.
Occasionally check that your synced data in ArcGIS matches expectations. If you notice discrepancies, contact your CSM.

​
Troubleshooting

Check these items:
  • Verify your saved view contains geocoded records with location data
  • Confirm records match your view’s filter criteria
  • Check if the sync has run recently (may take up to the sync interval)
  • Contact your CSM to verify the sync configuration is active
Non-geocoded records never appear in ArcGIS syncs. Check the geocoding status of your records in Forerunner.
Solution: Allow time for the next sync to run. Syncs occur at regular intervals (typically 15-60 minutes), so recent changes may not appear immediately. If more than 2 hours have passed, contact your CSM.
Solution: Verify the columns are visible in your saved view in Forerunner. Only columns shown in the saved view sync to ArcGIS. Add any missing columns to your view and wait for the next sync.
Solution: ArcGIS syncs only include geocoded records. Use the geocoding status filter in Forerunner to identify non-geocoded records. Records without valid location data are automatically excluded from geographic feature layers.
Solution: Contact your Customer Success Manager to reconfigure the sync connection. Changing the source view requires technical adjustments to the integration.
Solution: Yes, your CSM can configure a single saved view to sync to multiple feature layers if needed. This is useful when sharing the same data across different ArcGIS organizations or applications.

​
Getting help

For assistance with ArcGIS syncing:
  • Configuration changes - Contact your Customer Success Manager
  • Sync issues - Reach out to your CSM with specific details about the problem
  • ArcGIS questions - Consult ESRI’s documentation or your organization’s GIS administrator
When reporting sync issues to your CSM, include the name of the saved view, the ArcGIS layer name, and specific examples of missing or incorrect data.