Updating domain/coded values in an offline setup

5300
12
Jump to solution
12-11-2014 02:22 AM
KristofferStenersen
Occasional Contributor

Hi,

An app use the AGSPopupsContainerViewController for offline feature editing (AGSGDBFeatures obtained from an offline synced AGSGDBFeatureTable). The popups editor is nice and implementation is efficient.. But this setup seem to have some limitations:

The administrator of this app sometimes needs to do domain changes to the feature services, i.e adding coded values for some of the fields.

Now, these changes does not seem to propagate out to the clients when synchonizing the offline database.

I´ve been able to work around this by setting up a temporary AGSFeatureLayer with a corresponding AGSFeature, matching the AGSGDB table and feature.. But yeah, it´s not a very pretty fix.

Any ideas on how to make a better solution to this?

0 Kudos
12 Replies
KristofferStenersen
Occasional Contributor

Hi!

This app does not have an online mode - as it mainly operate in a disconnected environment. We figured it´s more user friendly to hide the concept of online and offline mode to the end users - all they need to know about is a "synchronize"-operation, and the app always run in "offline" mode.

Also, it is hard for us to build the re-create offline gdb into the workflow - the dataset is large and expensive to re-create when not on wifi (both in terms of cellular fees and time).

Thanks for clearifying this!

0 Kudos
MichaelDavis3
Occasional Contributor III

Hi - just want to confirm what you are saying still applies.

If we add additional entries to a geodatabase domain those values are not updated in existing offline geodatabases when we sync.  This is what is currently happening in our apps, and to be honest is not ideal, especially when a minor domain update could require re-downloading an entire database.

Are there any plans to include domain changes in the sync process in the future? 

As it stands now we are having to replace many of our domains with geodatabase tables for things like crew names, or animal/plant lists that might be updated throughout a project.

0 Kudos
KristofferStenersen
Occasional Contributor

We worked around this by fetching and persisting as fresh copies as possible of the feature layer definitions of all relevant layers. Since they contain all domain values, we present these to the user when editing a domain attribute.

0 Kudos