topic Re: Publish a View with sync enabled for READ ONLY Field Maps in Data Management Questions

Publish a View with sync enabled for READ ONLY Field Maps

vijaybadugu — Wed, 27 Nov 2024 16:02:04 GMT

I generated a view from spatial and non spatial databases, was able to see records in arcgis pro. When I try to publish with sync enabled service for offline usage in arcgis field maps. am getting error. So i tried add Global Id and enabling Archiving on Registered view. I am getting, Views cannot support add GLOBAL ID or Archiving. is there any alternative to this process? We have related to records in non spatial database.

Please suggest.

Re: Publish a View with sync enabled for READ ONLY Field Maps

RPGIS — Wed, 27 Nov 2024 16:09:42 GMT

Hi @vijaybadugu,

We had a similar situation happen and the only recourse we had was to schedule either python script or sql job to update a standalone table. Views cannot be published so we used one of the two as work around.

Re: Publish a View with sync enabled for READ ONLY Field Maps

vijaybadugu — Wed, 27 Nov 2024 16:20:58 GMT

I have been doing for all my previous views . I'm looking solution or work around for it .

Re: Publish a View with sync enabled for READ ONLY Field Maps

simoxu — Thu, 28 Nov 2024 01:22:30 GMT

What's the error message when you publish the spatial view as a sync-enabled feature service?

If you can't use Archiving, you can try versioned view.

To be able to take the feature service offline, I remember the data needs to be from the same enterprise geodatabase.

Please see if the following resource helps:

https://pro.arcgis.com/en/pro-app/3.3/help/data/geodatabases/overview/prepare-feature-layer-data-for-offline.htm

Re: Publish a View with sync enabled for READ ONLY Field Maps

RPGIS — Mon, 02 Dec 2024 19:07:20 GMT

You may need to utilize the NewID() sql method to generate something similar but it might still give you the same error that we kept running into. We had talked with Esri support regarding this and, due to the issue of the view requiring editing capabilities, we were extremely limited in tackling this issue.