nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Not All Records are Publishing to ArcGIS Online

MichaelTorbett1

Hello,

I am trying to publish a feature from a file geodatabase to ArcGIS online. This feature contains 611 records, however when I publish it to my organizations online account, only 510 records appear. I don't understand, the maximum records allowed is set to 1000 in the publishing window. Everything seems to be in working order and I recently published a similar layer containing almost 3000 records with no problem. Any insight to what might be causing this problem would be greatly appreciated.

Thanks and have a great day!

Michael

Vind meer berichten getagd met

Accepted answers

All comments

KyleBalke__GISP

Try running the Check Geometry geoprocessing tool and then Repair Geometry if there are errors (ensure you make a backup of your data before running the repair).

MichaelTorbett1

I went ahead and did the check, which found a few errors. Created a duplicate feature (and geodatabase) and ran the Repair Geometry tool. unfortunately I'm still having the same problem. The rest of the features appear to be correct in geometry and I can't find anything within the attributes that's preventing these 101 features from publishing.

Thank you for the suggestion Kyle.

KyleBalke__GISP

What method are you using to publish? Via ArcMap or Add Item in ArcGIS Online?

MichaelTorbett1

I'm publishing through ArcMap.

CathyWilson

I'm having the same problem. I have a very simple point layer in an ArcGIS Map. I'm Publishing it as a Service and when I look at it online, I'm missing a lot of records. I'm working with under a 1,000 records and I tried using a Definition query to include only the records I really need. On my latest test, 15 out of 51 records were uploaded. One test was with about 67 records and 31 uploaded. The whole feature class only has 177 records, so the 1,000 record limit should not be coming into play.

Then I tried Adding the layer from AGOL (Thank you Kyle for the idea.) and was able to upload all 177 records. (It required exporting the feature from the gdb, then zipping it, but it worked.) So something to do with the ArcMap Publisher, then? At least I now have a work around.

CathyWilson

Of course, now I have to re-do my nice symbology online.

KyleBalke__GISP

Cathy...if you can feel free to send me the problem feature class and I can try to troubleshoot for you.

KellyGerrow

Hi Cathy,

Try contacting Technical Support. They can help troubleshoot the issue and find out what is causing the problem.

-Kelly

CathyWilson

I'll send it in a couple of days. I'm out of town now to teach some summer volunteers to collect data with ArcPad.

Thank you,

Cathy

Sent from my iPhone

MichaelTorbett1

Well its's been a while, but here's an update. I finally got it to work. I had to separate the 101 records that wouldn't publish into a separate shapefile in ArcMap. Then republished that layer separately and made sure that the records displayed. Finally I combined them with my original layer using the "merge" tool on ArcGIS Online. That worked! Not sure why AGOL didn't like those 101 records, but it excepted them in a separate feature layer. I've also found that having M values can keep certain records from publishing. That was a separate issue though.

KellyGerrow

Thanks for reporting back Michael.

Can you share your problematic data?

MichaelTorbett1

Here you go Kelly. These are the features that wouldn't display in AGOL but show up fine in ArcMap. If you have trouble downloading it, just let me know.

http://gfcgis.maps.arcgis.com/home/item.html?id=0ec6c20188d24951b6040ded73085a92#overview

KellyGerrow

Hey Michael,

I'd like to get this looked at by technical support. Can you reach out to technical support or let me know if you need some help getting in contact.

-Kelly

MichaelTorbett1

Sure Kelly,

I can do that. I would like to know what causing this data to not publish.

SteveWorkman

I also have this problem, features not been taken across when publishing a service. My original service of 3 layers (point, line and polygon) all worked OK. I then started overwriting the service, which initially worked OK, but today and all the features in the line and polygon layers did not copy across to the service. As suggested above I copied my SDE data to FGDB and now everything copies across fine. I am publishing my service from ArcMap 10.3.1 from an SDE database. I also tried from ArcGIS Pro 1.4 and this also did not copy the features across.

Steve

KellyGerrow

Hey Steve,

I'd suggest getting in touch with technical support to look into this issue specifically.

As a quick troubleshooting step, try downloading and opening the zipped map in the SD file. Is all of the data included in the zipped FGDB? If all of the data is included, we'll need to look into a potential publishing issue.

-Kelly

JenniferStone

I was having the same problem. I had a very small feature class of 48 points (bus stops) but everytime I would publish or overwrite it would only publish 32 of those points. I realized that the points that were not publishing were in one corner of my ArcMap screen so I adjusted the following:

Data Frame Properties > Data Frame > Extent Used by Full Extent Command > Other > Outline of Features > Layer: Bus Stops > Features: All

Once I did this I republished and all of my points were published to AGOL. Hope this helps!

CathyWilson

Thanks for the insight. I'll keep an eye on that the next time I publish.

AdrienLepoutre

Something to consider...if your feature layers in Portal/AGOL are by reference, true curves are currently not displaying in Enterprise 10.7.1 Here is the full description of the bug https://community.esri.com/community/gis/web-gis/arcgisonline/blog/2019/09/13/polygons-containing-curves-not-displaying-in-portal-for-feature-layers-by-reference

Hope this helps!

KarolFallas

  I had the same situation after last realease of ArcGIS Online december 2019, and after many tests, I noted that the records that were not published had a slightly different date value than those that were published.
 In my case I didn’t need the field with the date, so I decided to eliminate it, I re-published the service and everything worked.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.