Sharing and Automation
Sharing and Automation tests how you move content from a project to a portal and how you make repeatable work run without manual steps. Expect web layer types, publishing prerequisites, packages, sharing permissions, and automation options.
Sharing web layers
ArcGIS Pro shares maps, layers, and packages to ArcGIS Online or ArcGIS Enterprise. A feature layer supports editing and feature access; a tile layer serves cached map images; a vector tile layer serves fast vector rendering; a map image layer serves dynamic map images; a scene layer serves 3D content. Publishing to a federated Enterprise site can reference registered data or copy data to the hosting server. Referencing avoids duplication but requires a registered data store and permissions; copying creates a hosted layer. Overwrite replaces an existing layer and requires compatible schema and sharing settings. The Share As Web Layer pane runs Analyze before Publish; resolve errors, especially unsupported symbols and source paths.
Packages and automation
Project, map, layer, and mobile map packages consolidate data for sharing. Mobile map packages support offline use. Automation options include Tasks for guided workflows, ModelBuilder for visual workflows, ArcPy scripts and Notebooks for code, and the ArcGIS API for Python for portal administration. Geoprocessing history records tools and parameters. Windows Task Scheduler can run a Python script that calls ArcPy or the API outside Pro; credentials must be stored securely.
Worked example
Publish a feature layer from a file geodatabase to an Enterprise portal for a field crew. Connect to the portal, add the layer to a map, and open Share As Web Layer. Analyze. If the data source is registered with the hosting server, share as referenced; otherwise copy to create a hosted feature layer. Enable editing and sync if offline use is needed. Share with the field crew group, not the organization. Reasoning: reference avoids duplicate storage only when the data store is registered; syncing supports offline editing; group sharing limits access; and Analyze catches unsupported properties before publishing.
Traps
Do not confuse sharing a map with sharing its layers; dependencies can break. A cached tile layer will not reflect edits until the cache is rebuilt. Overwrite fails if the schema or layer type changes. Scripts with hard-coded passwords are a security risk. Check the active portal connection and item owner before publishing; sharing to the wrong portal creates an inaccessible item. Mobile packages need offline-enabled layers and adequate storage.