Select to view content in your preferred language

Anyone having issue with the scale dependency check marks in the TOC?

872
8
06-14-2010 11:05 AM
by Anonymous User
Not applicable
We have had our server site up for a year.  In the last few months we republished a service and added a new service to our TOC.  The updated service and new service show all layers to be active and to scale on the TOC (black check mark).  Previously the check marks would stay greyed out until the layer actually became active.  This feature no longer works.  The layers that are in our site that we have not changed in the past year still show the scale dependency with the grey check mark and when the layer is up to scale, the check mark turns black.  The scale dependency appears correct in the mxd, however, when the service is published and added to the config in flex, the layers show up as "active" at all times, even though they will not show up until they hit the set scale dependency we applied in the mxd.  What would cause the scale depenedency check marks to stop functioning?
Tags (2)
0 Kudos
8 Replies
RobertScheitlin__GISP
MVP Emeritus
Allison,

    I am the developer of that code and have not seen the issue you are having. Did you clear your REST Service directory Cache once you made your map service changes?
0 Kudos
by Anonymous User
Not applicable
Robert,

Yes we have done that.  We have also complety recreated the mxd, republished and cached several times.  We even tried recreating and renaming the mxds and publishing to another service and mapping the config to that path.  We appreciate your codes and we have not had an issue with this until a month or so ago.  In April one of my original mxds was overwritten by a coworker, since that time we have experienced this scale dependency issue on this particular layer and any new mxd/layers we have tried to add to our project.
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Allison,

   That is strange... Is your map service public? If so I could test on my end and see if i get the same results.
0 Kudos
by Anonymous User
Not applicable
Unfortunately is it not public.  We have had a few of our IT group investigating it as well and we have yet to come up with a solution or cause.  Would you have any other suggestions, no matter how far fetched.  We are willing to try anything at this point.  We always appreciate your input.
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
Allison,

    With out much to go on here all I can do is take stabs in the dark:

1. On your web server where the app is deployed ensure you have the sd_overlay.png file. Should be in the \com\esri\solutions\flexviewer\assets\images\toc folder.

2. Look at your REST Services directory for that map service and then a layer that is scale dependent and ensure that it has either a max or min scale (like my layer 67 has Min. Scale: 15000).
0 Kudos
by Anonymous User
Not applicable
Well, all I can say is that you are great at taking stabs in the dark!  Your second solution did the trick.  I had a min and a max set for some of the layers.  Once I set the max to "none" the scale dependency began working again.  We really appreciate your insight and we always look forward to seeing your new ideas.

Oh Happy Day, Thank You!
Allison
0 Kudos
LarryPhelps
Regular Contributor
Robert,

Have done any modifications to the TOC in the new Flexviewer 2 to handle the Scale dependency and grey the layers out when not visible ?
0 Kudos
RobertScheitlin__GISP
MVP Emeritus
0 Kudos