Select to view content in your preferred language

Cannot Enable Export for Managed Feature Layer on Portal

1496
8
02-08-2023 10:04 AM
KenBragg
Occasional Contributor

Hi Folks,

 We have shared a "managed" [edit: "registered" geodatabase ] feature layer (i.e.  the data is coming from an enterprise geodatabase) with Feature and Map enabled and "Export" checked when publishing. I have also verified "Export" is checked in the ArcGIS Server Manager.

One the Portal website I would like to allow users to export data (from the Portal site) but this option does not seem to be available in Item details.  The option is available for hosted layers.

Is this not possible with a managed data source?

Thanks very much

ArcGIS Portal on Server 10.9.4. 

Tags (2)
0 Kudos
8 Replies
Scott_Tansley
MVP Regular Contributor

The managed database was a concept that predates the relational data store.  It worked on the basis of one portal, one hosting server, one  managed geodatabase.  Then the latter was replaced by the Datastore and we were encouraged to copy/migrate the data from managed databases to data stores.  Therefore they have no real place in a current AGE.  

The one to one to one relationship is to align portal functionality with the database.  Because your current environment is using the data store, that functionality is effectively ignoring the managed database. 

Scott Tansley
https://www.linkedin.com/in/scotttansley/
0 Kudos
Scott_Tansley
MVP Regular Contributor
0 Kudos
KenBragg
Occasional Contributor

Thanks for the reply but I don't think this is case. 

We have many services, some with editing enabled based on both a managed database and datastores, all of this works fine. Esri is well aware of this architecture and supports it.

I do agree "we were encouraged to copy/migrate the data from managed databases to data stores"  but not that "they have no real place in a current AGE".  

0 Kudos
Scott_Tansley
MVP Regular Contributor

In which case do you mean registered geodatabase rather than a managed geodatabase?  That's a different thing and I completely understand and advocate for their use.

 

Scott Tansley
https://www.linkedin.com/in/scotttansley/
0 Kudos
KenBragg
Occasional Contributor

Ah yes, maybe I am using the wrong terminology here. The geodatabase source is indeed registered with the server.  I'll edit the original post to make this more clear.

0 Kudos
Scott_Tansley
MVP Regular Contributor

I'm going out on a limb here, because I've never seen specific information on preparing data for export, but when it's for sync there are numerous dependencies:

https://enterprise.arcgis.com/en/server/10.9.1/publish-services/windows/prepare-data-for-offline-use...

I've always assumed that the "export data" option would need the same dependencies to be met, but I could be wrong.

Scott Tansley
https://www.linkedin.com/in/scotttansley/
0 Kudos
Scott_Tansley
MVP Regular Contributor

So you've massively peaked my interest here.  I've worked through some client portals who have Export Data/Sync successfully enabled and used in Distributed Collaborations.  From a registered geodatabase there is no export data source against the item.  Nothing.

I've also reviewed it in my own development environment and can confirm that the function is 'missing'.  It looks like it's only available on hosted feature layers.

When you try and export data from ArcGIS Pro, it makes no difference if export is enabled or not.

However, where the capability does make a difference is in the Analysis Tools in Map Viewer Classic.  If it's not enabled then you cannot export, but turn it on and you get this:

Scott_Tansley_1-1675929499180.png

 

the highlighted option is greyed out if the export data capability is disabled. 

Scott_Tansley_0-1675929459320.png

So I think the issue you describe is by design.

Scott Tansley
https://www.linkedin.com/in/scotttansley/
0 Kudos
KenBragg
Occasional Contributor

Yes thanks a lot Scott for confirming this is missing.  That was kind of my guess as well, that the Export functionality is missing for registered databases. And indeed I can confirm it makes no difference in ArcGIS Pro.  It was within Map Viewers I has hoping to allow it.

 I don't see anything in the documentation the suggests this export should not be available so I whether this is "by design" or an oversight I'm not sure but in any case over to Esri I guess.

0 Kudos