Skip to main content

REST endpoint for Site shows interesting order for MapServices

Comments

3 comments

  • Permanently deleted user

    Hi Ralph,

    You are correct.  If your workflow is referencing an ID that changes because of a modification to the site, the Workflow will have to be modified to address the ID change.  

    I don't know that it's "intended" behavior, I think it's more a case of it just being the way it is.

    Steve

     

    0
  • Ryan Cooney

    REST Manager assigns a unique ID to a Map Service when you add it to the site. The only way to change a Map Service ID is to edit the Site.xml directly. If you reorder your services it will not reassign the Map Service IDs.

    --Ryan

    0
  • Permanently deleted user

    Could the GetMapServiceInfo activity be extended to include map service names rather than IDs only??  I'm finding the whole workflow methodology too dependent on having map and layer IDs stipulated and correct. Layer Ids can be obtained using the aforementioned activity, but sticking to names seems an easier option as these could change less over the course of a applications development? Yet there is the possibility of like layer names in sites - perhaps?

    Interesting one..

    G

    0

Please sign in to leave a comment.