Feature Service (Hosted) JSON missing "Data" component in ArcGIS Enterprise

04-10-2019 12:19 PM
New Contributor III

ArcGIS Enterprise is giving me a lot of trouble when it comes to having Field Domains, currently have an ongoing case with Esri Support. A workaround I thought that might work would be to publish the layer in ArcGIS Online, where Field Domains work flawlessly. Then publish the layer in ArcGIS Enterprise without the field domains (It fails to publish when I have field domains in the fgdb, again, ongoing case with Esri Support), then use the JSON definition of the Feature Service in AGOL and pop it into the JSON definition of the Feature Service in ArcGIS Enterprise. Except for one thing that I noticed... In ArcGIS Enterprise, when I pull up the JSON definition using ArcGIS Online Assistant (ago-assistant.esri.com), it doesn't have a "Data" component that lists all the layers in the Feature Service. Even though the Feature Service definitely has layers that I'm able to pull into a Web Map and edit, etc.

Any ideas on why the Item's JSON is different in Enterprise than in AGOL?

Even though the Feature Services are basically the same, except for the lack of Field Domains in Enterprise, the JSON definition of the Feature Service in Enterprise is missing the "data" component that contains the information for the layers, pop-ups, etc.

0 Kudos
2 Replies
Occasional Contributor III

Hi Mitchell,

I think what's going on here is that you need to "generate" a definition for the Enterprise item. There's the Feature Service Layer Definition, which you can find here for example: https://sampleserver6.arcgisonline.com/arcgis/rest/services/Earthquakes_Since1970/FeatureServer/0?f=...

But there's also a definition for the ArcGIS Online/Portal for ArcGIS Item - you can easily generate a definition for the item by making a small change to the layer and saving the layer (e.g., change the symbology).


0 Kudos
New Contributor II

I have tested this on ArcGIS Enterprise 10.7.1 with latest patches and nothing has worked other than using the json conversion tool in ArcGIS Pro to a feature layer and then publishing from ArcGIS Pro to a hosted feature service.  Anyone figure out a workaround for this bug other than converting to a file geodatabase FC before publishing?

0 Kudos