https://community.esri.com/t5/arcgis-enterprise-ideas/allow-publishing-of-featureservices-by-reference/idi-p/1238700 <P>Currently in order to publish a FeatureService (for editing, sync, extract, replication, etc.) by reference from an enterprise geodatabase, you need to also publish the associated MapService (enabling "feature service" in the process.&nbsp;&nbsp;</P><P>However sometimes all we need is the FeatureService (e.g. for extract workflows with visualization on datasets that don't need a mapservice to power visualization).&nbsp; It would be nice if there was an option to&nbsp;<EM>just</EM> publish the FeatureService.&nbsp; I imagine that might reduce strain on server resources, minimize the number of Portal assets, and lessen confusion to users (especially new users), when looking at a FeatureService and MapService of the same exact data.&nbsp;&nbsp;</P> Wed, 07 Dec 2022 13:29:05 GMT Jay_Gregory 2022-12-07T13:29:05Z https://community.esri.com/t5/arcgis-enterprise-ideas/allow-publishing-of-featureservices-by-reference/idi-p/1238700 <P>Currently in order to publish a FeatureService (for editing, sync, extract, replication, etc.) by reference from an enterprise geodatabase, you need to also publish the associated MapService (enabling "feature service" in the process.&nbsp;&nbsp;</P><P>However sometimes all we need is the FeatureService (e.g. for extract workflows with visualization on datasets that don't need a mapservice to power visualization).&nbsp; It would be nice if there was an option to&nbsp;<EM>just</EM> publish the FeatureService.&nbsp; I imagine that might reduce strain on server resources, minimize the number of Portal assets, and lessen confusion to users (especially new users), when looking at a FeatureService and MapService of the same exact data.&nbsp;&nbsp;</P> Wed, 07 Dec 2022 13:29:05 GMT https://community.esri.com/t5/arcgis-enterprise-ideas/allow-publishing-of-featureservices-by-reference/idi-p/1238700 Jay_Gregory 2022-12-07T13:29:05Z