Selection Set changes in Saved Project

Chris Roberts

February 27, 2019 02:03

Hi All

 

I just noticed something a bit strange happening with a selection set in a saved porject.  A user saved a number of parcel boundaries in a region and saved the project. When they came back ans opened it a day or so later the selected parcels and changed and were spread all over the State.

 

I tested this myself and I saved and opened a project throughout the day but couldnt replicate this.  However I opened it again the next day and I saw the same thing.  The number of saved parcels was the same, but they were comletly different from the one I originally selected.

 

The only thing I can put this down to is that the Parcel Layer is updated on a nightly basis meaing that the OBJECTID would change.  So does this mean that when Geocortex saves a selection set, the saved feature is based on the OBJECTID?  If so that mean that anytime any layer is updated then and selection set in a sved project would effectively change?

 

Could Latitude shed any light on this.  Is this behaviour expected if/when layers are updated?

 

GXE410 and HTML5 2.11

 

Cheers

 

Chris

0

• 

  Chris Roberts

  February 27, 2019 02:22

  Ok I did I bit more digging and looking at the json file for the saved project it does indeed seem to be that the OBJECTID is held as the ID for the feature.  So, as this parcel layer is updated on pretty much a nightly basis via a delete and append the OBJECTIDs are recreated, meaning that the saved selected set is scrambled.

   

   

  0
• 

  Chris Roberts

  March 07, 2019 23:29

  Anyone from Latitude have any thoughts or suggestions on this?  Is there a workaround to prevent the selection set from scrambling following an update?

   

  Ta

  0
• 

  Permanently deleted user

  March 08, 2019 00:32

  Hi Chris,

   

  Unfortunately, there isn't much we can do about this.  It is indeed the expected behaviour, although we may not have called it out in our documentation.  We operate under the assumption that the OBJECTID attribute is the most relevant.  So, when you load a saved project we will requery the server to get the updated information for the features that were visible in the project when you saved it.

   

  Now that those features are reloaded, you will get a new, different set of data.  If we did not do this, you would be looking at yesterday's data, which was valid when you saved the project but may not be valid any more.  I agree that the "scrambled selection" is not the best way to handle this situation, but this makes it a philosophical argument over whether it's more important to show you the newest, best-to-our-knowledge data, or the last known good set of data.

   

  One possible workaround would be to copy your selection to the graphics layer before saving a project.  Another would be to ensure that your OBJECTIDs are preserved (somehow?) across data reloads.  After a quick scan of various Esri documentation, I'm not sure if that is worth the effort.

   

  Regards,

   

  -Malcolm

  0

Please sign in to leave a comment.