...
When an existing Feature Service has been developed by MB&G or LandMark it will be provided to you as a File Geodatabase (FGDB) and an ArcMap Document (*.mxd) or ArcPro Project (*.aprx). Additionally, you may be provided with ArcGIS Layer files (*.lyr) which define the symbology for feature layers. If business rules (Rules, Related_Domains, Check_Rules) have already been developed, they will be stored in the FGDB in the appropriate tables (Rules, Related_Domains, Check_Rules). The steps below can be used to publish the Feature Service from these inputs. If you have developed the data model independently, the steps below can be used to develop an ArcMap Document or ArcPro Project and publish a Feature Service.
...
Map document name - we recommend using the same name as the feature (e.g., Cruise_Data_Model_v2). This is helpful when overwriting a Feature Service, as ArcMap will know which Feature Service you are attempting to overwrite.
Map Layer - set projection to Web Mercator (Auxiliary Sphere)
Map Document Properties
Required properties - you must supply the following attributes prior to publishing
Title - We recommend using the same name as the MXD and Feature Service name
Tags - We recommend using ‘MobileMap’ and optionally ‘InventoryManager’ (if relevant)
Optional properties -
Summary - Use as appropriate to clarify the intended use of this service
Description - MobileMap settings can be copied from a MobileMap settings file (Actions > Export Settings). When MobileMap settings are saved in the Map Document Properties Description field, they can be imported into MobileMap (Actions > Export Settings) to set up the device for field data collection. While this is not required, it is highly recommended in order to provide efficient and consistent configuration of MobileMap devices.
Layer Order
The typical layer order is as follows:
...