Hi Team,
I'm trying to publish an editable Web Feature Layer where the users should be able to edit and update some fields. I have this feature class in a FGDB, and whenever I tried to publish the layer to the portal, I got the below error:
and there is no option to correct this error. Any thoughts?
Solved! Go to Solution.
FGDB does not support editing on a featrue service. You need to use an Enterprise geodatabase. Here is a similar question - https://community.esri.com/t5/arcgis-online-questions/layer-s-data-source-not-supported-feature-serv...
FGDB does not support editing on a featrue service. You need to use an Enterprise geodatabase. Here is a similar question - https://community.esri.com/t5/arcgis-online-questions/layer-s-data-source-not-supported-feature-serv...
Thank you very much for your response. Much appreciated.
I will try to connect using an Enterprise geodatabase but this will allow users to edit directly before we make our QAQC of the data. That's why I was hoping to use FGDB.
Use a copy of the feature class as a staging table or consider using a hosting feature service for staging? You don’t have to edit the authoritative feature class directly.
with regards to the fgdb approach. A ms word document on a windows file share will only allow one person to edit it because of windows applying locks to the file. The same is true of a fgdb. One instance of a map/feature service is the equivalent of a user in this contact. Multiple instances of a service are like multiple users. Windows is the limiting factor and so you need a multi-user (enterprise) geodatabase.
Hi @Abdullah_AlFazari,
As @berniejconnors said, your data source needs to be stored in an enterprise geodatabase to publish a feature service. File geodatabase data are not supported. Learn more in the help topic,
Prepare data to publish a feature service
Hope this helps,
Hi @DerekLaw
Thank you very much for your response and being here. Much appreciated. will try it now.
@DerekLaw i understand you cant publish a feature service from an fgdb...but you can go into the server manager and enable feature service access on the map image layer service to then spin up a feature layer...are there any gotchas or potential pitfalls to going this route? thanks.
I have created an "idea" related to this topic - "Read-only feature service from FGDB".
Bernie.