Problem turning on map service visibility with Set Layer Visibility activity
Hello. I'm writing a workflow for GVH that makes a map service folder visible. I use the Set Layer Visibility activity, and set the Layer ID to the map service number obtained from the Geocortex REST endpoint. But when I run the activity, it doesn't turn on the map service folder.
The weird thing is, if I manually turn on the map service folder to make it visible and then turn it off again, and then rerun the workflow, it works....
Any ideas?
Thanks,
Chris
-
To get the layer id for the set layer visibility command, I was able to use the get layer activity, then an alert activity with =$layer1.layer.id as the input
0 -
I'm pretty sure it's a bug. To test, I set up a new GVH site, with a single map service that has a single layer. The map service folder is not visible by default, but the layer is. I then ran a workflow that has a single Set Layer Visibility activity that makes the Layer Id (0) visible. An alert then shows the wasVisible and nowVisible outputs.
Running the workflow, the folder does NOT turn on, but both the wasVisible and nowVisible say true. So it doesn't work as intended. To get around it, I just put another Set Layer Visibility activity in front of the first one, and set visibility to false. This forces the folder to turn off and on, and fixes the problem.
0 -
I believe you are correct, and I believe geocortex is aware of it. Another post: https://communities.geocortex.com/s/question/0D5f200004oXB8nCAG/are-get-layer-and-get-layervisibility-working
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
3 kommentarer