Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Make sure to zoom out to an extent that covers all of the area for the relevant data to be published. For example, if you have data which consists of all counties in California, zoom out on the map to show California, Oregon and Mexico.

  • Once zoomed out, save the map document and do not zoom back in before publishing.

  • Ensure that you are logged in to your ArcGIS Account in ArcMap / ArcPro. To sign in from ArcMap, go to File -> Sign In.

  • Publish the service using the ‘Share’ option in ArcMap (File -> Share As -> Service).  Select ‘Publish a service’ and name the service. We recommend using the same naming convention as field names - title case with underscores, and include a version number if helpful (e.g., Title_Case_With_Underscores_v2). Note that the feature service names will be displayed alphabetically in the ‘Select Feature Service’ dialog, and Android sorting is case sensitive - this means that ‘a' will be sorted below 'Z’ because capitol letters are sorted before (above) lower case letters. As described above, we recommend naming the ArcMap document (MXD) with that will be used for the feature service. This helps when overwriting a service after changes are made to the data model or symbology. Complete the following information during the publication process:

    • Capabilities - check Feature Access and uncheck Tiled Mapping.  

    • Sync Enable - check this box to support Sync, which required for MobileMap 5.0.

      • Note that enabling Sync on a feature service prevents use of some workflows like using the Append tool in ArcGIS Pro.

    • Feature Access - check the boxes next to Create, Delete, Query, Sync, and Update.  (Figure 11)

    • Item Description - add text in the Summary and Tags. If these were set in the Map Document Properties as suggested above, these will already be populated. Review them to make sure they are correct. 

    • Sharing - choose the level of Sharing.  

      • Selecting Everyone makes the feature service a ‘public’ service, meaning anyone could potentially find the service if they know what to search for on ArcGIS Online.  This is NOT recommended.

      • Selecting your organization limits the sharing to just your group. (If you select your organization, you will need to put your ArcGIS Online user name and password in the settings of WSG MobileMap).

      • For MobileMap to find the service and display it in the ‘Select Feature Service’ dialog, the service must be shared with at least one group that the user is a member of. Sharing via ‘Everyone’ or ‘Your Organization’ is not sufficient for MobileMap to find the service.

      • See section below on Managing ArcGIS Online Groups and Users for more information on this topic

  • Finally, select Publish in the upper right corner.

...

  • Publishing a Feature Service from ArcGIS Pro is implemented under the Share tab using the Publish Web Layer option. This terminology is a bit confusing, because you will actually be publishing a Feature Service, and it will have multiple layers, but that is the generic term that is used in ArcGIS Pro. Go to Share > Web Layer > Publish Web Layer

...

  • On the Configuration Tab

    • Check the box to enable editing (Add, Delete, Update) of Attributes and Geometry

    Optionally enable
    • Enable Sync (for compatibility with MobileMap 5.0 and Esri Field Maps)

    • Enable editing and allow users to add, delete and update attributes and geometry

    • Optionally enable Export Data (to

    enabled
    • enable export of full database as FGDB for backup, etc.)

...

On

...

MobileMap Settings - Saving to Feature Service

...

To save MobileMap settings to a feature service, copy existing settings into the Map Properties ‘Description’ field. When the service is published (or republished) the settings can be imported into MobileMap by using Actions > Import Settings.

While adding MobileMap seetings settings to the Feature Service is not required, it is recommended in order to provide efficient and consistent configuration of MobileMap devices. Note that there are some situations where this may not be desired (e.g., cases where MobileMap settings will be imported from settings files, rather than the feature service due to the use of different settings under different scenarios).

...