Publishing from 10.5. Preview shows correct results, and no error messages seen during publishing. The Service Definition and Feature layer are both created, but empty - no records.
Check your editor tracking settings. In my case, the problem was a conflict with having editor tracking enabled on the FGDB feature classes, but also having the editor tracking fields turned off in ArcMap for publishing. Once I turned them back on in ArcMap, the feature service published with all data present. I also had success with disabling editor tracking and then turning off the corresponding editor tracking fields for publishing.
http://indianamap.maps.arcgis.com/home/item.html?id=8ab11dee4ddd484eb04c654d9387e503
here is a link to the published service
I suspect the issue could be due to a problem with the spatial reference. Test if the layers are overlaying correctly over the basemap in ArcMap (before you publish).
If the above step looks fine, try to define the coordinate system of the data-frame to WGS_1984_Web_Mercator_Auxiliary_Sphere, use appropriate transformation method, and republish the Feature Layer.
I am also having this issue. Posting 30,000 line features in a feature service. It publishes successfully but there are no records in the published feature service.Have tried making new copies and overwriting or publishing new feature services. Spatial reference does not seem to be the issue.
I'd suggest sharing your map package or pro package to dig into the data and setup, but there sounds like a bug in the publishing process. Consider contacting https://community.esri.com/groups/technical-support?sr=search&searchId=1996f0dc-eac6-414d-9ef5-f7dba60ed152&searchIndex=4 to help troubleshoot further.
-Kelly
We do not use WGS_1984_Web_Mercator_Auxiliary_Sphere on IndianaMap we use NAD_1983_UTM_Zone_16N (epsg projection 26916). I've confirmed both the data frame and the layer are set to 26916.
I was having this issue when I tried to overwrite a layer from Pro. I tried creating a new layer, nothing. It turns out my editor tracking was on but I had hidden the fields while working in Pro. Unhiding the creator/editor fields before publishing fixed this. Doh!
I've had a similar experience with the editor tracking settings, anyone with this problem should definitely check that first.
I am having the same issue. I enabled editing tracking for the dataset but it's still not working. Do I need to enable editing tracking somewhere else??
No need to enable editor tracking elsewhere, but you will need to verify that the editor tracking fields are turned on for that layer in your map document. To do this, open Layer Properties > Fields tab, then verify that all editor tracking fields are checked (highlighted in the screenshot below).
Another option is to disable editor tracking AND uncheck the fields as indicated in the screenshot above.
Just because i like to dig up the past... What @MatthewRuch1 suggested worked great.
Our scenario: we are publishing certain data to AGO from our SQL database for use in our new HUB site on the company website. The technician prepped all the layers how she wanted it, hiding what she didn't want public. Doing that, she hid the editor tracking fields. I didn't know this was a limitation when publishing to hosted in AGO. I reenabled the editor tracking fields for ALL the layers I published to AGO, and now the data is present.
Pro 3.3.1
Enterprise 11.1
SQL Server 2016
Thank you for that and happy publishing.
Just to show the impact of this, this solved my issue in Enterprise 11.3 publishing with Pro 3.3.
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
