Only a subset of data included in .geodatabase

[MichaelDavis3]

I'm attempting to create an offline geodatabase using the desktop pattern to display ~13k property ownership polygons in an iPad app.

It seems like all of the records are not displaying in the map, and I confirmed this by checking out the .geodatabase file in a sqlite viewer... only about 10% of the records are actually included.

Is there some sort of limit on the number of records that can be exported via the desktop tools?

[JamesRichards1]

Are there null shapes in the source data? We found that features with null shapes do not make it into the runtime geodatabase when generating a replica via a FeatureServer. Maybe something similar is happening with the Share As Runtime Content tool?

[DavidGreene]

All of the shapes (point features) are valid.  I haven't found a reason yet for the incomplete exports.

However, I did find a temporary work-around.  Through some developer sleuthing and curiosity, I found a reference to an SDE connection to the SQLite .geodatabase file.  To my utter surprise, it worked.  I opened a connection to the .geodatabase file in ArcCatalog as if it was a an enterprise geodatabase.  I simply deleted the 3 incomplete features classes and copied them from the source database.  All features accounted for and working without issues so far on the devices.

It appears Esri is still in the development stages for this type of connection and thus why they haven't made it public .. if they plan on doing so at all.  While my trials did work, there were plenty of errors that popped up when trying to do some typical "enterprise" operations just for giggles.  I would only recommend this option to those who are very technical and understand the internal geodatabase structure and system tables.

I hesitate to post the details of method I used unless someone at Esri gives the "OK" to do so.  As with any undocumented method, there is a real danger of corrupting data.

[ValCannon1]

I spent several hours with this problem and I have found another work-around. Null geometry does not convert but the .geodatabase also doesn't like extremely complex polygons with multiple holes cut out of them.

There is also a bug in the "Share as runtime content" in ArcMap. When the analyze or output window appear during the export, they reduce the extent of the export. The trick is to zoom out further than the full extent and pan up so that none of your features are covered by the output/analyze window during export. Seems like an odd bug.

The best solution would be for ArcCatalog to support the .geodatabase extension just like it does other formats.

[DavidGreene]

If anyone is looking at this post with a similar problem, I have discussed it with Esri Technical Support at the Dev Summit and confirmed that there is a bug that appears to be fixed in 10.4.

If any of the layers/tables you are exporting to Runtime Content has a GlobalID column, then the export may fail and/or result in an incomplete runtime geodatabase.  The only workaround is to delete the GlobalID columns before exporting.

I have not yet confirmed that the export succeeds in 10.4 or any versions of ArcGIS Pro.